Resolved -
This incident has now been resolved, the backlog identified earlier has been processed.
Feb 1, 16:06 PST
Monitoring -
We have been processing new occurrences in real-time. There is a backlog from the incident that is actively processing. The system will process this queue in reverse time order at a lower priority than new data until the backlog is cleared.
Feb 1, 14:30 PST
Update -
We are continuing to investigate this issue, and will provide a further update at 1pm PT
Feb 1, 12:02 PST
Investigating -
We are experiencing a processing delay in our occurrence pipeline. We are investigating actively and will post when we have identified the issue.
Feb 1, 09:55 PST
Resolved -
This incident has been resolved.
Jan 31, 09:28 PST
Monitoring -
A fix has been implemented and we're monitoring the results
Jan 31, 09:17 PST
Identified -
The issue has been identified and a fix has been implemented.
Jan 31, 09:08 PST
Investigating -
We are experiencing a processing delay in our occurrence pipeline. We are investigating actively and will post when we have identified the issue.
Jan 31, 08:01 PST
Resolved -
This has now been resolved, apologies for any inconvenience caused.
Jan 30, 11:32 PST
Monitoring -
A fix has been implemented and we are monitoring the results.
Jan 30, 11:15 PST
Investigating -
We are experiencing a processing delay in our occurrence pipeline. We are investigating actively and will post when we have identified the issue.
Jan 30, 10:13 PST
Resolved -
Apologies for any inconvenience caused this issue has now been resolved.
Jan 23, 13:02 PST
Monitoring -
A fix has been implemented and we are monitoring the results.
Jan 23, 11:45 PST
Investigating -
We are experiencing a processing delay in our occurrence pipeline. We are investigating actively and will post when we have identified the issue.
Jan 23, 09:32 PST