Sage incident

Sage 50 Cloud (US) - Operational

Minor Resolved View vendor source →

Sage experienced a minor incident on August 10, 2026 affecting Sage 50 Cloud (US), lasting 7h 36m. The incident has been resolved; the full update timeline is below.

Started
Aug 10, 2026, 08:35 AM UTC
Resolved
Aug 10, 2026, 04:11 PM UTC
Duration
7h 36m
Detected by Pingoru
Aug 10, 2026, 08:35 AM UTC

Affected components

Sage 50 Cloud (US)

Update timeline

  1. investigating Aug 05, 2026, 02:14 PM UTC

    We are investigating a potential issue with the service. An update will be provided within 30 minutes.

  2. investigating Aug 05, 2026, 02:44 PM UTC

    We have identified an issue preventing customers in the US from accessing their G drive. We are currently investigating.

  3. investigating Aug 05, 2026, 05:02 PM UTC

    We are continuing to investigate the cause of the issue.

  4. investigating Aug 05, 2026, 07:09 PM UTC

    We continue to investigate the cause of the issue. We appreciate your patience as we work to resolve this issue.

  5. investigating Aug 06, 2026, 12:21 PM UTC

    We continue to investigate the cause of the issue. If you urgently require access to your G: Drive, please reach out customers services that will be able to apply a workaround. We apologise for any inconvenience this might cause.

  6. monitoring Aug 07, 2026, 07:43 PM UTC

    The service is performing as expected. Avoiding a reoccurrence is our priority as we closely monitor the service.

  7. monitoring Aug 10, 2026, 08:44 AM UTC

    In order to introduced further stability measures we have scheduled a maintenance at 04:40 ET on the 10 of August that will last for 30 minutes until 05:10 ET on the 10th of August. During this scheduled period customers might require to re-enter the credentials to log in or be unable to access the services for a brief period of time. We apologise for any inconvenience this might take.

  8. monitoring Aug 10, 2026, 09:10 AM UTC

    The service is performing as expected. Avoiding a reoccurrence is our priority as we closely monitor the service.

  9. resolved Aug 10, 2026, 04:11 PM UTC

    The issue is resolved and the service continues to perform as expected.