Between 06:03 and 07:11 UTC on 12 August 2026, a portion of requests to the Invopop API returned HTTP 500 errors. Roughly one in three requests was affected; retries during this period generally succeeded.
The cause was an internal connection between two of our services being routed incorrectly following a routine infrastructure change, which caused authentication checks to fail on one of three API authorisation instances. Service was fully restored at 07:11 UTC by replacing the affected instance.
No data was lost or altered, and no action is required from customers. We have identified the underlying cause and are rolling out a change to our internal service connections to prevent it recurring.
Resolved
Between 06:03 and 07:11 UTC on 12 August 2026, a portion of requests to the Invopop API returned HTTP 500 errors. Roughly one in three requests was affected; retries during this period generally succeeded.
The cause was an internal connection between two of our services being routed incorrectly following a routine infrastructure change, which caused authentication checks to fail on one of three API authorisation instances. Service was fully restored at 07:11 UTC by replacing the affected instance.
No data was lost or altered, and no action is required from customers. We have identified the underlying cause and are rolling out a change to our internal service connections to prevent it recurring.
Identified
We’ve identified the source of the partial outage, causing some API calls to fail while others succeeded. We’ve removed the affected instance and are implementing a permanent fix.
Investigating
We're currently investigating an incident that may prevent usage of API and Console
