Grafana Outage History

Grafana is up right now

Pingoru has recorded 195 incidents for Grafana: 195 in the last 12 months and 70 in the last 90 days.

Source: status.grafana.com

195incidents recorded
195last 12 months
70last 90 days
31 hourstypical duration
Incidents per month
02040AprMayJunJulAugSepOct26
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct62%
Pingoru began tracking Grafana in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202623367 of 720 (51%)
May 20261365 of 744 (9%)
June 202623391 of 720 (54%)
July 202639292 of 744 (39%)
August 20261418 of 744 (2%)
September 20262385 of 720 (12%)
October 202626366 of 594 (62%)

Incidents, newest first

Major April 10, 2026 Grafana Cloud Logs - Write degradation in us-east-3 43m

Started Apr 10, 2026, 11:53 PM UTC· resolved Apr 11, 2026, 12:36 AM UTC

  1. investigating Apr 10, 2026, 11:53 PM UTC

    We are seeing issues on the write path for Loki in cluster in us-east-3, and we are actively investigating this issue.

  2. monitoring Apr 11, 2026, 12:10 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 11, 2026, 12:36 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 10, 2026 Tempo Write Outage 1h 19m AWS US East - prod-us-east-3: Ingestion

Started Apr 10, 2026, 07:42 PM UTC· resolved Apr 10, 2026, 09:02 PM UTC

  1. investigating Apr 10, 2026, 07:42 PM UTC

    We are currently investigating a write outage affecting prod-us-east-3. The issue began at 18:50 UTC. Users may experience errors, timeouts, or unavailability while we work to identify the cause and restore service.

  2. monitoring Apr 10, 2026, 07:53 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 within an hour.

  3. resolved Apr 10, 2026, 09:02 PM UTC

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

Read the full incident report →

Minor April 9, 2026 K6 Browser Testing/Timeline Not Available 1h 15m Result Analysis

Started Apr 09, 2026, 05:34 PM UTC· resolved Apr 09, 2026, 06:50 PM UTC

  1. investigating Apr 09, 2026, 05:34 PM UTC

    We’re currently investigating an issue affecting browser testing. Users running browser tests will not be able to see the browser timeline. Our team is actively working to identify the cause and will share an update within two hours. Thank you for your patience.

  2. identified Apr 09, 2026, 06:39 PM UTC

    We’ve identified the cause of the issue impacting k6 browser testing/timeline. Our team is currently implementing a fix. We’ll provide another update in two hours or sooner if the situation changes.

  3. resolved Apr 09, 2026, 06:50 PM UTC

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

Read the full incident report →

Minor April 8, 2026 Stability Issues for Some Customers in the prod-gb-south-1 Region. –

Started Apr 08, 2026, 05:00 PM UTC· resolved Apr 08, 2026, 05:00 PM UTC

  1. resolved Apr 08, 2026, 05:00 PM UTC

    We had a stability issue for a subset of customers in the prod-gb-south-1 region. The impact was between UTC 15:20-16:30 which impacted roughly 30% of queries and rules evaluations. We've applied mitigations, queries should be back to normal.

Read the full incident report →

Minor April 7, 2026 Unable to Edit Notification Policies 4h 59m AWS Australia - prod-au-southeast-1: Alertmanager, AWS Brazil - prod-sa-east-1: Alertmanager, AWS Canada - prod-ca-east-0: Alertmanager, AWS Germany - prod-eu-west-2: Alertmanager and 14 more

Started Apr 07, 2026, 03:17 PM UTC· resolved Apr 07, 2026, 08:17 PM UTC

  1. investigating Apr 07, 2026, 03:17 PM UTC

    We’re currently investigating an issue affecting notification policies. Our team is actively working to identify the cause and will share an update within 2 hours. Thank you for your patience.

  2. identified Apr 07, 2026, 04:52 PM UTC

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

  3. identified Apr 07, 2026, 06:03 PM UTC

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

  4. resolved Apr 07, 2026, 08:17 PM UTC

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

Read the full incident report →

