Service Health
Incident affecting Chronicle Security
[Chronicle Security] Detection page may not be loading
Incident began at 2024-07-16 04:00 and ended at 2024-07-16 05:36 (all times are US/Pacific).
Previously affected location(s)
Tokyo (asia-northeast1)Mumbai (asia-south1)Singapore (asia-southeast1)Sydney (australia-southeast1)Turin (europe-west12)London (europe-west2)Frankfurt (europe-west3)Zurich (europe-west6)Doha (me-central1)Dammam (me-central2)Tel Aviv (me-west1)Toronto (northamerica-northeast2)
Date | Time | Description | |
---|---|---|---|
| 16 Jul 2024 | 05:36 PDT | The issue with Chronicle Security has been resolved for all affected projects as of Tuesday, 2024-07-16 05:36 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
| 16 Jul 2024 | 04:41 PDT | Summary: [Chronicle Security] Detection page may not be loading Description: Mitigation work is currently underway by our engineering team. The mitigation is expected to complete by Tuesday, 2024-07-16 06:00 US/Pacific. We will provide more information by Tuesday, 2024-07-16 06:00 US/Pacific. Diagnosis: Detection page may not be loading Workaround: None at this time. |
| 16 Jul 2024 | 04:30 PDT | Summary: [Chronicle Security] Detection page may not be loading Description: We are experiencing an issue with Chronicle Security. Our engineering team continues to investigate the issue. We will provide an update by Tuesday, 2024-07-16 06:00 US/Pacific with current details. Diagnosis: Detection page may not be loading . Workaround: None at this time. |
- All times are US/Pacific