Live / Sage / Incident
Sage: Brightpearl - Partial Outage
Sage · sage.comMinor incidentResolved2026-11-13 13:32 UTC
Public — what happened
Summary
Sage reported a minor partial outage affecting its Brightpearl service, which began at 09:44 UTC on 2026-11-13. The company said customers worldwide were seeing unexpected behaviour after posting landed cost allocations, and it identified the issue about half an hour after first investigating. By 11:23 UTC Sage said the service was performing as expected and it was monitoring to prevent a repeat, and the incident was marked resolved at 13:32 UTC.
Affected
Brightpearl, Brightpearl, Brightpearl, Brightpearl
Timeline
- Started — 2026-11-13 09:44 UTC
- Investigating — 2026-11-13 09:44 UTC
- Identified — 2026-11-13 10:15 UTC
- Monitoring — 2026-11-13 11:23 UTC
- Resolved — 2026-11-13 13:32 UTC · 3h 48m 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 47, 2026, our weekly internet health report.