Live / Sage / Incident
Sage: Sage Intacct - Operational
Sage · sage.comMinor incidentResolved2026-11-06 09:56 UTC
Public — what happened
Summary
Sage said that some customers using the Sage Intacct sandbox, its testing environment, ran into an issue that could stop certain testing tasks from being completed. The company said the live production environment was not affected. It reported the issue on 2026-10-27 at 19:03 UTC and said its teams were working to restore the affected data and services. The incident is now marked resolved as of 2026-11-06 at 09:56.
Affected
Sage Intacct, Sage Intacct, Sage Intacct, Sage Intacct
Timeline
- Started — 2026-10-27 19:03 UTC
- Identified — 2026-10-27 19:03 UTC
- Resolved — 2026-11-06 09:56 UTC · 10 days 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.