Live / Sage / Incident
Sage: Sage 200 Standard (UKI) - Operational
Sage · sage.comMinor incidentmonitoring2026-11-13 16:09 UTC
Public — what happened
Summary
Sage reported a minor issue affecting its Sage 200 Standard service for the UK and Ireland, starting at 11:13 UTC on 2026-11-13. The company said manually created backups in Sage 200 Standard UK and Sage 200 Professional got stuck in progress and did not finish. By 11:27 UTC it said the problem was fixed and it was monitoring, and at 16:09 UTC it said the service was performing as expected. Sage said anyone who started a backup before the fix would need to wait for it to time out, and the incident is still listed as being monitored.
Affected
Sage 200 Standard (UKI)
Timeline
- Started — 2026-11-13 11:13 UTC
- Investigating — 2026-11-13 11:13 UTC
- Monitoring — 2026-11-13 11:27 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.