Live / Sage / Incident
Sage: Sage.com Websites - Degraded Performance
Sage · sage.comMinor incidentResolved2026-11-10 20:51 UTC
Public — what happened
Summary
Sage reported a minor incident causing degraded performance on its Sage.com websites, starting at 18:51 UTC on 2026-11-10. About fifteen minutes later, the company said customers using the Commerce Journeys section of the sites were experiencing slowdowns, and it was still investigating. Sage did not name a cause in the text provided, and the incident was marked resolved at 20:51 UTC.
Affected
Sage.com Websites, Sage.com Websites
Timeline
- Started — 2026-11-10 18:51 UTC
- Investigating — 2026-11-10 18:51 UTC (2 updates)
- Resolved — 2026-11-10 20:51 UTC · 1h 59m 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 47, 2026, our weekly internet health report.