The issue is fully resolved. All API endpoints are responding normally. The expired TLS certificate has been renewed with automatic renewal configured to prevent recurrence. We've also increased monitoring on the proxy service. We apologize for the disruption.

The root cause was an expired TLS certificate on an internal proxy service. This caused upstream requests to time out, which cascaded into widespread 502 errors across the API. After the initial 502s cleared, quote endpoints continued to fail due to the underlying proxy being unreachable. The certificate has been renewed with automatic renewal in place to prevent recurrence. All endpoints are responding normally. We're monitoring to confirm stability.

We have identified a spike in request volume, which contributed to the elevated error rates previously reported. Additionally, we identified that our service responsible for fetching Binance quotes is experiencing abnormally high response times, further impacting quote-related endpoints. We are actively monitoring the situation and working to stabilize response times. Further updates will follow.

502 errors have been resolved and the majority of endpoints are responding normally. We are still seeing 504 timeouts on quote-related requests. We're continuing to work on that and will update again when there is a change.

Almost all API endpoints are currently returning 502 or 504 errors and the service is effectively down. We're working to restore normal operation and will post updates here as the situation changes.