Live / Sage / Incident
Sage: Sage Expense Management CapitalOne - Partial Outage
Sage · sage.comMinor incidentResolved2026-10-26 19:06 UTC
Public — what happened
Summary
Sage reported a partial outage involving Sage Expense Management CapitalOne, which it rated as minor, beginning at 16:58 UTC on 2026-10-26. The company said customers in the USA were not receiving replies when they sent SMS messages. By 17:19 UTC Sage said it had found the cause of the problem and was working on a fix, and the incident was marked resolved at 19:06.
Affected
Sage Expense Management CapitalOne
Timeline
- Started — 2026-10-26 16:58 UTC
- Investigating — 2026-10-26 16:58 UTC
- Identified — 2026-10-26 17:19 UTC
- Resolved — 2026-10-26 19:06 UTC · 2h 08m 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 45, 2026, our weekly internet health report.