Resolved -
This incident has been resolved.
Jul 8, 19:31 AEST
Monitoring -
A fix has been implemented and we are monitoring the results.
Jul 8, 19:19 AEST
Update -
The problem is happening again, we are troubleshooting it.
Jul 8, 18:29 AEST
Identified -
The issue has been identified and a fix is being implemented.
Jul 8, 17:58 AEST
Monitoring -
A fix has been implemented and we are monitoring the results.
Jul 8, 16:24 AEST
Update -
We are continuing to work on a fix for this issue.
Jul 8, 16:11 AEST
Update -
We are continuing to work on a fix for this issue.
Jul 8, 15:22 AEST
Update -
We are continuing to work on a fix for this issue.
Jul 8, 15:09 AEST
Identified -
The issue has been identified and a fix is being implemented.
Jul 8, 14:40 AEST
Update -
We are continuing to monitor for any further issues.
Jul 8, 14:01 AEST
Update -
We are continuing to monitor for any further issues.
Jul 8, 13:44 AEST
Monitoring -
A fix has been implemented and we are monitoring the results.
Jul 8, 13:07 AEST
Identified -
The issue has been identified and a fix is being implemented.
Jul 8, 13:07 AEST
Investigating -
We are currently investigating this issue.
Jul 8, 12:52 AEST