Postmortem -
Read details
Feb 10, 08:32 PST
Resolved -
This incident has been resolved.
Feb 4, 15:21 PST
Monitoring -
A fix has been implemented and we are monitoring the results.
Feb 4, 14:34 PST
Update -
We are deploying the fix to all clusters now. Starting with production -1 environment
Feb 4, 13:41 PST
Update -
We are working towards the fix and are verifying this in a lower environment.
Feb 4, 11:34 PST
Update -
We have identified the database component that caused the issue and are working to restore it at the moment.
Feb 4, 10:46 PST
Identified -
The issue has been identified and team is working on a fix. The issue started at 8:15 PDT
Feb 4, 09:41 PST
Investigating -
We are currently investigating this issue.
Feb 4, 09:38 PST