Sage incident

Sage 200 Standard (UKI) - Operational

Major Resolved View vendor source →

Sage experienced a major incident on July 1, 2026 affecting Sage 200 Standard (UKI), lasting 1d 9h. The incident has been resolved; the full update timeline is below.

Started
Jul 01, 2026, 09:28 AM UTC
Resolved
Jul 02, 2026, 07:22 PM UTC
Duration
1d 9h
Detected by Pingoru
Jul 01, 2026, 09:28 AM UTC

Affected components

Sage 200 Standard (UKI)

Update timeline

  1. investigating Jul 01, 2026, 09:28 AM UTC

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

  2. investigating Jul 01, 2026, 09:40 AM UTC

    We have identified an issue preventing customers in the UK and Ireland from accessing the service. Customers are being presented with an error message: "The request channel timed out while waiting for a reply." Approximately 18 customers have reported the issue. We are currently investigating.

  3. monitoring Jul 01, 2026, 10:07 AM UTC

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

  4. monitoring Jul 01, 2026, 03:08 PM UTC

    The service continues to be available and performing as expected. We are implementing a permanent fix and will carry out this work on July 1st between 20:00 BST and 22:00 BST. During this period, customers may experience a brief period of degraded performance. We appreciate your patience and understanding as we complete this work.

  5. monitoring Jul 01, 2026, 07:31 PM UTC

    The maintenance has been completed and the service continues to be available and performing as expected. We continue to closely monitor the service.

  6. monitoring Jul 02, 2026, 10:32 AM UTC

    While the service continues to be available and performing as expected, and under close monitoring, we will carry out a maintenance on July 2nd between 20:00 BST and 22:00 BST. During this period, customers may experience a brief period of degraded performance. We appreciate your patience and understanding as we complete this work.

  7. resolved Jul 02, 2026, 07:22 PM UTC

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