incident
On 2026-07-30, from 13:24 (UTC) until 13:36 (UTC) some api calls returned a 500 or 502 error.
Impacted behavior:
– Any api call can be impacted
– Write operation will have to be performed again
The issue was isolated to the API network infrastructure.
No data were lost throughout the outage.
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 13:36 (UTC).
We apologize for any inconvenience.