Newsletter
Resolved: 500 errors
  • Home
  • Resolved: 500 errors
incident

On 2026-07-07, between 15:40 and 15:45 (UTC), a service outage caused API requests to return 500 (Internal Server Error) responses on all endpoints.

Impacted behavior:

– All API endpoints were affected, except authentication
– Requests returned a 500 response the underlying data remained intact and unaffected.
– Data write (POST/PUT/PATCH) api calls which returned a 500 error where not processed.

The issue was isolated to the API response layer.

Data write api calls should implement retry on 5xx errors and should have been replayed after the end of the incident based on implemented retry strategies.
Data collection api calls should have resumed after the incident without any data loss.

The issue has been identified and resolved. Service was fully restored at 15:45 (UTC).

We apologize for any inconvenience.