Minor April 6, 2026 Notification Policies and Contact Points Missing in UI on the Slow Release Channel 21h 38m AWS Australia - prod-au-southeast-1: Rule Evaluation, AWS Australia - prod-au-southeast-1: Alertmanager and Rules Configuration API, AWS Australia - prod-au-southeast-1: Alertmanager, AWS Brazil - prod-sa-east-1: Rule Evaluation and 57 more

Started Apr 06, 2026, 02:48 PM UTC· resolved Apr 07, 2026, 12:26 PM UTC

  1. investigating Apr 06, 2026, 02:48 PM UTC

    We’re currently investigating an issue affecting notification policies and contact points for instances on the slow release channel. Alerting API calls for contact points and notification policies return data as expected, so this appears to be limited to the UI. 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 Apr 06, 2026, 04:13 PM UTC

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

  3. identified Apr 06, 2026, 09:04 PM UTC

    We’ve identified the cause of the issue impacting the Notification Policy and Contact Point UI. Our team is currently implementing a fix. We’ll provide another update when the fix is deployed and we monitor the expected improvement.

  4. monitoring Apr 06, 2026, 11:58 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 within 2 hours.

  5. resolved Apr 07, 2026, 12:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 3, 2026 Partial K6 Test Run Outage 2h 8m Cloud Test Runs, Cloud Output Test Runs, Private Load Zones

Started Apr 03, 2026, 03:29 PM UTC· resolved Apr 03, 2026, 05:38 PM UTC

  1. investigating Apr 03, 2026, 03:29 PM UTC

    We're experiencing an outage affecting test runs that use k6 extensions. The issue prevents users from executing these types of test runs both locally and in Grafana Cloud. Test runs that do not use extensions are not affected by this incident.

  2. resolved Apr 03, 2026, 05:38 PM UTC

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

Read the full incident report →

Minor April 1, 2026 AWS integration Degraded Performance 46m Integrations

Started Apr 01, 2026, 08:17 PM UTC· resolved Apr 01, 2026, 09:03 PM UTC

  1. investigating Apr 01, 2026, 08:17 PM UTC

    We are investigating a noticeable drop in active series for the AWS integration that began around 18:15 UTC. This issue may cause scrapes to hit rate limits, which can result in individual data points not being collected for the serverless integration. The impact is intermittent and may affect any customer using the AWS integration, regardless of region. We are currently working to identify the cause and will provide an update as soon as we have more information.

  2. resolved Apr 01, 2026, 09:03 PM UTC

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

Read the full incident report →

Minor April 1, 2026 Query degradation and possible rule evaluation failure on prod-eu-west-0.cortex-prod-01 11h 16m GCP Belgium - prod-eu-west-0: Querying, GCP Belgium - prod-eu-west-0: Ingestion

Started Apr 01, 2026, 09:56 AM UTC· resolved Apr 01, 2026, 09:13 PM UTC

  1. investigating Apr 01, 2026, 09:56 AM UTC

    We are currently observing delays in ingesting data, possibly causing partial query results and failed rule evaluations for prod-eu-west-0.cortex-prod-01 metrics cell.

  2. investigating Apr 01, 2026, 10:11 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Apr 01, 2026, 10:12 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Apr 01, 2026, 09:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 31, 2026 k6 Cloud Degradation –

Started Mar 31, 2026, 02:59 PM UTC· resolved Mar 31, 2026, 02:59 PM UTC

  1. resolved Mar 31, 2026, 02:59 PM UTC

    From approximately 11:00 UTC - 15:00 UTC we had a degradation that caused test start errors for a large percentage of Cloud runs managed as scripts in the GCK6 app. This has since been resolved.

Read the full incident report →

Notice March 31, 2026 Synthetic Monitoring: Some Check Creations & Updates Might be Blocked. –

Started Mar 31, 2026, 02:32 PM UTC· resolved Mar 31, 2026, 02:32 PM UTC

  1. resolved Mar 31, 2026, 02:32 PM UTC

    This is a retroactive status page linked to the following incident: https://status.grafana.com/incidents/38wwbz50ggrp This retroactive status page is meant to clarify the time of impact. This issue first started at ~2026-03-30 18:00 UTC. This is now resolved

