Previous incidents

Resolved Aug 24 at 11:00 AM CEST

Between 7:47 AM and 11:00 AM CEST on August 24, 2025, all API endpoints were unavailable. Monitoring confirmed complete service outage during this window.

The root cause was an upstream provider-side infrastructure issue. Service were resumed after Technical Team implemented the necessary fixes.

Resolved Aug 22 at 09:51 PM CEST

Between 6:30 PM and 9:51 PM CEST on August 22, 2025, production systems experienced an elevated number of HTTP 500 errors. The disruption was traced back to an outage at the provider’s ISP, which caused connectivity issues and service instability.

Service was fully restored once the provider resolved the issue. No changes were deployed on our side during this time.

Between 08:00 AM and 4:00 PM UTC on June 3, 2025, all API endpoints experienced temporary failures, returning either 204 or 500 errors. The issue was caused by an incorrect deployment to our server infrastructure. This push introduced changes that could not be rolled back cleanly, requiring us to manually delete and recreate all production instances.

Importantly, this incident was not related to any external data sources — the root cause was strictly internal and due to an infrastructure mis...