Service Health
Incident affecting Chronicle Security, Mandiant Managed Defense
This incident is being merged with an existing incident. All future updates will be provided there: https://status.cloud.google.com/incidents/PtQCvMMdqsRLZLbdC11p
Incident began at 2024-06-26 07:27 and ended at 2024-06-26 22:09 (all times are US/Pacific).
Previously affected location(s)
GlobalMulti-region: us
Date | Time | Description | |
---|---|---|---|
| 26 Jun 2024 | 22:09 PDT | This incident is being merged with an existing incident. All future updates will be provided there: https://status.cloud.google.com/incidents/PtQCvMMdqsRLZLbdC11p |
| 26 Jun 2024 | 19:25 PDT | Summary: Chronicle Security is experiencing data ingestion delay for some 3rd party API feeds in the US region. Description: We believe the issue with Chronicle Security, Mandiant Managed Defense is partially resolved. Full resolution (backlog clearance) is expected to complete by Thursday, 2024-06-27 09:00 US/Pacific. We will provide an update by Thursday, 2024-06-27 00:00 US/Pacific with details on the progress. Diagnosis: Data ingestion is delayed by > 17 hours for some 3rd party API feeds. Workaround: None at this time |
| 26 Jun 2024 | 15:24 PDT | Summary: Chronicle Security is experiencing data ingestion delay for some 3rd party API feeds in the US region. Description: Mitigation work is currently underway by our engineering team. Mandiant Managed Defense is also impacted due this incident. We do not have an ETA for mitigation at this point. We will provide more information by Wednesday, 2024-06-26 19:30 US/Pacific. Diagnosis: Data ingestion is delayed by > 17 hours for some 3rd party API feeds. Workaround: None at this time |
| 26 Jun 2024 | 11:15 PDT | Summary: Chronicle Security is experiencing data ingestion delay for some 3rd party API feeds in the US region. Description: Mitigation work is currently underway by our engineering team. Mandiant Managed Defense is also impacted due this incident. We do not have an ETA for mitigation at this point. We will provide more information by Wednesday, 2024-06-26 15:30 US/Pacific. Diagnosis: Data ingestion is delayed by > 17 hours for some 3rd party API feeds. Workaround: None at this time |
| 26 Jun 2024 | 09:22 PDT | Summary: Chronicle Security is experiencing data ingestion delay for some 3rd party API feeds in the US region. 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-06-26 11:30 US/Pacific. Diagnosis: Data ingestion is delayed by > 17 hours for some 3rd party API feeds. Workaround: None at this time |
| 26 Jun 2024 | 09:18 PDT | Summary: Chronicle Security is experiencing data ingestion delay for some 3rd party API feeds in the US region. 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-06-26 11:30 US/Pacific. Diagnosis: Data ingestion is delayed by > 17 hours for some 3rd party API feeds. Workaround: None at this time |
| 26 Jun 2024 | 07:57 PDT | Summary: Chronicle Security is experiencing data ingestion delay for some 3rd party API feeds in the US region. Description: We are experiencing an issue with Chronicle Security beginning on Wednesday, 2024-06-26 06:40 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2024-06-26 09:30 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Data ingestion is delayed by > 17 hours for some 3rd party API feeds. Workaround: None at this time |
- All times are US/Pacific