Sage Business Cloud Payroll South Africa partial outage, 20 November
Sage's status page logged a partial outage affecting South African payroll customers on 20 November, describing the service as restored 23 minutes later.
Sage's service status page recorded a partial outage on Business Cloud Payroll in South Africa on 20 November. The page titled the incident "Partial Outage", posted its first notice at 07:18 UTC, and declared the service restored in an update 23 minutes later. Both entries carry UTC timestamps; the copy we reviewed did not state a year.
The timeline on Sage's status page
The first entry appeared at 07:18 UTC under the heading Investigating. "We are investigating a potential issue with the service," the vendor wrote. "An update will be provided within 30 minutes."
The second entry followed at 07:41 UTC under the heading Monitoring. In it, Sage said it had "identified an issue that was preventing a small subset of customers in South Africa from using certain functionalities within the service". The same entry stated that "the service is now restored and performing as expected", and that avoiding a repeat remained the priority while the service was monitored.
Two details stand out in that record. The 07:41 entry was filed as Monitoring rather than Resolved, even though its text said the service was back. And the record we reviewed ends there, with no later resolution or root-cause entry.
Who was affected?
By the vendor's own wording, the blast radius was narrow: "a small subset of customers in South Africa". The affected service is Business Cloud Payroll. The page named no specific functions, gave no customer count, and said nothing about other regions or other Sage products.
Impact on mid-month payroll work
The vendor described the service as performing as expected.
The gap in the record matters in practice.
What is still unknown?
The root cause was not disclosed. The number of affected customers, the functions involved, and whether any in-flight submissions or calculations were disturbed all remain unsaid. The impairment may also predate the 07:18 notice by an unknown amount, so the true duration is not established. We found no follow-up entry marking the incident fully resolved.