Incident History

Cloudwatch datasource query issues on cluster GPC US central

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

1744123946 - 1744358624 Resolved

Degraded Performance of Adaptive Metrics in GCP US Central

This incident has been resolved.

1744120879 - 1744132748 Resolved

Log ingestion rate limit issue in AWS Germany (logs-prod-012)

Between 2025-04-07:13:00:00UTC and 2025-04-08:14:00:00UTC some customers in AWS Germany (logs-prod-012) have had their ingestion rate limits incorrectly lowered, causing affected customers to hit rate limits writing their logs. The correct rate limits have been reinstated and we can confirm affected customers are no longer being rate limited.

1744117410 - 1744117410 Resolved

Multiple components of Grafana down

This incident has been resolved.

1744090921 - 1744096847 Resolved

Intermittent 500 Errors for Log Queries

Some Loki Queries responded with a 500 Response Code, between 06:45 - 7:15UTC.

1744017237 - 1744017237 Resolved

Hosted Grafana Instance Creation Failures in ap-southeast-1 (Singapore)

This incident has been resolved.

1743950534 - 1743961507 Resolved

Instances on "Fast" experiencing issues querying the Tempo datasources

The fix has been rolled out on our "fast" release channel. At this point, we are considering the incident resolved.

1743693492 - 1743729906 Resolved

Grafana Cloud: SAML UI Role mapping

Engineering has rolled out a fix for this issue. At this point, we are considering the incident resolved.

1743613707 - 1743730047 Resolved

Grafana Cloud: SAML UI Role Mapping

Engineering has released a fix and as of 0600 UTC, customers should no longer experience the inability to change SAML role mapping. At this time, we are considering this issue resolved. No further updates.

1743531278 - 1743575572 Resolved

Hosts unreachable for instances in prod-sa-east-1

From 6:23 UTC to 6:39 UTC, we became aware of an issue with instances in the prod-sa-east-1 cluster. Users experiencing this issue may have encountered with requests failing for instances in this cluster.

This has stabilised and customers should no longer experience this issue.

1743148757 - 1743148757 Resolved
⮜ Previous Next ⮞