Service Health
Incident affecting Chronicle Security
Multiple Chronicle SIEM operations might be delayed/not working
Incident began at 2024-08-16 01:27 and ended at 2024-08-16 03:45 (all times are US/Pacific).
Previously affected location(s)
Tokyo (asia-northeast1)Mumbai (asia-south1)Singapore (asia-southeast1)Sydney (australia-southeast1)Turin (europe-west12)London (europe-west2)Frankfurt (europe-west3)Zurich (europe-west6)Doha (me-central1)Dammam (me-central2)Tel Aviv (me-west1)Toronto (northamerica-northeast2)
Date | Time | Description | |
---|---|---|---|
| 16 Aug 2024 | 03:45 PDT | The issue with Chronicle SIEM has been resolved for all affected users as of Friday, 2024-08-16 03:30 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
| 16 Aug 2024 | 03:04 PDT | Summary: Multiple Chronicle SIEM operations might be delayed/not working Description: Mitigation work is still underway by our engineering team. We will provide more information by Friday, 2024-08-16 04:30 US/Pacific. Diagnosis: Backstory Customer Management Application Programming Interfaces (APIs) could not be working. Ingestion of GCP logs might be delayed. Cloud Console Page of Chronicle may experience slowness. Workaround: None at this time. |
| 16 Aug 2024 | 02:06 PDT | Summary: Multiple Chronicle SIEM operations might be delayed/not working Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Friday, 2024-08-16 03:15 US/Pacific. Diagnosis: Backstory Customer Management Application Programming Interfaces (APIs) could not be working. Ingestion of GCP logs might be delayed. Cloud Console Page of Chronicle may experience slowness. Workaround: None at this time. |
- All times are US/Pacific