Live / Sage / Incident
Sage: Sage Intacct - Partial Outage
Sage · sage.comMinor incidentResolved2026-10-30 15:56 UTC
Public — what happened
Summary
Sage said it began investigating a possible problem with Sage Intacct on 2026-10-29 at 09:29 UTC, which it labeled a minor partial outage. It later explained that a small group of customers in Europe could not log in and were shown an error saying their IP address was not valid. By 12:46 UTC the same day Sage said the service was working as expected and that it was monitoring to prevent a repeat, and it marked the incident resolved on 2026-10-30 at 15:56. Sage did not state a cause in the text provided.
Affected
Sage Intacct
Timeline
- Started — 2026-10-29 09:29 UTC
- Investigating — 2026-10-29 09:29 UTC (2 updates)
- Monitoring — 2026-10-29 12:46 UTC
- Resolved — 2026-10-30 15:56 UTC · 30h 27m 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.