Read the full incident report →

Major March 31, 2026 Some of the CloudWatch queries are failing 35m AWS Australia - prod-au-southeast-2, AWS Brazil - prod-sa-east-1, AWS Canada - prod-ca-east-0, AWS Germany - prod-eu-west-2 and 27 more

Started Mar 31, 2026, 09:48 AM UTC· resolved Mar 31, 2026, 10:24 AM UTC

  1. monitoring Mar 31, 2026, 09:48 AM UTC

    Some of the CloudWatch queries were failing. Started at 08:37 UTC Monitoring from 09:21 UTC

  2. monitoring Mar 31, 2026, 09:49 AM UTC

    We are continuing to monitor for any further issues.

  3. resolved Mar 31, 2026, 10:24 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 30, 2026 Tempo Reads Outage for Small Subset of Customers –

Started Mar 30, 2026, 04:30 PM UTC· resolved Mar 30, 2026, 04:30 PM UTC

  1. resolved Mar 30, 2026, 06:34 PM UTC

    We encountered an issue impacting only a small subset of customers in the prod-us-central-0 region. The incident occurred between 16:20 and 17:50 UTC on 3/30/26. This incident is now resolved.

Read the full incident report →

Critical March 25, 2026 Prometheus writes in prod-eu-west-3 are degraded 29d 5h Azure Netherlands - prod-eu-west-3: Ingestion

Started Mar 25, 2026, 02:11 PM UTC· resolved Apr 23, 2026, 08:07 PM UTC

  1. investigating Mar 25, 2026, 02:11 PM UTC

    The metric writes issue reported in https://status.grafana.com/incidents/gfshj17lxj5z is still ongoing. Our Engineering team is actively investigating this and we will provide further updates as our investigation progresses.

  2. investigating Mar 25, 2026, 09:35 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Mar 26, 2026, 12:04 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Mar 26, 2026, 05:45 PM UTC

    We are continuing to monitor the previously impacted environments.

  5. monitoring Mar 27, 2026, 09:05 PM UTC

    We are continuing to monitor this through the weekend.

  6. monitoring Apr 02, 2026, 09:38 PM UTC

    We are continuing to monitor for any further issues.

  7. monitoring Apr 08, 2026, 08:32 PM UTC

    We are still seeing intermittent issues and continue to seek a resolution

  8. monitoring Apr 14, 2026, 08:11 PM UTC

    We have deployed mitigation and seen improvement in write failures over the past week. We are still seeing intermittent spikes in latency and continue to monitor.

  9. monitoring Apr 20, 2026, 03:08 PM UTC

    We are continuing to monitor for any further issues.

  10. resolved Apr 23, 2026, 08:07 PM UTC

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

Read the full incident report →

Notice March 24, 2026 Service degradation on Dashboard loading in several clusters. –

Started Mar 24, 2026, 02:00 PM UTC· resolved Mar 24, 2026, 02:00 PM UTC

  1. resolved Mar 25, 2026, 10:30 AM UTC

    An issue affecting Grafana Cloud instances was diagnosed yesterday 24th of March that avoided Dashboards to be loaded correctly. The incident impacted the following clusters: - GCP US Central (us-central-0) between 13:15 and 13:50 UTC - AWS US East (us-east-0) between 13:43 and 13:55 UTC - AWS US West (us-west-2) between 14:05 and 14:06 UTC The issue has been identified and measurement corrections has been applied.

Read the full incident report →

Minor March 24, 2026 Prometheus writes, Logs, and Synthetic Monitoring in prod-eu-west-3 are degraded 1d 3h Azure Netherlands - prod-eu-west-3, Azure Netherlands - prod-eu-west-3: API, Azure Netherlands - prod-eu-west-3: Ingestion, Azure Netherlands - prod-eu-west-3: Public Probes

