Live / Sage / Incident
Sage: Sage 50 (US) - Partial Outage
Sage · sage.comMajor incidentidentified2026-11-13 20:59 UTC
Public — what happened
Summary
Sage said customers in the US were unable to reach both the Cloud and Desktop versions of Sage 50, with the problem beginning around 14:28 UTC on 2026-11-11. The company said it identified the issue within about twenty minutes and spent the next day working on a fix. By 16:12 UTC on 2026-11-12 it reported the Cloud service was performing as expected and was being watched closely. Sage said work on the Desktop version was still ongoing, and it pointed affected users to a workaround in a help article, so the incident was not marked resolved.
Affected
Sage 50
Timeline
- Started — 2026-11-11 14:28 UTC
- Investigating — 2026-11-11 14:28 UTC
- Identified — 2026-11-11 14:46 UTC (4 updates)
- Monitoring — 2026-11-12 16:12 UTC
- Identified — 2026-11-12 16:30 UTC (2 updates)
- Ongoing at last check.
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Sage against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Sage: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Sage report →
More from Sage
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.