Grafana Outage History
Grafana is up right nowPingoru has recorded 195 incidents for Grafana: 195 in the last 12 months and 70 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 23 | 367 of 720 (51%) |
| May 2026 | 13 | 65 of 744 (9%) |
| June 2026 | 23 | 391 of 720 (54%) |
| July 2026 | 39 | 292 of 744 (39%) |
| August 2026 | 14 | 18 of 744 (2%) |
| September 2026 | 23 | 85 of 720 (12%) |
| October 2026 | 26 | 366 of 593 (62%) |
Incidents, newest first
Minor May 18, 2026 Grafana K6 metrics processing and test runs degradation 7h 18m Cloud Test Runs, Cloud Output Test Runs, Result Analysis, Private Load Zones
Started May 18, 2026, 08:24 AM UTC· resolved May 18, 2026, 03:42 PM UTC
- investigating May 18, 2026, 08:24 AM UTC
We’re currently investigating an issue that is resulting in degraded performance in metrics processing and test run metrics may take longer than usual to show up. Our team is actively working to identify the cause. Thank you for your patience.
- investigating May 18, 2026, 10:27 AM UTC
We have identified that test runs are getting timed out as a result of the issue This issue first occurred on May 05/15/2026 at 8:00PM UTC.
- monitoring May 18, 2026, 02:30 PM UTC
We've stabilized the system and test runs no longer result in timeout. There is a small delay (a few minutes) in processing metrics at the end of the test run, but most users shouldn't be too negatively impacted by that. We expected the delay/lag to also resolve within the next 30-60 minutes.
- resolved May 18, 2026, 03:42 PM UTC
This incident has been resolved.
Minor May 13, 2026 Intermittent Errors and High latency Writing to Cloud Metrics, Cloud Logs and Cloud Traces 22h 16m GCP US Central - prod-us-central-0, GCP US Central - prod-us-central-5, GCP US Central - prod-us-central-0: Ingestion, GCP US Central - prod-us-central-5: Ingestion and 1 more
Started May 13, 2026, 08:50 AM UTC· resolved May 14, 2026, 07:06 AM UTC
- investigating May 13, 2026, 08:50 AM UTC
We’re currently investigating an issue causing intermittent errors and high latency when writing to Cloud Metrics. Our team is actively working to identify the cause. Thank you for your patience.
- investigating May 13, 2026, 10:01 AM UTC
We’re continuing to investigate the issue causing intermittent errors and high latency when writing to Cloud Metrics. We are in contact with the cloud provider’s support team, and they are investigating the issue alongside us.
- investigating May 13, 2026, 10:25 AM UTC
We have identified expanded impact affecting Grafana Cloud Logs and Grafana Cloud Traces in addition to Cloud Metrics, causing intermittent errors and increased latency when writing data. Our teams continue working on a fix and investigating the issue with the cloud provider’s support team.
- monitoring May 13, 2026, 01:37 PM UTC
We are seeing signs of recovery and improved stability across impacted services over the past hour. Our teams continue to closely monitor the situation while working with the cloud provider.
- monitoring May 13, 2026, 03:41 PM UTC
We continue to see signs of recovery and improved stability across impacted services. Our teams continue to closely monitor the situation while working with the cloud provider.
- monitoring May 13, 2026, 09:10 PM UTC
We continue to see signs of recovery and improved stability across impacted services. Our teams continue to closely monitor the situation while working with the cloud provider.
- resolved May 14, 2026, 07:06 AM UTC
We continue to observe an extended period of recovery and we're marking the incident as resolved at this point in time.
Major May 11, 2026 "Failed to Load Dashboard" Errors 18h 56m 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 May 11, 2026, 09:38 PM UTC· resolved May 12, 2026, 04:35 PM UTC
- identified May 11, 2026, 09:38 PM UTC
Customers on Grafana Cloud may see an error on dashboard panels with "Failed to load dashboard ... json unmarshal number ...". We have identified the issue and are working to deploy out the fix.
- identified May 12, 2026, 08:58 AM UTC
We are continuing to work on a fix for this issue. While we do not have additional updates to share at this time, our teams remain actively engaged and we will provide further updates as soon as they become available.
- identified May 12, 2026, 11:11 AM UTC
Our teams continue working on a fix for this issue. We do not have additional information to share at this time, but we will continue to provide updates as progress is made.
- identified May 12, 2026, 02:13 PM UTC
The fix is currently being rolled out to all impacted environments.
- resolved May 12, 2026, 04:35 PM UTC
This incident has been resolved. Thank you for your patience.
Major May 11, 2026 SSL/TLS Connectivity Issues 1h 51m Azure US Central - us-central2
Started May 11, 2026, 08:49 PM UTC· resolved May 11, 2026, 10:40 PM UTC
- investigating May 11, 2026, 08:49 PM UTC
We are currently investigating reports of service disruption affecting a subset of customers. Customers may experience intermittent connectivity issues, degraded performance, or SSL/TLS certificate validation errors when accessing affected services. Our engineering teams are actively working to identify the scope of impact and restore full functionality as quickly as possible. We will continue to provide updates as more information becomes available.
- resolved May 11, 2026, 10:40 PM UTC
This incident has been resolved. Thank you for your patience.
Minor May 8, 2026 Cloud Metrics -High Write Latency and Errors in prod-us-central-7 1h 13m Azure US Central - prod-us-central-7: Ingestion
Started May 08, 2026, 09:16 PM UTC· resolved May 08, 2026, 10:30 PM UTC
- monitoring May 08, 2026, 09:16 PM UTC
From approximately 20:40-21:00 UTc, we experienced an issue affecting Grafana Cloud Metrics in prod-us-central-7. Affected users may have experienced high latency and/or errors during ingestion and rule evaluation. Our team has identified the cause and mitigated. We are currently monitoring for long-term stability.
- resolved May 08, 2026, 10:30 PM UTC
We have continued to observe stability. This incident is now being considered as resolved. Thank you for your patience.
Critical May 7, 2026 Metrics read errors in prod-ap-south-1 region 38m AWS India - prod-ap-south-1: Querying
Started May 07, 2026, 07:18 AM UTC· resolved May 07, 2026, 07:56 AM UTC
- investigating May 07, 2026, 07:18 AM UTC
From approximately 06:24 UTC, we were alerted to an issue with read errors in mimir-prod-43. Users with instances hosted in the prod-ap-south-1 region experiencing this issue may encounter an error message when querying metrics. Engineering is actively engaged and assessing the issue. We will provide updates accordingly.
- monitoring May 07, 2026, 07:53 AM UTC
Engineering has released a fix and as of 07:50 UTC, customers should no longer experience errors when querying metrics. We will continue to monitor for recurrence and provide updates accordingly.
- resolved May 07, 2026, 07:56 AM UTC
At this time, we have confirmed that the query errors have gone and we are considering this issue resolved.
Minor May 6, 2026 Datasource Query Performance Issues 28m Integrations
Started May 06, 2026, 08:07 PM UTC· resolved May 06, 2026, 08:36 PM UTC
- investigating May 06, 2026, 08:07 PM UTC
We’re currently investigating an issue affecting Datasource query performance in prod-us-east-4. Our team is actively working to identify the cause. Thank you for your patience.
Major May 6, 2026 Hardware failure on CSP within prod-us-west-0 –
Started May 06, 2026, 05:30 AM UTC· resolved May 06, 2026, 05:30 AM UTC
- resolved May 08, 2026, 11:04 AM UTC
We observed an underlying hardware failure on our CSP which triggered an automatic live VM migration. The situation caused a (severe) degradation in write performance for Grafana Cloud Metrics on prod-us-west-0 between 05:26 UTC and 05:43 UTC
Minor May 5, 2026 Elevated Error Rate of Browser Checks in PoP Oregon 4h 2m AWS US East - prod-us-east-0: Public Probes
Started May 05, 2026, 04:11 PM UTC· resolved May 05, 2026, 08:13 PM UTC
- investigating May 05, 2026, 04:11 PM UTC
We’re currently investigating an issue affecting browser checks in the PoP Oregon region. Our team is actively working to identify the cause. Thank you for your patience.
- identified May 05, 2026, 06:13 PM UTC
We’ve identified the cause of the issue impacting browser checks. Our team is currently implementing a fix.
- monitoring May 05, 2026, 07:44 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.
- resolved May 05, 2026, 08:13 PM UTC
This incident has been resolved. Thank you for your patience.
Major May 4, 2026 k6 Partial Outage 3h 11m AWS Australia - prod-au-southeast-1: API, GCk6 App, AWS Australia - prod-au-southeast-1: Public Probes, Cloud Test Runs and 59 more
Started May 04, 2026, 10:58 PM UTC· resolved May 05, 2026, 02:09 AM UTC
- investigating May 04, 2026, 10:58 PM UTC
We’re currently investigating an issue affecting k6. Our team is actively working to identify the cause. Thank you for your patience.
- investigating May 04, 2026, 11:23 PM UTC
After further investigation, this issue may also be affecting Synthetic Monitoring. We continue to identify the cause and will update as soon as we have more information.
- monitoring May 05, 2026, 12:04 AM 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.
- resolved May 05, 2026, 02:09 AM UTC
This incident has been resolved. Thank you for your patience.
Major May 1, 2026 Ingestion Errors for AWS Cloud Provider Observability Metric Streams in prod-us-central-7 1h 13m Grafana Cloud: AWS Metrics
Started May 01, 2026, 09:14 AM UTC· resolved May 01, 2026, 10:27 AM UTC
- investigating May 01, 2026, 09:14 AM UTC
We are investigating an issue with ingesting Metrics for AWS Cloud Provider Observability with Metric Streams. Users experiencing this issue may encounter ingestion errors in the "prod-us-central-7" region only. Engineering is actively engaged and assessing the issue. We will provide updates accordingly.
- investigating May 01, 2026, 09:42 AM UTC
We are continuing to investigate this issue.
- monitoring May 01, 2026, 09:43 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 01, 2026, 10:27 AM UTC
This incident has been resolved.
Notice April 29, 2026 Performance Testing – Degraded Service (Resolved) –
Started Apr 29, 2026, 12:00 PM UTC· resolved Apr 29, 2026, 12:00 PM UTC
- resolved Apr 29, 2026, 01:51 PM UTC
We experienced degraded performance affecting Performance Testing from 13:10 UTC to 13:20 UTC. During this time, users may not have been able to start new test runs. The issue has been resolved, and the service is now operating normally. We apologize for any disruption this may have caused and appreciate your patience.
Minor April 29, 2026 Elevated write latency for AWS Metrics Streaming integration in us-east-3 region. –
Started Apr 29, 2026, 10:30 AM UTC· resolved Apr 29, 2026, 10:30 AM UTC
- resolved Apr 29, 2026, 12:57 PM UTC
We were facing an incident with AWS Metrics Streaming integration in us-east-3 region manifesting in elevated ingestion latency. The incident started at around 10:45 UTC and was resolved at around 12:30 UTC. Some tenants could see an elevated write latency, but all requests were being processed and we don't expect any data loss during the time of the incident. The incident is now resolved, but we keep monitoring the system's health.
Minor April 28, 2026 Investigating Issues Saving SQL Datasource Credentials 18h 51m Integrations
Started Apr 28, 2026, 06:46 PM UTC· resolved Apr 29, 2026, 01:37 PM UTC
- investigating Apr 28, 2026, 06:46 PM UTC
We are currently investigating reports of issues affecting SQL-based data sources where users are unable to save credentials. This appears to impact a subset of customers and may be occurring across multiple regions. We are actively working to determine the scope and root cause. We will provide updates as more information becomes available.
- monitoring Apr 28, 2026, 06:59 PM UTC
We’ve identified the cause of the issue impacting SQL datasources. Our team is currently implementing a fix and are monitoring the results to confirm the issue is fully resolved. Services may start to recover during this time.
- resolved Apr 29, 2026, 01:37 PM UTC
This incident has been resolved. Thank you for your patience.
Minor April 28, 2026 Gateway Slowness Detected in Prod (US-East-1) 2d 5h GCP US East - prod-us-east-1
Started Apr 28, 2026, 09:20 AM UTC· resolved Apr 30, 2026, 03:11 PM UTC
- investigating Apr 28, 2026, 09:20 AM UTC
Successful requests have dropped, users may not be able to access their instances.. The issue is under investigation.
- resolved Apr 30, 2026, 03:11 PM UTC
After further review, this was a false alarm and should not have affected any users. This incident has been resolved. Thank you for your patience.
Major April 27, 2026 InfluxDB Datasource - Intermittent Failures 6h 16m Integrations
Started Apr 27, 2026, 05:08 PM UTC· resolved Apr 27, 2026, 11:24 PM UTC
- investigating Apr 27, 2026, 05:08 PM UTC
We’re currently investigating an issue affecting the InfluxDB plugin. Some users may see intermittent failures. Our team is actively working to identify the cause. Thank you for your patience.
- identified Apr 27, 2026, 06:01 PM UTC
We’ve identified the cause of the issue impacting the InfluxDB datasource. Our team is currently implementing a fix.
- monitoring Apr 27, 2026, 11:13 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.
- resolved Apr 27, 2026, 11:24 PM UTC
This incident has been resolved. Thank you for your patience.
Major April 23, 2026 Cloudwatch Datasource Outage 5h 35m GCP US Central - prod-us-central-0
Started Apr 23, 2026, 02:26 PM UTC· resolved Apr 23, 2026, 08:01 PM UTC
- investigating Apr 23, 2026, 02:26 PM UTC
We’re currently investigating an issue affecting Cloudwatch datasources. Our team is actively working to identify the cause. Thank you for your patience.
- monitoring Apr 23, 2026, 02:39 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.
- resolved Apr 23, 2026, 08:01 PM UTC
This incident has been resolved. Thank you for your patience.
Minor April 20, 2026 Restrictions on Alerts & Reports for Grafana Cloud Free/Trial Users 3d 17h AWS Australia - prod-au-southeast-2, AWS Australia - prod-au-southeast-1: Rule Evaluation, AWS Brazil - prod-sa-east-1, AWS Australia - prod-au-southeast-1: Alertmanager and Rules Configuration API and 86 more
Started Apr 20, 2026, 09:12 PM UTC· resolved Apr 24, 2026, 03:04 PM UTC
- monitoring Apr 20, 2026, 09:12 PM UTC
Grafana Labs is taking steps to safeguard our Grafana Cloud platform against unauthorized access while maintaining the Grafana Cloud Free tier of service our users and the community have come to rely on. As of Monday April 20, alerting and reporting capabilities have been disabled in new Grafana Cloud Free and trial stacks. We are working towards deploying improvements and restoring those functionalities in a way that keeps our platform secure and open for all of our users.
- monitoring Apr 20, 2026, 10:07 PM UTC
We are continuing to monitor for any further issues.
- monitoring Apr 22, 2026, 03:03 PM UTC
Grafana Labs is implementing measures to safeguard the Grafana Cloud platform against ongoing unauthorized use while preserving the capabilities relied upon by our community. Effective immediately, we have made the following modifications to the platform: Alerting Email alerting has been disabled for new Grafana Cloud Free and Trial accounts; however, all other integrations such as webhooks remain functional. Additionally, Cloud Alertmanager is now disabled for Grafana instances in these accounts, requiring all configuration to occur via the native Grafana Alertmanager. Existing Grafana Cloud accounts remain unaffected by these restrictions and all other Grafana Cloud account types are also unaffected. Reporting To prevent the distribution of unauthorized emails, Grafana instances in new Grafana Cloud Free and Trial accounts are limited to sending reports exclusively to users within their Grafana instance. Standard reporting functionality continues unrestricted for existing Grafana Cloud accounts and all other Grafana Cloud account types. We remain committed to further refining platform security to ensure a safe and open environment for our entire user base.
- resolved Apr 24, 2026, 03:04 PM UTC
Grafana Labs has taken steps to safeguard the Grafana Cloud platform against the distribution of unauthorized emails. We have implemented the following changes to new Grafana Cloud Free and Trial accounts, effective immediately: Users who open Grafana Cloud Free and Trial accounts can only send email alerts and reports to users within their Grafana instance. Other email recipients will be rejected. Additionally, the Cloud Alertmanager is no longer available for these instances, requiring all alerting to be configured via the native Grafana Alertmanager. All other integrations for alerting remain functional. If users would like to expand their email capabilities, they can upgrade their Grafana Cloud account to scale their use case, as needed. These changes to alerting and reporting will be applied to all new Grafana Cloud Free and Trial accounts. Existing Grafana Cloud Free and Trial accounts opened before April 20 and all other Grafana Cloud account types are unaffected by these changes.
Critical April 20, 2026 Elevated 429 Errors Impacting Metrics Querying Across Multiple Regions 21m AWS Australia - prod-ap-southeast-2: Querying, AWS Australia - prod-ap-southeast-2: Ingestion, AWS Brazil - prod-sa-east-1: Querying, AWS Brazil - prod-sa-east-1: Ingestion and 44 more
Started Apr 20, 2026, 02:09 PM UTC· resolved Apr 20, 2026, 02:30 PM UTC
- investigating Apr 20, 2026, 02:09 PM UTC
We are currently experiencing a major incident causing elevated 429 (rate limit) errors across multiple regions, primarily impacting metrics querying. This is a high-priority issue, and our engineering team is actively engaged and working urgently to identify the root cause and restore full service as quickly as possible. Customers may experience widespread failures or delays when querying metrics during this time. We understand the significant impact this may have and will continue to provide updates as more information becomes available.
- investigating Apr 20, 2026, 02:21 PM UTC
The issue is now confirmed to be widespread, affecting Prometheus across all regions. Customers may continue to experience elevated 429 (rate limit) errors, particularly when querying metrics, with failures or inconsistent responses possible. Our engineering team remains fully engaged and is actively working on mitigation and resolution efforts with the highest priority.
- resolved Apr 20, 2026, 02:30 PM UTC
This incident has been resolved. Thank you for your patience.
Minor April 17, 2026 Query Caching - Degraded Performance 1h 34m AWS Germany - prod-eu-west-2, AWS US East (OH) - prod-us-east-0, Azure Netherlands - prod-eu-west-3, GCP US Central - prod-us-central-0
Started Apr 17, 2026, 09:23 PM UTC· resolved Apr 17, 2026, 10:58 PM UTC
- 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.
- 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.
- resolved Apr 17, 2026, 10:58 PM UTC
This incident has been resolved
Minor April 16, 2026 Issues on Stack creation 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 27 more
Started Apr 16, 2026, 12:52 PM UTC· resolved Apr 16, 2026, 02:02 PM UTC
- identified Apr 16, 2026, 12:52 PM UTC
Since today 16th at ~12:11UTC we are seeing issues on stack creation across all our regions. Customers will experience error message when attempting to create a stack. Our engineering team has identified the source of the issue as external to Grafana (provider), and they are tracking its recovery.
- monitoring Apr 16, 2026, 01:19 PM UTC
The issue is fixed and we are currently monitoring the service.
- resolved Apr 16, 2026, 02:02 PM UTC
This incident has been resolved.
Minor April 15, 2026 Degraded Ticket Visibility in Support System 17m Support Tickets
Started Apr 15, 2026, 04:07 PM UTC· resolved Apr 15, 2026, 04:25 PM UTC
- monitoring Apr 15, 2026, 04:07 PM UTC
We are currently experiencing an issue with our ticketing system provider that is affecting how tickets appear within our internal support views. We are continuing to receive all new tickets successfully, and no requests are being lost at this time. Our team is actively monitoring the situation and working to ensure all incoming requests are reviewed, including those that may not be immediately visible in standard views. We will provide further updates as we receive more information from our provider. We appreciate your patience.
- resolved Apr 15, 2026, 04:25 PM UTC
This incident has been resolved and our ticketing system is fully operational. Thank you for your patience.
Notice April 14, 2026 k6 Cloud Service Disruption –
Started Apr 14, 2026, 11:30 AM UTC· resolved Apr 14, 2026, 11:30 AM UTC
- resolved Apr 14, 2026, 01:44 PM UTC
Between approximately 12:30 UTC and 13:15 UTC, k6 Cloud experienced a service disruption due to issues introduced in a recent API release. During this time, users were unable to access the k6 Cloud application. The issue was mitigated by reverting the release, and service has since been fully restored.
Minor April 14, 2026 K6 Sporadic DNS Issues 1d 3h Cloud Test Runs
Started Apr 14, 2026, 09:22 AM UTC· resolved Apr 15, 2026, 12:59 PM UTC
- identified Apr 14, 2026, 09:22 AM UTC
We are having sporadic DNS issues that occasionally affect the start of cloud test runs, causing them to abort. We are currently working to resolve. The issue has been occurring since April 9.
- monitoring Apr 14, 2026, 02:29 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.
- monitoring Apr 14, 2026, 02:29 PM UTC
Our engineering team has deployed a fix and we are currently monitoring the behaviour of the system until full resolution.
- resolved Apr 15, 2026, 12:59 PM UTC
This incident is now resolved. We had intermediary issues with a flaky DNS server that caused random tests to not start properly. Since the DNS server was fixed, we haven't been seeing the issue anymore.
Notice April 13, 2026 Loki write instability in prod-eu-west-2.loki-prod-012 –
Started Apr 13, 2026, 11:30 AM UTC· resolved Apr 13, 2026, 11:30 AM UTC
- resolved Apr 14, 2026, 12:02 PM UTC
There was a period of write instability yesterday. It was between ~1330 -1730 UTC yesterday. This was due to a scheduled maintenance.