Fiftytwo incident

Receipt API instability

Minor Resolved View vendor source →

Fiftytwo experienced a minor incident on March 26, 2026 affecting Receipt API, lasting 8h 20m. The incident has been resolved; the full update timeline is below.

Started
Mar 26, 2026, 07:45 AM UTC
Resolved
Mar 26, 2026, 04:05 PM UTC
Duration
8h 20m
Detected by Pingoru
Mar 26, 2026, 07:45 AM UTC

Affected components

Receipt API

Update timeline

  1. investigating Mar 26, 2026, 07:45 AM UTC

    We are currently investigating an issue where requests to the API is responding with Http Status 502

  2. identified Mar 26, 2026, 08:56 AM UTC

    We have identified the cause and are looking into fixing it.

  3. identified Mar 26, 2026, 10:43 AM UTC

    We are verifying the fix and deploying it soon. All ordinary usages should not be affected - only a corner case.

  4. monitoring Mar 26, 2026, 01:55 PM UTC

    We are working on a fix that will be hotfixed to the currently deployed application. A note of this will happen when it is done. For now the application is in a better state, but is being actively monitored.

  5. resolved Mar 26, 2026, 04:05 PM UTC

    We have pushed a fix to the Receipt API, resulting in a max allowed Limit on Get requests at 100.