Resolved -
This incident is now resolved.
The backlog has been handled and system is working as intended.
Dec 2, 07:13 UTC
Update -
We are continuing to monitor for further issues while working on clearing the backlog of sent in documents.
The backlog will be dealt with throughout the day.
Dec 1, 07:43 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
We are dealing with the backlog of sent in documents and will generate the reports throughout the day.
Nov 30, 12:48 UTC
Update -
The issue has been identified and we are working on a solution. The current estimate is that this will take less than 1 hour to solve.
All documents sent in are being queued and will get a report once the incident is over.
Next update in 1 hour.
Nov 30, 12:12 UTC
Update -
The issue has been identified and we are working on a solution. The current estimate is that this will take 1 hour to solve.
All documents sent in are being queued and will get a report once the incident is over.
Next update in 1 hour.
Nov 30, 11:09 UTC
Update -
The issue has been identified and we are working on a solution. The current estimate is that this will take 2 hours to solve.
All documents sent in are being queued and will get a report once the incident is over.
Next update in 1 hour.
Nov 30, 10:08 UTC
Update -
The issue has been identified and we are working on a solution. The current estimate is that this will take 2+ hours to solve.
All documents sent in are being queued and will get a report once the incident is over.
Next update in 1 hour.
Nov 30, 09:09 UTC
Identified -
The issue has been identified and we are working on a solution. The current estimate is that this will take 3+ hours to solve.
All documents sent in are being queued and will get a report once the incident is over.
Next update in 1 hour.
Nov 30, 08:08 UTC
Update -
We are continuing to investigate this issue.
Nov 30, 07:34 UTC
Investigating -
We are currently investigating this issue.
Nov 30, 06:30 UTC