Skip to main content
Sophos logo

Is Sophos Down?

No — Sophos is up

Reachable from all 8 checked regions

Average response time: 2440ms

Last checked · checks run every 6 hours

Official status page: https://status.sophos.com

Sophos uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
2171ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 33 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

33-day clean streak
Sep 12: 100.00% uptime, 31 checks
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 31 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 31 checks
Sep 19: 100.00% uptime, 31 checks
Sep 20: 100.00% uptime, 31 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 23 checks
Sep 24: 100.00% uptime, 45 checks
Sep 25: 100.00% uptime, 31 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 31 checks
Sep 30: 100.00% uptime, 32 checks
Oct 1: 100.00% uptime, 31 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 30 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 31 checks
Oct 7: 100.00% uptime, 31 checks
Oct 8: 100.00% uptime, 31 checks
Oct 9: 100.00% uptime, 31 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 29 checks
Sep 12 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

iad
1756ms
DNS 0ms TCP 104ms TLS 210ms TTFB 1756ms
jnb
3564ms
DNS 0ms TCP 196ms TLS 390ms TTFB 3564ms
lax
2670ms
DNS 0ms TCP 151ms TLS 307ms TTFB 2669ms
lhr
377ms
DNS 0ms TCP 10ms TLS 23ms TTFB 377ms
nrt
4137ms
DNS 0ms TCP 242ms TLS 487ms TTFB 4136ms
ord
1837ms
DNS 0ms TCP 109ms TLS 219ms TTFB 1837ms
sin
2818ms
DNS 0ms TCP 166ms TLS 334ms TTFB 2818ms
sjc
2363ms
DNS 0ms TCP 141ms TLS 284ms TTFB 2363ms

What Sophos does

Sophos sells endpoint protection, firewalls, email filtering and managed detection to businesses, all administered through a web console called Sophos Central. Partners and managed service providers use the same console to run security across many client organisations at once. Sophos Home is a separate consumer product with its own dashboard.

What an outage looks like

The Sophos Central console fails to load or sign-in hangs, so administrators cannot push policy, read alerts or investigate detections. Because Central is hosted per region, an administrator in one country is locked out while a colleague on a tenant in another region works normally. Sophos Email, DNS Protection, ZTNA and firewall management are separate components and can fail individually.

What to do about it

Open status.sophos.com and find the region your tenant is hosted in. Sophos breaks the Central dashboards down by region, listing Ireland, Germany, Australia, Brazil, Canada, India, Japan, Ohio and Oregon separately, so the global headline is rarely the answer. The Partner, Admin and Enterprise dashboards are also tracked separately, as are the support portal and product documentation.

Is it down for everyone, or just you?

If this page says Sophos is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Sophos outage FAQ

Sophos Central will not load for me but works for a colleague. Why?
Sophos Central is regional. The status page reports each dashboard against a specific region, including Ireland, Germany, Australia, Brazil, Canada, India, Japan, Ohio and Oregon. Your tenant lives in exactly one of them, so an incident in that region locks you out while a colleague whose tenant sits elsewhere is unaffected. Find your region on the page before raising a case.
Does a Sophos Central outage mean my endpoints are unprotected?
Sophos does not state on its status page what protection does while the console is unreachable, so we will not claim endpoints keep enforcing policy. What the page does show is that management dashboards and protection services such as DNS Protection, ZTNA, Workspace Protection and Phish Threat are listed separately, so an incident can be confined to management alone. Verify against an endpoint rather than assuming.
Is Sophos Home affected when Sophos Central is down?
Not necessarily. Sophos Home and the Sophos Home Dashboard are separate components from Sophos Central on the same status page. Sophos Home is the consumer product and runs on its own infrastructure, so a business console incident and a home product incident are usually distinct events. Check the entry that matches the product you actually use.
Can I still manage my firewall if Sophos Central is unavailable?
Central Firewall Management and Central Firewall Reporting are their own components, so cloud management can be interrupted while other parts of Central work. Sophos does not publish local-management fallback behaviour on the status page, so check your firewall's own local interface directly rather than assuming it is reachable or unreachable.
Why can I not reach Sophos support during an outage?
The support surfaces are separate components and can be affected at the same time. Sophos tracks the Sophos Support Portal, Sophos Community, Sophos Product Documentation, MySophos and Sophos.com individually. That means the console, the place you would raise a case about the console and the documentation explaining it can each be down independently, or together.

How we measure this

  • We request Sophos's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Sophos publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Sophos goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required