Google Cloud MAJOR

Chronicle Security and Chronicle SOAR experiencing high Remote Procedure Calls (RPC) error rate in Multiregion/us

February 29, 2024 · 07:50 AM UTC – 05:50 PM UTC · Duration: 10h

Affected Services

Chronicle SecurityChronicle SOAR

Timeline

08:53 PM
A mini incident report has been posted on the Google Cloud Service Health Dashboard at https://status.cloud.google.com/incidents/JAxa64hv45yMYzCpqx1T
02:29 PM
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.
01:26 PM
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
12:06 PM
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
11:54 AM
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