Service Health
Incident affecting Chronicle Security
Ingestion delays for small number of Third Party API Feeds while using Chronicle Security in US Multi-regions
Incident began at 2024-04-24 21:21 and ended at 2024-04-25 10:38 (all times are US/Pacific).
Previously affected location(s)
Multi-region: us
Date | Time | Description | |
---|---|---|---|
| 25 Apr 2024 | 10:38 PDT | The issue with Chronicle Security has been resolved as of Thursday, 2024-04-25 10:37 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
| 25 Apr 2024 | 09:57 PDT | Summary: Ingestion delays for small number of Third Party API Feeds while using Chronicle Security in US Multi-regions Description: Mitigation work is taking more time than expected and is currently underway by our engineering team. We will provide more information by Thursday, 2024-04-25 11:30 US/Pacific. Diagnosis: Some Chronicle Security customers in the US may notice ingestion delays for Third Party API Feeds. Our investigation suggests it is impacting a very small number of feeds. The delays in ingested data may surface as delays in detections and other downstream product features. Workaround: None at this time. |
| 25 Apr 2024 | 08:30 PDT | Summary: Ingestion delays for small number of Third Party API Feeds while using Chronicle Security in US Multi-regions Description: Mitigation work is taking more time than expected and is currently underway by our engineering team. We will provide more information by Thursday, 2024-04-25 10:00 US/Pacific. Diagnosis: Some Chronicle Security customers in the US may notice ingestion delays for Third Party API Feeds. Our investigation suggests it is impacting a very small number of feeds. The delays in ingested data may surface as delays in detections and other downstream product features. Workaround: None at this time. |
| 25 Apr 2024 | 06:52 PDT | Summary: Ingestion delays for small number of Third Party API Feeds while using Chronicle Security in US Multi-regions Description: Mitigation work is taking more time than expected and is currently underway by our engineering team. We will provide more information by Thursday, 2024-04-25 08:30 US/Pacific. Diagnosis: Some Chronicle Security customers in the US may notice ingestion delays for Third Party API Feeds. Our investigation suggests it is impacting a very small number of feeds. The delays in ingested data may surface as delays in detections and other downstream product features. Workaround: None at this time. |
| 25 Apr 2024 | 03:50 PDT | Summary: Ingestion delays for small number of Third Party API Feeds while using Chronicle Security in US Multi-regions Description: Mitigation work is currently underway by our engineering team. The mitigation is expected to complete by Thursday, 2024-04-25 07:00 US/Pacific. We will provide more information by Thursday, 2024-04-25 07:00 US/Pacific. Diagnosis: Some Chronicle Security customers in the US may notice ingestion delays for Third Party API Feeds. Our investigation suggests it is impacting a very small number of feeds. The delays in ingested data may surface as delays in detections and other downstream product features. Workaround: None at this time. |
| 25 Apr 2024 | 00:01 PDT | Summary: Ingestion delays for small number of Third Party API Feeds while using Chronicle Security in US Multi-regions Description: We are experiencing an issue with Chronicle Security beginning at Wednesday, 2024-04-24 17:39 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2024-04-25 04:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Some Chronicle Security customers in the US may notice ingestion delays for Third Party API Feeds. Our investigation suggests it is impacting a very small number of feeds. The delays in ingested data may surface as delays in detections and other downstream product features. Workaround: None at this time. |
| 24 Apr 2024 | 23:25 PDT | Summary: Ingestion delays for Third Party API Feeds while using Chronicle Security in US Multi-regions Description: We are experiencing an issue with Chronicle Security beginning at Wednesday, 2024-04-24 17:39 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2024-04-25 04:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Some Chronicle Security customers in the US may notice ingestion delays for Third Party API Feeds. The delays in ingested data may surface as delays in detections and other downstream product features. Workaround: None at this time. |
| 24 Apr 2024 | 21:51 PDT | Summary: Ingestion delays for Third Party API Feeds for Chronicle customers in the US Description: We are experiencing an issue with Chronicle Security beginning at Wednesday, 2024-04-24 17:39 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2024-04-24 23:30 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Some Chronicle customers in the US may notice ingestion delays for Third Party API Feeds. The delays in ingested data may surface as delays in detections and other downstream product features. Workaround: None at this time. |
- All times are US/Pacific