Previous incidents

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...

On April 30 10:00am UTC, our production infrastructure faced a critical failure due to unhandled rate limiting in our scraping systems. This resulted in all API endpoints returning HTTP 500 errors with no data being served.

For two full days (April 30 to May 2), our API was completely unavailable.

On May 2, we deployed a degraded mode: only the most valuable portion of the data (approximately one-third of the usual results) was returned through fallback logic. While this helped partially re...