Update 21:30 UTC — Resolved. The upstream network incident at our hosting provider has been confirmed resolved, and all endpoints have been healthy since 18:10 UTC. Total customer impact was three windows of intermittent 502/503 errors between 17:16 and 18:10 UTC, roughly 2–8 minutes each. We apologize for the disruption.

Update 18:50 UTC — Service has recovered. Root cause: an upstream network incident at our hosting provider intermittently disrupted outbound connectivity between our API and database, causing waves of 502/503 errors at 17:16, 17:57, and 18:05 UTC (a few minutes each). We applied a network configuration change at approximately 18:20 UTC to bypass the affected path, and all endpoints have been healthy since. We are monitoring for recurrence and will resolve this incident after a stable observation window.

We are investigating widespread 502/503 errors affecting API, Authentication, Data, and Events endpoints beginning at 17:16 UTC. Errors are intermittent and affect all regions. The website remains operational. We are working to identify the root cause.