What happened:From June 1 12:00am UTC to June 1 08:45am UTC, one of the component serving the public monitoring experienced some delays and a growing backlog of unprocessed messages.
Impact:No data was lost. The only impact for customers could have been a delay between the detection of a secret and the moment the corresponding incident was created in the customer's dashboard.
The problem is now fixed, the faulty component was able to re-start and to process the backlog of messages.
No components marked as affected
Resolved
What happened:From June 1 12:00am UTC to June 1 08:45am UTC, one of the component serving the public monitoring experienced some delays and a growing backlog of unprocessed messages.
Impact:No data was lost. The only impact for customers could have been a delay between the detection of a secret and the moment the corresponding incident was created in the customer's dashboard.
The problem is now fixed, the faulty component was able to re-start and to process the backlog of messages.