Resolved -
This incident has been resolved.
All events have been recovered
Jun 5, 11:25 UTC
Update -
The issue has been resolved, and the service is operating normally again.
We are currently reprocessing historical events to fully complete the incident resolution.
Jun 4, 20:43 UTC
Monitoring -
The issue has been resolved, and the service is operating normally again.
We are currently reprocessing historical events to fully complete the incident resolution.
Jun 4, 20:37 UTC
Identified -
The issue has been resolved, and the service is operating normally again.
We are currently reprocessing historical events to fully complete the incident resolution.
Jun 4, 20:37 UTC
Update -
We've identified the issue. Incoming messages and conversations were not affected and continued to work normally throughout the incident.
The issue was limited to a background billing process, which briefly delayed some subscription and invoice updates. No data was lost, and the delayed updates are being processed automatically.
A fix is currently rolling out, and we're monitoring the system until the issue is fully resolved.
Jun 4, 16:52 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jun 4, 16:51 UTC
Identified -
We're investigating delays in receiving and processing new incoming messages across channels. No messages are being lost, and all affected messages will be processed once the issue is resolved. Sending messages and handling of existing conversations remain unaffected.
Jun 4, 16:06 UTC