Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Sophos Outage History

Every past Sophos outage tracked by IsDown, with detection times, duration, and resolution details.

There were 76 Sophos outages since May 2023. The 17 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor May 14, 2026

May 2026: Important Sophos Notification Regarding: Sophos Email

Detected May 14, 2026 9:43 AM UTC · Resolved May 14, 2026 10:49 AM UTC · Duration about 1 hour

Sophos Email experienced a service degradation across multiple regions (Canada, Germany, India, Ireland, Japan, and Ohio) that caused delays and temporary inability to receive inbound emails for 1.1 hours. The issue was related to a third-party provider and affected the email processing queue. Engineering teams resolved the problem by releasing stuck emails from the processing queue and restoring normal delivery for new incoming emails.

Minor April 14, 2026

April 2026: Important Sophos Notification Regarding: Sophos Partner Portal

Detected Apr 14, 2026 9:10 AM UTC · Resolved Apr 14, 2026 11:35 AM UTC · Duration about 2 hours

The Sophos Partner Portal became inaccessible for 2.4 hours, preventing partners from accessing the portal while other Sophos dashboards (Enterprise, Partner, and Central) remained unaffected. Partners reported being unable to access the portal during the outage, which was classified as a minor incident.

Minor March 2, 2026

March 2026: Important Sophos Notification Regarding: Sophos Central

Detected Mar 2, 2026 10:16 AM UTC · Resolved May 19, 2026 1:32 PM UTC · Duration 3 months

Sophos Central customers in the UAE region experienced inability to access the platform, affecting multiple components including admin dashboards, email services, network management, and monitoring systems. The service disruption was geographically limited to the UAE region only. The incident lasted approximately 78 days with ongoing informational updates directing customers to a knowledge base article for status information.