Brief API Outage — 502 Bad Gateway

All affected services (API, Payments, Downloads) have recovered and are responding normally. The next health check at 04:56 UTC confirmed full recovery across all endpoints. No further action required.

Root cause identified as a transient proxy restart on the API server. The disruption lasted less than 5 minutes and was limited to a single health check cycle. No user-facing requests were dropped during this window.

Our monitoring detected 502 Bad Gateway errors on the API, Payments, and Downloads services. All three endpoints returned status code 502 simultaneously at 04:51 UTC, indicating a brief upstream proxy disruption. Website, Documentation, and Marketplace were unaffected.