Live / Sage / Incident
Sage: AutoEntry - Core
Sage · sage.comMinor incidentResolved2026-11-03 15:09 UTC
Public — what happened
Summary
Sage reported a minor incident affecting AutoEntry Core, starting at 12:41 UTC on 2026-11-03. The company said customers in all regions could not sync the desktop and web versions and were seeing time-out errors, and that it was looking into the reason. By 13:30 UTC Sage said the service was working as expected and that it was monitoring to prevent a repeat, and the incident was marked resolved at 15:09. No cause was given in the text provided.
Affected
AutoEntry, AutoEntry, AutoEntry, AutoEntry, AutoEntry
Timeline
- Started — 2026-11-03 12:41 UTC
- Investigating — 2026-11-03 12:41 UTC (2 updates)
- Monitoring — 2026-11-03 13:30 UTC
- Resolved — 2026-11-03 15:09 UTC · 2h 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 46, 2026, our weekly internet health report.