Incident resolved. log indexing for a few last accounts is in final stages
Posted Nov 03, 2022 - 12:00 IST
Update
We are continuing reingestion for the remaining accounts in the remaining regions.
Posted Nov 03, 2022 - 03:26 IST
Monitoring
We are continuing reingestion for all the remaining accounts in the remaining regions.
Posted Nov 02, 2022 - 22:16 IST
Update
Reingestion of data for affected accounts in ca-central-1 is done.
Posted Nov 02, 2022 - 22:12 IST
Update
Reingestion of data for affected accounts in ap-southeast-2 is also done.
Posted Nov 02, 2022 - 20:19 IST
Update
Reingestion of data for affected accounts in ap-northeast-1 is done.
Posted Nov 02, 2022 - 19:58 IST
Update
We are continuing our work on reingesting data that has been delayed. There are no accounts currently suffering from suspension.
Posted Nov 02, 2022 - 19:50 IST
Update
We are continuing to work on a fix for this issue.
Posted Nov 02, 2022 - 19:19 IST
Update
Except Azure WestEurope all affected accounts are no longer suspended. We are continuing on the remaining region. In addition, we are working on restoring data that may appear to be delayed for some of the affected accounts.
Posted Nov 02, 2022 - 18:56 IST
Update
We are continuing to work on a fix for this issue.
Posted Nov 02, 2022 - 18:54 IST
Identified
We have identified the cause of the wrong account suspensions and are taking steps to resolve it, while in parallel resuming normal operations for the accounts affected.
Posted Nov 02, 2022 - 18:24 IST
Investigating
We are investigating an issue where some of our customers accounts are being wrongly suspended
Posted Nov 02, 2022 - 18:16 IST
This incident affected: AWS Frankfurt (eu-central-1) (Logs Ingestion), AWS Canada (ca-central-1) (Logs Ingestion), AWS Sydney (ap-southeast-2) (Logs Ingestion), AWS London (eu-west-2) (Log Ingestion), Azure Netherlands (West Europe) (Logs Ingestion), Azure Washington (West US 2) (Logs Ingestion), and AWS Tokyo (ap-northeast-1) (Logs Ingestion).