Resolved -
The issue has been resolved. We are sorry for the disruption and inconvenience.
Jan 26, 12:08 EST
Update -
We are continuing to monitor for any further issues.
Jan 26, 03:53 EST
Update -
We are continuing to monitor for any further issues.
Jan 26, 00:20 EST
Update -
We have implemented a fix for the issue and are monitoring the recovery.
Jan 25, 18:21 EST
Monitoring -
We have implemented a fix for the issue and are monitoring the recovery.
Jan 25, 16:05 EST
Update -
Our engineering team is continuing to work on a fix for this issue.
Jan 25, 14:37 EST
Update -
Our engineering team is continuing to work on a fix for this issue.
Jan 25, 12:28 EST
Update -
Our engineering team is continuing to work on a fix for this issue.
Jan 25, 09:56 EST
Identified -
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
Jan 25, 08:52 EST
Investigating -
We are aware of and actively investigating delays that are impacting scan processing for certain users. We will provide periodic updates as our engineers continue working on this issue.
Jan 25, 06:56 EST
Update -
We are continuing to monitor for any further issues.
Jan 25, 03:11 EST
Update -
We are continuing to monitor for any further issues.
Jan 24, 22:16 EST
Monitoring -
We have implemented a fix for the issue and are monitoring the recovery.
Jan 24, 17:32 EST
Update -
Our engineering team continues to investigate this issue.
Jan 24, 12:05 EST
Investigating -
We are aware of and actively investigating delays that are impacting scan processing for certain users. We will provide periodic updates as our engineers continue working on this issue.
Jan 24, 09:04 EST
Update -
We are continuing to monitor for any further issues.
Jan 24, 04:30 EST
Monitoring -
We have implemented a fix for the issue and are monitoring the recovery.
Jan 23, 18:02 EST
Update -
We are continuing to work on a fix for this issue.
Jan 23, 15:24 EST
Update -
We are continuing to work on a fix for this issue.
Jan 23, 12:01 EST
Identified -
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
Jan 23, 12:01 EST