Grafana incident

Some Grafana Instances Unavailable

Major Resolved View vendor source →

Grafana experienced a major incident on March 27, 2026 affecting AWS Australia - prod-ap-southeast-2 and AWS Brazil - prod-sa-east-1 and 1 more component, lasting 7h 12m. The incident has been resolved; the full update timeline is below.

Started
Mar 27, 2026, 01:36 PM UTC
Resolved
Mar 27, 2026, 08:48 PM UTC
Duration
7h 12m
Detected by Pingoru
Mar 27, 2026, 01:36 PM UTC

Affected components

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

Update timeline

  1. investigating Mar 27, 2026, 01:36 PM UTC

    We’re currently investigating an issue which is affecting primarily users on the Free tier. Impacted users will be met with a "your Grafana instance is loading" message indefinitely. Our team is actively working to identify the cause and will share an update within 1-2 hours. Thank you for your patience.

  2. investigating Mar 27, 2026, 02:51 PM UTC

    We’re continuing to investigate the issue with Grafana instances. While we don’t have new information to share yet, our team is working to identify the root cause. Next update in 1-2 hours.

  3. investigating Mar 27, 2026, 04:36 PM UTC

    We’re continuing to investigate the issue with Grafana instances. While we don’t have new information to share yet, our team is working to identify the root cause. Next update in 1-2 hours.

  4. identified Mar 27, 2026, 06:10 PM UTC

    We’ve identified the cause of the issue impacting the instances. Our team is currently implementing a fix. We’ll provide another update in 1–2 hours, or sooner, if the situation changes.

  5. monitoring Mar 27, 2026, 08:16 PM UTC

    We’ve implemented a fix and are monitoring the results to confirm the issue is fully resolved. Services may start to recover during this time. We’ll update again in 1 hour.

  6. resolved Mar 27, 2026, 08:48 PM UTC

    This incident has been resolved. Thank you for your patience.