There were 52 Grafana outages since February 25, 2026 totaling 1064h 58m of downtime. Each is summarised below — incident details, duration, and resolution information.
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
Some of the CloudWatch queries were failing. Started at 08:37 UTC Monitoring from 09:21 UTC
We are continuing to monitor for any further issues.
This incident has been resolved.
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.
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.
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.
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.
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.
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.
This incident has been resolved. Thank you for your patience.
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.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor the previously impacted environments.
We are continuing to monitor this through the weekend.
We are continuing to monitor for any further issues.
We are still seeing intermittent issues and continue to seek a resolution
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.
We are continuing to monitor for any further issues.
This incident has been resolved. Thank you for your patience.
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.
We are currently experiencing degraded writes for mimir-prod-22 in prod-eu-west-3 since 08:45Z.
A fix has been implemented and we are monitoring the results.
We have not observed any recent errors, but we will continue to monitor while we work with our CSP.
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.
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.
This incident has been resolved.
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.
We are continuing to investigate this issue.
The impact extends beyond the TOS check. Assistant is completely unavailable in the impacted region.
The issue has been identified, and we are implementing a fix.
This incident has been resolved.
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.
We have observed impact in prod-eu-west-4 as well.
This incident has been resolved.
We are currently investigating an issue impacting the CloudWatch Datasource causing failures.
We have identified the issue, and are rolling out the fix. We are already seeing improvements and will continue to monitor progress.
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.
We are continuing to monitor for any further issues.
This incident has been resolved.
Some customers are seeing degraded performance and errors from certain v6 API endpoints. We are investigating the issue.
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.
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.
We are continuing to investigate this issue with our CSP, and will provide updates as they become available.
We have been observing stability for a period of time and will mark the incident as resolved at this time.
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.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are noticing issues with various HG pages. Our engineering team is actively looking into it.
This incident has been resolved.
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.
A fix has been implemented, and we are monitoring.
There are ongoing intermittent elevated transient write failures. We will continue to provide additional updates as more information becomes available.
Things have been stable, and we have a potential mitigation should this issue arise again. We are monitoring the issue in the meantime.
This incident has been resolved.
There has been a reoccurrence o the issues on the Read path of Loki services on AWS US West since yesterday 9th around ~17:15UTC. The issue has been identified, and resolutions steps has been taken to restore full service. We are currently monitoring the service status. The impact of this includes timeouts and 5xx errors when query logs for customers on this cluster.
This incident has been resolved.
From 15:30 to 15:45 UTC and from 16:53 to 17:03 UTC, the prod-us-central-0 and prod-us-central-5 regions saw elevated latency and error rates on the write path. We're monitoring now.
This incident has been resolved.
Some users in prod-us-central-0 may be seeing elevated rate of errors when fetching configurations. Our engineers are currently investigating this issue.
Our engineering team continues to work towards a resolution for this issue.
This incident has been resolved.
We are seeing elevated errors rate and outages across many of our services in prod-eu-central-0, due to an on-going AWS S3 outage in that region.
We are continuing to investigate this issue.
Since about 20:03 UTC we have seen AWS S3 recover and also our services are recovering, we are monitoring.
Since about 20:03 UTC we have seen AWS S3 recover and also our services are recovering, we are monitoring.
This incident has been resolved.
A recent incident affecting the data read path and rule execution within prod-eu-west-0 began at ~21:05 UTC on March 5, 2026. Customers with instances in this region may experience write failures and delays in rule evaluation. Engineering is actively engaged and assessing the issue. We will provide updates accordingly.
Engineering has released a fix and as of 22:00 UTC, customers should no longer experience write failures and delays in rule evaluation. We will continue to monitor for recurrence and provide updates accordingly.
We continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.
We are currently experiencing an issue with Fleet Management in prod-us-central-0. Users in prod-us-central-0 may observe elevated rate of errors when fetching configurations.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Test run browser screenshot upload experienced failures from 13:12 to 14:51 UTC. The issue has been resolved
We are experiencing increased write latency for logs in prod-eu-west-3. Our Engineering team is aware and currently investigating this. We will provide further updates accordingly.
We are now experiencing write outage for logs in prod-eu-west-3. Our Engineering team is aware and currently investigating this. We will provide further updates accordingly.
This incident has been resolved.
Pingoru polls Grafana's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
5 free monitors · No credit card required