May 4, 23:05 UTC
Resolved - This incident has been resolved.
May 4, 21:28 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 4, 21:24 UTC
Update - We are continuing to work on a fix for this issue.
May 4, 21:20 UTC
Identified - We have deployed a fix and we expect to recover within the next 10 minutes.
May 4, 21:15 UTC
Investigating - We are currently investigating this issue.