Grafana incident

Query Caching - Degraded Performance

Resolved after 1 hour 34 minutes, affecting AWS Germany - prod-eu-west-2 and AWS US East (OH) - prod-us-east-0 and 1 more, on April 17, 2026.

monitoring Apr 17, 2026, 10:09 PM UTC

Currently prod-us-east-0 and prod-eu-west-3 have recovered, and we are continuing to monitor prod-us-central-0 which is in the process of recovery.

Started
Apr 17, 2026, 09:23 PM UTC
Resolved
Apr 17, 2026, 10:58 PM UTC
Duration
1h 34m
Detected by Pingoru
Apr 17, 2026, 09:23 PM UTC

Affected components

AWS Germany - prod-eu-west-2AWS US East (OH) - prod-us-east-0Azure Netherlands - prod-eu-west-3GCP US Central - prod-us-central-0

Update timeline

  1. investigating Apr 17, 2026, 09:23 PM UTC

    As of 20:52 UTC, we are currently investigating degraded Query Caching performance in multiple regions. For datasources where query caching is configured, some queries may take longer than usual. Our team is actively working to identify the cause. Thank you for your patience.

  2. monitoring Apr 17, 2026, 10:09 PM UTC

    Currently prod-us-east-0 and prod-eu-west-3 have recovered, and we are continuing to monitor prod-us-central-0 which is in the process of recovery.

  3. resolved Apr 17, 2026, 10:58 PM 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.

Add your stack →