Service Health
Incident affecting Chronicle Security, Chronicle SOAR
Chronicle Security and Chronicle SOAR experiencing high Remote Procedure Calls (RPC) error rate in Multiregion/us
Incident began at 2024-02-28 23:50 and ended at 2024-02-29 09:50 (all times are US/Pacific).
Previously affected location(s)
Multi-region: us
Date | Time | Description | |
---|---|---|---|
| 29 Feb 2024 | 12:53 PST | A mini incident report has been posted on the Google Cloud Service Health Dashboard at https://status.cloud.google.com/incidents/JAxa64hv45yMYzCpqx1T |
| 29 Feb 2024 | 06:29 PST | The issue with Chronicle Security, Chronicle SOAR has been resolved for all affected users as of Thursday, 2024-02-29 06:00 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
| 29 Feb 2024 | 05:26 PST | Summary: Chronicle Security and Chronicle SOAR experiencing high Remote Procedure Calls (RPC) error rate in Multiregion/us 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 Thursday, 2024-02-29 07:00 US/Pacific. Diagnosis: Impacted users may experience high failure rate for Backstory API calls Workaround: None at this time |
| 29 Feb 2024 | 04:06 PST | Summary: Chronicle Security and Chronicle SOAR experiencing high Remote Procedure Calls (RPC) error rate in Multiregion/us 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 Thursday, 2024-02-29 05:40 US/Pacific. Diagnosis: Impacted users may experience high failure rate for Backstory API calls Workaround: None at this time |
| 29 Feb 2024 | 03:54 PST | Summary: High Remote Procedure Calls (RPC) error rate in Multiregion/us Description: We are experiencing an issue with Chronicle Security and Chronicle SOAR connectors beginning on Wednesday, 2024-02-28 23:50 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2024-02-29 04:30 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Impacted users may experience high failure rate for Backstory API calls Workaround: None at this time |
- All times are US/Pacific