Live / Sage / Incident
Sage: Sage HCM (Criterion) - Operational
Sage · sage.comResolved2026-10-22 20:03 UTC
Public — what happened
Summary
Sage reported an incident on its status page. It has been resolved.
Affected
Sage HCM (Criterion), Sage HCM (Criterion)
Timeline
- Started — 2026-10-21 19:22 UTC
- Investigating — 2026-10-21 19:22 UTC (2 updates)
- Monitoring — 2026-10-22 10:54 UTC
- Resolved — 2026-10-22 20:03 UTC · 24h 40m 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 44, 2026, our weekly internet health report.