500 errors in application

Incident Report for Superblocks

Resolved

A change was promoted to our ingress controllers in production that prevented requests from being forwarded to all of our upstream services. This would result in the end user seeing a 500 error after a lengthy timeout was hit. This prevented all users from using the platform for 6 minutes while this change persisted in production before it was rolled back.

Posted Apr 16, 2024 - 15:00 EDT