Live / Sage / Incident
Sage: Sage Token Service - Degraded Performance
Sage · sage.comMinor incidentResolved2026-11-06 17:01 UTC
Public — what happened
Summary
Sage reported a minor incident labeled degraded performance affecting its Sage Token Service, which began at 15:34 UTC on 2026-11-06. By 16:11 UTC the company said it had found that requests to the service from Sage 50 CA were failing, and it was still looking into the problem. Sage did not state a cause in the text provided, and the incident is marked resolved as of 17:01 UTC.
Affected
Sage Token Service
Timeline
- Started — 2026-11-06 15:34 UTC
- Investigating — 2026-11-06 15:34 UTC (2 updates)
- Resolved — 2026-11-06 17:01 UTC · 1h 26m 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.