Live / Sage / Incident
Sage: Brightpearl - Partial Outage
Sage · sage.comMinor incidentResolved2026-10-29 14:06 UTC
Public — what happened
Summary
Sage reported a partial outage affecting its Brightpearl service, which it rated as minor. The company said that starting on 28 October 2026 at 10:53 UTC, customers around the world could not save xlsx files and saw a "Failed to save a file" error, while everything else in the product worked normally. Sage said it identified the issue by 11:13 UTC, and by 12:53 UTC reported the service was performing as expected while it monitored to avoid a repeat. The incident was marked resolved on 29 October at 14:06.
Affected
Brightpearl, Brightpearl, Brightpearl, Brightpearl
Timeline
- Started — 2026-10-28 10:53 UTC
- Investigating — 2026-10-28 10:53 UTC
- Identified — 2026-10-28 11:13 UTC
- Monitoring — 2026-10-28 12:53 UTC
- Resolved — 2026-10-29 14:06 UTC · 27h 14m 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.