Sage incident

Sage Intacct - Operational

Resolved after 6 hours 36 minutes, affecting Sage Intacct and Sage Intacct and 1 more, on May 11, 2026.

resolved May 11, 2026, 08:47 AM UTC

The incident was resolved at 07:54 UTC on the 11th of May after we applied a fix that rolled back the SSO changes introduced by the deployment. Customers have confirmed that they are able to log using SSO without issues. We will follow up with remediation steps to prevent this issue from reoccurring in the future. No further communications will be sent.

Started
May 11, 2026, 02:11 AM UTC
Resolved
May 11, 2026, 08:47 AM UTC
Duration
6h 36m
Detected by Pingoru
May 11, 2026, 02:11 AM UTC

Affected components

Sage IntacctSage IntacctSage IntacctSage Intacct

Update timeline

  1. investigating May 11, 2026, 02:11 AM UTC

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

  2. identified May 11, 2026, 02:27 AM UTC

    We have identified an issue preventing a subset of customers globally who have SSO enabled from accessing the service. We are currently investigating.

  3. identified May 11, 2026, 07:01 AM UTC

    We have identified the cause of the issue and are currently working on a fix. We apologise for any inconvenience this might cause.

  4. monitoring May 11, 2026, 08:10 AM UTC

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

  5. resolved May 11, 2026, 08:47 AM UTC

    The incident was resolved at 07:54 UTC on the 11th of May after we applied a fix that rolled back the SSO changes introduced by the deployment. Customers have confirmed that they are able to log using SSO without issues. We will follow up with remediation steps to prevent this issue from reoccurring in the future. No further communications will be sent.

Your product runs on more than Sage

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →