Live / Sage / Incident
Sage: Remote Data Access (RDA) NA - Operational
Sage · sage.comResolved2026-11-13 14:06 UTC
Public — what happened
Summary
Sage reported a problem with its Remote Data Access (RDA) service in North America that began on 2026-10-30 at 10:20 UTC. Sage said a small number of customers in Canada could not open their Sage 50 files, and it suggested stopping and then re-sharing the files as a temporary workaround. Sage said it was still looking into the cause on 2026-11-02, then reported on 2026-11-04 that the service was working as expected and that it was monitoring to prevent a repeat. The incident was marked resolved on 2026-11-13, and Sage did not state a cause in the text provided.
Affected
Sage 50
Timeline
- Started — 2026-10-30 10:20 UTC
- Investigating — 2026-10-30 10:20 UTC
- Identified — 2026-10-30 10:41 UTC (2 updates)
- Monitoring — 2026-11-04 16:00 UTC (2 updates)
- Resolved — 2026-11-13 14:06 UTC · 14 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.