Live  /  Sage  /  Incident

Sage: Sage 300 People Managed Services - Partial Outage

Sage · sage.comMinor incidentResolved2026-10-28 12:07 UTC
Public — what happened

Summary

Sage reported a partial outage affecting its Sage 300 People Managed Services product, which it rated as minor. The company said it began looking into the problem at 14:11 UTC on 2026-10-27, and later said a small number of customers in South Africa could not log in to the application. Sage said it found the cause that afternoon and began working on a fix. By 12:07 UTC on 2026-10-28 it said the service was performing as expected and that it was monitoring closely to prevent a repeat, and the incident had not yet been marked resolved.

Affected

Sage 300 People Managed Services

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 45, 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.