Started Mar 24, 2026, 09:08 AM UTC· resolved Mar 25, 2026, 12:52 PM UTC

  1. investigating Mar 24, 2026, 09:08 AM UTC

    We are currently experiencing degraded writes for mimir-prod-22 in prod-eu-west-3 since 08:45Z.

  2. monitoring Mar 24, 2026, 09:19 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Mar 24, 2026, 09:23 PM UTC

    We have not observed any recent errors, but we will continue to monitor while we work with our CSP.

  4. investigating Mar 25, 2026, 07:04 AM UTC

    We are moving this back to 'Investigating' as we are now observing a substantial drop in successful ingestion and increase in write path errors, and elevated rule evaluation latency and error. Reads are mostly fine. Our Engineering team is actively investigating this and we will provide further updates as our investigation progresses.

  5. investigating Mar 25, 2026, 07:43 AM UTC

    This is also now impacting Logs and Synthetic Monitoring in prod-eu-west-3. For Synthetic Monitoring, users might observe errors pushing check execution metrics, and this can eventually lead to missing data. In addition, users might observe errors evaluating Synthetic Monitoring provisioned alert rule evaluations, and this can lead to missed alerts. For Logs, there is no immediate impact on alerts, however, remote writes to Mimir is delayed which means users may see gaps in their recording rules.

  6. resolved Mar 25, 2026, 12:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 23, 2026 Grafana Assistant Unavailable in prod-us-east-0 1h 44m AWS US East - prod-us-east-0, AWS US East - prod-us-east-2, GCP US East - prod-us-east-1

Started Mar 23, 2026, 05:03 PM UTC· resolved Mar 23, 2026, 06:48 PM UTC

  1. investigating Mar 23, 2026, 05:03 PM UTC

    We are aware of an issue currently impacting Grafana Assistant. Impacted users are met with a request to accept the TOS, however the plugin is failing upon accepting. Our engineering are currently investigating this issue.

  2. investigating Mar 23, 2026, 06:01 PM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 23, 2026, 06:07 PM UTC

    The impact extends beyond the TOS check. Assistant is completely unavailable in the impacted region.

  4. identified Mar 23, 2026, 06:25 PM UTC

    The issue has been identified, and we are implementing a fix.

  5. resolved Mar 23, 2026, 06:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 20, 2026 Authentication API Database Down in prod-eu-west-2 and prod-eu-west-4 40m AWS Germany - prod-eu-west-2, AWS Germany - prod-eu-west-4

Started Mar 20, 2026, 03:00 PM UTC· resolved Mar 20, 2026, 03:41 PM UTC

  1. investigating Mar 20, 2026, 03:00 PM UTC

    We are currently investigating an issue impacting the main database for Authentication API's in the prod-eu-west-2 region. Writes are currently failing, but reads are operational.

  2. investigating Mar 20, 2026, 03:08 PM UTC

    We have observed impact in prod-eu-west-4 as well.

  3. resolved Mar 20, 2026, 03:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 19, 2026 Various Datasource Issues 1h 57m Integrations

Started Mar 19, 2026, 04:46 PM UTC· resolved Mar 19, 2026, 06:44 PM UTC

  1. investigating Mar 19, 2026, 04:46 PM UTC

    We are currently investigating an issue impacting the CloudWatch Datasource causing failures.

  2. monitoring Mar 19, 2026, 05:13 PM UTC

    We have identified the issue, and are rolling out the fix. We are already seeing improvements and will continue to monitor progress.

  3. monitoring Mar 19, 2026, 05:56 PM UTC

    We have observed recovery for the Cloudwatch Datasource. We are now seeing failures for the following Datasources: Aurora Opensearch X-Ray Timestream Redshift Sitewise A fix for the above is being rolled out now, and we will monitor progress. We will also change the name of this incident from "Cloudwatch Datasource Issues" to "Various Datasource Issues" to more accurately reflect impact.

  4. monitoring Mar 19, 2026, 05:56 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Mar 19, 2026, 06:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 19, 2026 Degraded performance of Grafana Cloud k6 test runs 6h 54m Cloud Test Runs

