Service Health
Incident affecting Chronicle Security
We are experiencing an issue with Chronicle Security
Incident began at 2024-04-10 07:39 and ended at 2024-04-10 11:35 (all times are US/Pacific).
Previously affected location(s)
Tokyo (asia-northeast1)Mumbai (asia-south1)Sydney (australia-southeast1)London (europe-west2)Frankfurt (europe-west3)Zurich (europe-west6)Dammam (me-central2)Tel Aviv (me-west1)Toronto (northamerica-northeast2)
Date | Time | Description | |
---|---|---|---|
| 10 Apr 2024 | 11:35 PDT | The issue with Chronicle Security has been resolved for all affected users as of Wednesday, 2024-04-10 11:35 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
| 10 Apr 2024 | 10:57 PDT | Summary: We are experiencing an issue with Chronicle Security Description: Mitigation work is ongoing and Engineering is observing some recovery. We do not have an ETA for mitigation at this point and will continue to provide updates on full recovery. We will provide more information by Wednesday, 2024-04-10 12:30 US/Pacific. Diagnosis: Chronicle may be processing ingested data slower than normal and detections on recent data may be impacted, causing some customers to experience data freshness issues. Workaround: None at this time. |
| 10 Apr 2024 | 10:22 PDT | Summary: We are experiencing an issue with Chronicle Security 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 Wednesday, 2024-04-10 11:15 US/Pacific. Diagnosis: Chronicle may be processing ingested data slower than normal and detections on recent data may be impacted, causing some customers to experience data freshness issues. Workaround: None at this time. |
| 10 Apr 2024 | 09:18 PDT | Summary: We are experiencing an issue with Chronicle Security 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 Wednesday, 2024-04-10 11:00 US/Pacific. Diagnosis: Chronicle may be processing ingested data slower than normal and detections on recent data may be impacted, causing some customers to experience data freshness issues. Workaround: None at this time. |
| 10 Apr 2024 | 08:26 PDT | Summary: We are experiencing an issue with Chronicle Security Description: We are experiencing an issue with Chronicle Security. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2024-04-10 09:21 US/Pacific with current details. Diagnosis: Chronicle may be processing ingested data slower than normal and detections on recent data may be impacted, causing some customers to experience data freshness issues. Workaround: None at this time. |
- All times are US/Pacific