Grafana Outage History

Grafana major outage View live status →

There were 52 Grafana outages since February 25, 2026 totaling 488h 19m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.grafana.com

Minor February 27, 2026

Trace querying issue in all Tempo clusters

Detected by Pingoru
Feb 27, 2026, 01:46 PM UTC
Resolved
Feb 27, 2026, 11:38 PM UTC
Duration
9h 51m
Affected: AWS Australia - prod-ap-southeast-2: QueryingAWS Brazil - prod-sa-east-1: QueryingAWS Canada - prod-ca-east-0: QueryingAWS Germany - prod-eu-west-2: QueryingAWS India - prod-ap-south-1: QueryingAWS Japan - prod-ap-northeast-0: QueryingAWS Singapore - prod-ap-southeast-1: QueryingAWS Sweden - prod-eu-north-0: QueryingAWS US East - prod-us-east-0: QueryingAWS US West - prod-us-west-0: QueryingAzure Germany - prod-eu-west-1: QueryingAzure Netherlands - prod-eu-west-3: QueryingAzure US Central - us-central2: QueryingGCP Australia - prod-au-southeast-0: QueryingGCP Belgium - prod-eu-west-0: QueryingGCP Brazil - prod-sa-east-0: QueryingGCP India - prod-ap-south-0: QueryingGCP Singapore - prod-ap-southeast-0: QueryingGCP UK - prod-gb-south-0: QueryingGCP US Central - prod-us-central-0: QueryingAWS US East - prod-us-east-2: QueryingGCP US Central - prod-us-central-5: QueryingAWS Ireland - prod-eu-west-6: Querying
Timeline · 3 updates
  1. investigating Feb 27, 2026, 01:46 PM UTC

    We're currently working on an issue where portions of data may be temporarily unretrievable, affecting a small percentage of tenants in all Tempo clusters.

  2. identified Feb 27, 2026, 07:27 PM UTC

    Our team has identified the issue, and are in the process of testing a fix.

  3. resolved Feb 27, 2026, 11:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 25, 2026

Grafana Cloud Metrics - Intermittent Write Latency in prod-us-central, prod-us-central-5, and prod-eu-west-0

Detected by Pingoru
Feb 25, 2026, 07:54 PM UTC
Resolved
Mar 17, 2026, 06:22 PM UTC
Duration
19d 22h
Affected: GCP Belgium - prod-eu-west-0: IngestionGCP US Central - prod-us-central-0: IngestionGCP Belgium - prod-eu-west-0: IngestionGCP US Central - prod-us-central-5: Ingestion
Timeline · 8 updates
  1. investigating Feb 25, 2026, 07:54 PM UTC

    Since February 19, we have been investigating an intermittent issue causing increased write latency in the prod-us-central-0 and prod-us-central-5 regions. The issue does not affect all traffic but may result in delayed write operations for some customers. Our engineering team is actively working to identify the root cause and stabilize performance. We will share additional updates as progress is made.

  2. investigating Feb 26, 2026, 04:23 PM UTC

    We have begun rolling out mitigation steps to reduce write latency in the prod-us-central-0 and prod-us-central-5 regions. While these measures are expected to improve performance, we are continuing to investigate the underlying root cause of the issue. We will provide additional updates as more information becomes available.

  3. monitoring Feb 27, 2026, 02:55 PM UTC

    We've implemented mitigation in place and are continuing to monitoring and investigating this issue.

  4. monitoring Feb 27, 2026, 10:05 PM UTC

    We are continuing to investigate this issue alongside the CSP. Any notable updates will continue to be shared here for tracking.

  5. monitoring Mar 05, 2026, 10:22 PM UTC

    We are continuing to investigate this issue alongside the CSP, and have taken steps to escalate through the appropriate channels. The mitigation in place continues to work as expected, and any notable updates will continue to be shared here for tracking.

  6. monitoring Mar 06, 2026, 08:53 PM UTC

    We have seen an increase in latency in our cloud providers services, and are rolling out a change to mitigate the issue. We are monitoring.

  7. monitoring Mar 06, 2026, 09:44 PM UTC

    We are rolling out a mitigation across the environments in these regions, and preemptively where possible to ensure it doesn’t spread elsewhere.

  8. resolved Mar 17, 2026, 06:22 PM UTC

    This incident is now resolved. During the incident the Cloud Metrics platform experienced intermittent latency spikes communicating with a backend cloud service in the prod-us-central-0 and prod-us-central-5 regions. During the incident the internal CSP-facing issue was escalated to a P1. After determining the scope of the latency spikes was limited to only one availability zone, the team mitigated the situation by migrating all write traffic from to the single nearly unaffected availability zone. As the CSP service team attempted to remedy the situation, the situation became worse and began affecting the previously unaffected zone. Given this, another mitigation path was needed. Changing the connection strategy employed by Cloud Metrics to a different method was deployed to all environments, stabilizing the write path once again as we found the different connection method was more reliable and not affected by these increases in latency. We have migrated all tenants back to multi-zone write paths and are happy with and confident in the current method of connectivity to the backend cloud service, which is the one we migrated to during the course of the incident. We have no immediate plans to use the previous problematic connectivity method for the foreseeable future.

Read the full incident report →

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