Resolved -
This incident has been resolved.
Jun 9, 08:44 UTC
Update -
Our engineering team continues to monitor the situation. Thank you for your patience.
Jun 8, 02:06 UTC
Update -
Our engineering team continues to monitor the situation. Thank you for your patience.
Jun 7, 00:15 UTC
Update -
Our engineering team continues to monitor the situation. Thank you for your patience.
Jun 6, 05:57 UTC
Update -
Our Engineering team is continuing to monitor the situation.
Jun 5, 21:35 UTC
Monitoring -
Our Engineering team are continuing to monitor the situation.
Jun 5, 19:27 UTC
Update -
Our Engineering team are continuing to review and monitor the situation.
Jun 5, 15:48 UTC
Update -
Our Engineering team are continuing to roll out a fix and monitor the results. Thank you for your continued patience and we do apologise for the disruptions.
Jun 5, 13:07 UTC
Update -
Our Engineering team are continuing to roll out a fix and monitor the results. Thank you for your continued patience.
Jun 5, 11:27 UTC
Update -
Our Engineering team is rolling out a fix for this issue and monitoring the results.
Jun 5, 10:32 UTC
Identified -
The issue has been identified, and a fix is being implemented.
Jun 5, 09:56 UTC
Investigating -
We are currently investigating reports of 504/long-running SQL queries issues on our platform.
Jun 5, 09:05 UTC