Grafana incident

Query Caching - Degraded Performance

Minor Resolved View vendor source →
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 - 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

Looking to track Grafana downtime and outages?

Pingoru polls Grafana's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Grafana reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Grafana alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Grafana for free

5 free monitors · No credit card required