Grafana incident

Grafana Loki Log Query Issues

Resolved after 1 hour 56 minutes, affecting AWS Australia - prod-au-southeast-1 and AWS Brazil - prod-sa-east-1 and 1 more, on May 29, 2026.

monitoring May 29, 2026, 10:28 AM UTC

We have identified the cause of this incident and a fix has been applied. Normal functions are returning. We are currently monitoring the recovery process.

Started: May 29, 2026, 09:03 AM UTC
Resolved: May 29, 2026, 10:59 AM UTC
Duration: 1h 56m
Detected by Pingoru: May 29, 2026, 09:03 AM UTC

Affected components

AWS Australia - prod-au-southeast-1AWS Brazil - prod-sa-east-1AWS Canada - prod-ca-east-0AWS Germany - prod-eu-west-2AWS UAE - prod-me-central-1AWS India - prod-ap-south-1AWS Japan - prod-ap-northeast-0AWS Singapore - prod-ap-southeast-1AWS Sweden - prod-eu-north-0AWS US West - prod-us-west-0

Update timeline

investigating May 29, 2026, 09:03 AM UTC

We’re currently investigating an issue affecting Loki queries in Grafana. We have had reports from customers showing the logs are not loading or showing missing logs. Our team is actively working to identify the cause. Thank you for your patience.
monitoring May 29, 2026, 10:28 AM UTC

We have identified the cause of this incident and a fix has been applied. Normal functions are returning. We are currently monitoring the recovery process.
resolved May 29, 2026, 10:59 AM UTC

This incident has been resolved.

Your product runs on more than Grafana

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.