Incident History

Azure PrivateLink 503 errors on Mimir and Tempo

From 11:00 UTC to 22:09 UTC, customers of Mimir and Tempo using Azure PrivateLink were unable to access services and received 503 errors. This happened because part of our traffic routing setup was unintentionally shut down too early. Once identified, we restored the service and traffic returned to normal.

1758179843 - 1758179843 Resolved

Synthetic monitoring API outage - us-central2

The incident is resolved, API in us-central2 is available again as of 21:01 UTC

1758056353 - 1758057393 Resolved

Loki read and write outage in us-central2

There were read and write outages in the us-central2 region for Loki from 16:57 to 17:04 UTC. The issue is now resolved.

1758043270 - 1758043270 Resolved

hgapi down in prod-us-west-0

This incident has been resolved.

1757958941 - 1757960271 Resolved

Access to Unified-Storage Database in Us-Central-2 Broken.

This incident has been resolved.

1757946720 - 1757953639 Resolved

Metrics Aggregation - Degraded Performance

This incident has been resolved.

1757703103 - 1757721663 Resolved

K6 Experiencing Degraded Performance

This incident has been resolved.

1757608836 - 1757612241 Resolved

Hosted Grafana - Connection Errors and Slow Load Times

We continue to observe a period of stability. At this time, we are considering this issue resolved.

1757540875 - 1757605341 Resolved

k6 test run performance degradation that may affect some users

This incident has been resolved.

1757500171 - 1757590647 Resolved

Test runs in Grafana Cloud k6 are missing metrics/time-series

This incident has been resolved.

1756814801 - 1756821236 Resolved
⮜ Previous Next ⮞