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

As listed on Sage’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the Sage status & history page.

Related: Sage status & history. SquidGrid is not affiliated with Sage.