Sage experienced a major incident on May 18, 2026 affecting Sage Business Cloud Accounting ZA, lasting 9d 6h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 18, 2026, 08:16 AM UTC
We are investigating a potential issue with the service. An update will be provided within 30 minutes.
- investigating May 18, 2026, 08:49 AM UTC
We have identified that customers are experiencing severe slowness when trying to use the product. We are currently investigating.
- identified May 18, 2026, 09:24 AM UTC
We have scheduled an emergency maintenance at 11:25 SAST at 18th of May to help us resolve the issue. The service will be unavailable for customers while we conduct this activity. We apologise for any inconvenience this might cause.
- identified May 18, 2026, 09:52 AM UTC
We have completed the maintenance succesfully and the service is now available. We continue to investigate to ensure that all services have resumed succesfully.
- monitoring May 18, 2026, 12:48 PM UTC
The service is performing as expected. Avoiding a reoccurrence is our priority as we closely monitor the service. We have scheduled a maintenance at 20:00 SAST on the 18th of May that will last for 20 minutes, until 20:20 SAST. During this scheduled time customers might experience slow performance while using the service. We apologise for any inconvenience this might cause.
- monitoring May 18, 2026, 07:08 PM UTC
The scheduled maintenance has been completed successfully. The service is performing as expected. Avoiding a reoccurrence is our priority as we closely monitor the service.
- investigating May 19, 2026, 07:34 AM UTC
We have identified that customers may experience degraded performance when using the product. We are currently investigating.
- monitoring May 19, 2026, 11:18 AM UTC
The service is performing as expected. Avoiding a reoccurrence is our priority as we closely monitor the service.
- identified May 21, 2026, 08:44 AM UTC
We have identified that customers are experiencing slowness and being presented with the following error "can´t reach this page". We have identified the cause and are working on a fix. We apologise for any inconvenience this might cause.
- identified May 21, 2026, 11:14 AM UTC
We have scheduled an emergency maintenance at 13:15 SAST at 21th of May to help us resolve the issue. The service will be unavailable for customers while we conduct this activity.
- identified May 21, 2026, 11:23 AM UTC
The server is now available for customers. We expect that some customers could potentially experience slowness while using the service and eventually will be presented with errors. We continue to investigate. We apologise for any inconvenience this might cause.
- identified May 21, 2026, 12:41 PM UTC
The server continues to be available for customers, however third-party integrations will remain disabled until 16:00 SAST. We have scheduled a maintenance at 19:00 SAST on the 21th of May that will last for 3 hours minutes, until 22:00 SAST. The service will remain unavailable during most of this scheduled window. We apologise for any inconvenience this might cause.
- identified May 21, 2026, 02:22 PM UTC
The server continues to be available for customers, and third-party integrations have been enabled. We have scheduled a maintenance at 19:00 SAST on the 21th of May that will last for 3 hours minutes, until 22:00 SAST. The service will remain unavailable during most of this scheduled window. We apologise for any inconvenience this might cause.
- monitoring May 21, 2026, 07:23 PM UTC
The scheduled maintenance has been completed and the service is performing as expected. Avoiding a reoccurrence is our priority as we closely monitor the service.
- monitoring May 22, 2026, 01:27 PM UTC
The service has continued to perform as expected and we continue to closely monitor. We have scheduled a maintenance to add further improvements at 20:00 SAST that will last for 20 minutes until 20:20 SAST. During this scheduled time customers might experience slow performance while using the service. We apologise for any inconvenience this might cause.
- monitoring May 26, 2026, 02:48 PM UTC
The service continues to perform as expected. Avoiding a reoccurrence is our priority as we closely monitor the service.
- resolved May 27, 2026, 02:56 PM UTC
The issue is resolved and the service continues to perform as expected.