Live / Sage / Incident
Sage: Certificates Renewal Sage 50 / 200 / Payroll - Operational
Sage · sage.comResolved2026-11-09 09:58 UTC
Public — what happened
Summary
Sage reported a problem starting at 15:36 UTC on 2026-11-06 that stopped some customers in Europe using Intouch from renewing their certificates. It said only customers who actually needed to renew were affected, and that Sage 50 UKI, Sage 200 UKI and Sage Business Cloud Payroll UKI otherwise worked normally for everyone else. Sage said the issue was identified and the service is now performing as expected, and it is monitoring closely to avoid a repeat. The incident is still marked as monitoring and has not been declared resolved.
Affected
Sage 50 Accounts, Sage 200 Standard (UKI), Sage Business Cloud Payroll
Timeline
- Started — 2026-11-06 15:36 UTC
- Identified — 2026-11-06 15:36 UTC
- Monitoring — 2026-11-06 15:36 UTC
- Resolved — 2026-11-09 09:58 UTC · 3 days after it started
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 46, 2026, our weekly internet health report.