Service Health
Incident affecting Chronicle Security
Chronicle Security experienced elevated timeout errors across US regions.
Incident began at 2025-01-15 12:30 and ended at 2025-01-15 15:43 (all times are US/Pacific).
Previously affected location(s)
Toronto (northamerica-northeast2)São Paulo (southamerica-east1)Multi-region: us
Date | Time | Description | |
---|---|---|---|
| 15 Jan 2025 | 15:43 PST | The issue with Chronicle Security has been resolved for all affected users as of Wednesday, 2025-01-15 15:30 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
| 15 Jan 2025 | 14:04 PST | Summary: Chronicle Security is experiencing elevated timeout errors across US regions. Description: We are experiencing an issue with Chronicle Security beginning on Wednesday, 2025-01-15 12:30 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2025-01-15 16:30 US/Pacific with current details. Diagnosis: Customers are experiencing timeouts in views and APIs related to rules and detections. Some UI pages related to rules and detection may not load completely. Workaround: None at this time |
- All times are US/Pacific