Cortex - read/write path disruption
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
resolved since 03:02UTC
Spanning from November 10th, 18:00 UTC to November 11th, 22:00 UTC, Synthetic Monitoring experienced degraded browser check performance due to a faulty release that has been rolled back.
This impacted all regions, specifically the probes. The API itself experienced no issues.
This incident has been resolved.
Test runs are now working as expected. The duration of this incident was roughly 30 minutes. The test runs were not able to start, and the app and the API were not accessible.
The incident is resolved as of 14:35 UTC.
From Oct 31st 17:40 UTC to Nov 3rd 14:50 UTC:
Due to some internal auth issues, the components evaluating loki-managed rules failed to push the evaluated recording and alert rules to the metrics endpoint for some tenants.
This incident has been resolved.
From approximately 16:30-8:15 UTC, a configuration change inadvertently removed a required headless service for hosted traces in one of our production regions. This caused elevated error rates and increased service-level objective (SLO) burn for the trace ingestion pathway. The underlying issue was a mismatch in internal configuration references following a prior migration. Re-enabling the headless service restored normal operation.