Started Mar 19, 2026, 11:17 AM UTC· resolved Mar 19, 2026, 06:11 PM UTC

  1. investigating Mar 19, 2026, 11:17 AM UTC

    Some customers are seeing degraded performance and errors from certain v6 API endpoints. We are investigating the issue.

  2. resolved Mar 19, 2026, 06:11 PM UTC

    Our engineering team has deployed a fix and we continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.

Read the full incident report →

Minor March 13, 2026 Grafana Cloud Logs - Write degradation in Azure Netherlands (eu-west-3) 4d 20h Azure Netherlands - prod-eu-west-3

Started Mar 13, 2026, 10:28 AM UTC· resolved Mar 18, 2026, 07:13 AM UTC

  1. investigating Mar 13, 2026, 10:28 AM UTC

    We are seeing issues on the write path for Loki in cluster Azure Netherlands (eu-west-3). Impact will reflect in degradation of logs ingestion on that cluster. Our engineering team is already working on restoring the service.

  2. investigating Mar 13, 2026, 09:22 PM UTC

    We are continuing to investigate this issue with our CSP, and will provide updates as they become available.

  3. resolved Mar 18, 2026, 07:13 AM UTC

    We have been observing stability for a period of time and will mark the incident as resolved at this time.

Read the full incident report →

Major March 13, 2026 Increased number of Aborted-by-Systems with a k6 binary building errors 10h 30m Cloud Test Runs

Started Mar 13, 2026, 07:41 AM UTC· resolved Mar 13, 2026, 06:11 PM UTC

  1. investigating Mar 13, 2026, 07:41 AM UTC

    We are seeing an increased number of Aborted-by-Systems with a k6 binary building error. We are investigating the issue. The first occurrence of this happened back on March 9, has now been identified as a blocking issue for some customers.

  2. identified Mar 13, 2026, 08:45 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Mar 13, 2026, 12:49 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Mar 13, 2026, 06:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 11, 2026 Rule Evaluation Outage in prod-us-west-0 2d 1h AWS US West - prod-us-west-0: Rule Evaluation

Started Mar 11, 2026, 05:10 PM UTC· resolved Mar 13, 2026, 06:15 PM UTC

  1. investigating Mar 11, 2026, 05:10 PM UTC

    We are currently investigating an issue impacting rule evaluation for a subset of customers in the prod-us-west-0 region. We will provide updates as they become available.

  2. monitoring Mar 11, 2026, 06:02 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 13, 2026, 06:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 10, 2026 Various Issues with HG Pages 1h 10m AWS Australia - prod-au-southeast-2, AWS Brazil - prod-sa-east-1, AWS Canada - prod-ca-east-0, AWS Germany - prod-eu-west-2 and 26 more

Started Mar 10, 2026, 06:06 PM UTC· resolved Mar 10, 2026, 07:17 PM UTC

  1. investigating Mar 10, 2026, 06:06 PM UTC

    We are noticing issues with various HG pages. Our engineering team is actively looking into it.

  2. resolved Mar 10, 2026, 07:17 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 10, 2026 Some Write Failures in prod-eu-west-3. 1d 3h Azure Netherlands - prod-eu-west-3: Ingestion

Started Mar 10, 2026, 06:00 PM UTC· resolved Mar 11, 2026, 09:48 PM UTC

  1. investigating Mar 10, 2026, 06:00 PM UTC

    We are currently investigating an issue impacting a subset of users in the prod-eu-west-3 region. Impacted users are experiencing elevated transit write failures, with no degradation to the read path.

  2. monitoring Mar 10, 2026, 06:42 PM UTC

    A fix has been implemented, and we are monitoring.

  3. identified Mar 11, 2026, 01:35 AM UTC

    There are ongoing intermittent elevated transient write failures. We will continue to provide additional updates as more information becomes available.

  4. monitoring Mar 11, 2026, 03:51 PM UTC

    Things have been stable, and we have a potential mitigation should this issue arise again. We are monitoring the issue in the meantime.

  5. resolved Mar 11, 2026, 09:48 PM UTC

    This incident has been resolved.

Read the full incident report →