Aug 1, 19:46 UTC
Resolved - This incident has been resolved.

Aug 1, 19:13 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Aug 1, 15:40 UTC
Update - We are continuing to work on a fix for this issue.

Aug 1, 14:49 UTC
Identified - The issue has been identified and a fix is being implemented.

Aug 1, 14:22 UTC
Investigating - We are currently investigating this issue.

Aug 1, 14:56 UTC
Resolved - This incident has been resolved.

Jul 31, 12:04 UTC
Monitoring - The error condition has been resolved. We are still working to identify the root cause. We are currently monitoring the situation and will have further updates available soon.

Jul 31, 09:42 UTC
Investigating - We are currently experiencing a service disruption due to what appears to be networking issues in our AWS us-east-1 and eu-west-1 regions. Our database team is working to identify the root cause and implement a solution.

Aug 1, 14:56 UTC
Resolved - This incident has been resolved.

Jul 31, 22:33 UTC
Update - We are continuing to monitor for any further issues.

Jul 31, 22:32 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Jul 31, 22:16 UTC
Investigating - We are currently investigating this issue.

Jul 21, 10:58 UTC
Resolved - This incident has been resolved.

Jul 16, 19:27 UTC
Investigating - We are currently investigating this issue.

Jul 16, 14:20 UTC
Resolved - This incident has been resolved.

Jul 15, 20:14 UTC
Monitoring - There was a 2 minute period of unavailability on the read path in AWS us-east-1 environments. We have since resolved this issue and are monitoring.

Jul 15, 20:13 UTC
Identified - The issue has been identified.