Live / Sage / Incident
Sage: Sage 50 US/CA Authentication Issues - Operational
Sage · sage.comResolved2026-11-10 21:06 UTC
Public — what happened
Summary
Sage said that customers of its Sage 50 US and Canada products may be asked to complete multifactor sign-in checks more often than they should, because the option to remember a device for 30 days is not working as intended. The report began on 2026-11-05 at 22:32 UTC, when Sage listed the problem as identified. On 2026-11-06 at 14:53 UTC Sage moved the incident to monitoring and said the issue will be addressed in a future product update. It has not been marked resolved.
Affected
Sage 50
Timeline
- Started — 2026-11-05 22:32 UTC
- Identified — 2026-11-05 22:32 UTC
- Monitoring — 2026-11-06 14:53 UTC
- Resolved — 2026-11-10 21:06 UTC · 5 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 46, 2026, our weekly internet health report.