Resolved -
This incident has been resolved.
Aug 1, 14:44 UTC
Update -
We are continuing to monitor for any further issues.
Aug 1, 14:33 UTC
Update -
The underlying issue has been identified and fixed. Systems are currently recovering, though it may take a short time for all services to return to full capacity. We are continuing to monitor the situation closely.
Aug 1, 14:13 UTC
Update -
We are continuing to monitor for any further issues.
Aug 1, 14:06 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Aug 1, 14:05 UTC
Update -
Our engineering team has identified the root cause of the issue and is actively executing multiple resolution paths to restore service as quickly as possible. Further updates to follow shortly.
Aug 1, 13:25 UTC
Update -
We are continuing to work on a fix for this issue.
Aug 1, 12:47 UTC
Identified -
The issue has been identified and a fix is being implemented.
Aug 1, 12:34 UTC
Update -
We are continuing to investigate this issue.
Aug 1, 11:48 UTC
Update -
We are continuing to investigate this issue.
Aug 1, 11:43 UTC
Update -
We are continuing to investigate this issue.
Aug 1, 11:40 UTC
Update -
We are continuing to investigate this issue.
Aug 1, 11:30 UTC
Investigating -
We are currently investigating this issue.
Aug 1, 11:27 UTC