Over a 24 hour period, there were a number of long delays (> 60 seconds) for checks to complete, which may have caused timeouts for users depending on their client timeout configurations. These checks did all complete and update any relevant status in the UI and via GitHub, though they may have failed CI jobs depending on configuration.
We apologize for any disruption this may have caused for your day-to-day operations, and we have put a fix in place (a missing database index) to avoid future problems, as well as put monitoring in place to identify these problems before causing problems for users.
No components marked as affected
Resolved
Over a 24 hour period, there were a number of long delays (> 60 seconds) for checks to complete, which may have caused timeouts for users depending on their client timeout configurations. These checks did all complete and update any relevant status in the UI and via GitHub, though they may have failed CI jobs depending on configuration.
We apologize for any disruption this may have caused for your day-to-day operations, and we have put a fix in place (a missing database index) to avoid future problems, as well as put monitoring in place to identify these problems before causing problems for users.