Live status · checked every 15 minutes
Is Grafana Cloud down right now?
Grafana Cloud hosts dashboards, metrics, logs and traces.
Live reader reports
Is Grafana Cloud down for you?
Tap what's not working, or tell us it works. Reports are anonymous, one per visitor.
No reports in the last 24 hours. Be the first to tell other readers what you're seeing.
Grafana Cloud not working for you?
- Check your internet connection and any VPN or corporate proxy.
- Sign out and back in, or try a private browser window.
- Check the specific feature you use on the official status page: one part can be down while the rest works.
- Retry failed API calls and jobs with backoff.
Grafana Cloud outage history
Last 30 daysFixed Increased Read Latency In prod-us-central-0 Region
Affected: GCP US Central - prod-us-central-0: Querying, Metrics - GCP US Central - prod-us-central-0: Querying
-
Between 16:20 and 17:40 UTC, a subset of customers in prod-us-central-0 experienced increased query latency and delayed or missed rule evaluations. Service is fully restored. Thank you for your patience.
-
A fix is currently being rolled out, and we are seeing improvement. Most customers should now see normal query performance, but some may still notice slower queries or delays in alert and recording rule evaluations until recovery is complete. We are continuing to monitor the situation. Next update by 18:30 UTC.
-
We are currently investigating an issue that is causing increased latency in the read path in the prod-us-central-0 region. Next update by 18:00 UTC.
Fixed Data Source Permission Errors
-
Between November 9 and November 18, 2026, some Grafana Cloud users with Edit or Admin permissions on a data source may have experienced “permission denied” (403) errors when configuring or querying a newly created data source. A change to how data source permissions are stored caused these permissions to be incorrectly evaluated. We rolled back that change on November 18 at 17:27 UTC, preventing newly created permissions from being affected. However, access issues caused by permissions stored before the rollback may persist until an additional fix is deployed.
Fixed Degraded performance for Grafana Cloud Metrics in prod-us-central-7
Affected: Azure US Central - us-central7, Azure US Central - us-central7: Ingestion, Azure US Central - prod-us-central-7: Querying, Azure US Central - prod-us-central-7: Ingestion, Metrics - Azure US Central - prod-us-central-7: Querying, Metrics - Azure US Central - prod-us-central-7: Ingestion, Logs - Azur...
-
Increased latency on a cloud provider database resulted in a 50m write and rule evaluation outage, starting about 2020 UTC. Metrics rule evaluations were last to recover, around 2110 UTC.
-
Traffic has recovered and we are monitoring the results.
-
We are continuing to investigate this issue.
-
We are continuing to investigate this issue.
-
We are investigating an issue affecting Grafana Cloud Metrics, Logs, and Traces in the prod-us-central-7 region. Some customers may see failed or delayed writes, query errors, and failed alerting and recording rule evaluations.
Fixed Elevated query errors for Grafana Cloud Metrics in prod-us-east-3
-
This incident has been resolved.
-
Between 17:21 and 17:41 UTC, a small percentage of metrics queries for some Grafana Cloud Metrics customers in the prod-us-east-3 region failed. Ingestion was not affected. Query errors have stopped, and we are monitoring the service to confirm it stays stable.
Fixed Cloud Logs writes - Elevated latency and error rates in prod-eu-central-0
Affected: AWS Switzerland - prod-eu-central-0, Logs - AWS Switzerland - prod-eu-central-0
-
We're observing a continued period of recovery and will mark this as resolved.
-
Cloud Logs writes have experienced elevated latency and error rates in prod-eu-central-0 from 07:05 UTC to 07:08 UTC, and 07:25 UTC to 07:45 UTC. The latency has been mitigated and we are currently monitoring.
Fixed Mimir query unexpected response with status code 500
Affected: AWS US East - prod-us-east-0: Querying, GCP US Central - prod-us-central-0: Querying, Metrics - AWS US East - prod-us-east-0: Querying, Metrics - GCP US Central - prod-us-central-0: Querying
-
From approximately 03:20 UTC on 10 November, some Grafana Cloud Metrics customers in AWS US East (OH) and GCP US Central saw errors, or failed queries, when reading older data. Service has fully recovered and this incident is now resolved.
-
Our mitigation remains in place and query behavior in AWS US East (OH) and GCP US Central continues to improve. Some customers may still see occasional, brief query errors in the meantime.
-
Our mitigation remains in place and query behavior in AWS US East (OH) and GCP US Central continues to improve. Some customers may still see occasional, brief query errors in the meantime.
-
A fix has been implemented and we are monitoring the results.
-
We’ve identified an issue querying older data, and are already seeing recovery.
-
We’ve identified an issue querying older data, and are already seeing recovery
Fixed Synthetic Monitoring — Jakarta Public Probe Degradation
Affected: AWS Indonesia - prod-ap-southeast-2: Public Probes, Synthetic Monitoring - AWS Indonesia - prod-ap-southeast-2: Public Probes
-
Between 08:31 and 09:17 UTC on 6 November 2026, a network issue at the Jakarta public probe caused elevated check failures for monitors running from that location. - DNS checks: failure rate increased from ~0.3% to ~15% - HTTP, ping, traceroute, and browser checks:
Fixed GitHub returning 403 for all Git Sync repositories
Affected: AWS Australia - prod-au-southeast-1, AWS Australia - prod-au-southeast-2, AWS Brazil - prod-sa-east-1, AWS Canada prod-ca-central-1, AWS Canada - prod-ca-east-0, AWS Germany - prod-eu-west-2, AWS Germany - prod-eu-west-4, AWS Germany prod-eu-central-1, AWS India - prod-ap-south-1, AWS Indonesia - pr...
-
The fix has been deployed to all production clusters and we are observing a continued period of stability. At this time, we are marking the incident as resolved.
-
The fix has landed in 60% of production. We are currently monitoring as it lands in the remaining clusters.
-
Since ~21:40 UTC on Nov 3, GitHub started rejecting the default User-Agent our Git Sync client sends (nanogit/0), so nearly every GitHub-backed repo shows as unhealthy ("not authorized") and syncs are being skipped. Our Engineering team has rolled out a fix to development and validated that the fix works. We will roll out the fix to production shortly and will provide another update.
Fixed October usage report visualization issue
Affected: Cost Management and Billing
-
This incident has been resolved.
-
We are currently back filling the missing data. We will provide another update once the backfill has been completed.
-
We are still working to backfill the correct data. Note that this did not affect billing, and is only a visualization issue.
-
There was an issue with our billing metrics exporter that caused us to mis-report usage for October at month-end. This is causing October usage to be reported as 0 in our cost management app. We are working to backfill the correct data. Note that this did not affect billing, and is only a visualization issue.
Fixed Increased query latency for Logs in GCP US Central (prod-us-central-0)
Affected: GCP US Central - prod-us-central-0, GCP US Central - prod-us-central-0: Rule Evaluation, Logs - GCP US Central - prod-us-central-0, Alerting and SLO - GCP US Central - prod-us-central-0: Rule Evaluation
-
This incident has been resolved. Some Logs queries in GCP US Central (prod-us-central-0) were slower than usual between 12:08 and 12:34 UTC. Some Metrics alert and recording rule evaluations in the same region were also delayed between 12:11 and 12:44 UTC. Both issues have been mitigated.
-
Some Logs queries in GCP US Central (prod-us-central-0) were slower than usual between 12:08 and 12:34 UTC. The issue is believed to be mitigated, and the team is monitoring while the cause is investigated.
Fixed Elevated Request Errors for Grafana Across Multiple Regions
Affected: AWS Australia - prod-au-southeast-1, AWS Australia - prod-au-southeast-2, AWS Brazil - prod-sa-east-1, AWS Canada prod-ca-central-1, AWS Canada - prod-ca-east-0, AWS Germany - prod-eu-west-2, AWS Germany - prod-eu-west-4, AWS Germany prod-eu-central-1, AWS India - prod-ap-south-1, AWS Indonesia - pr...
-
Between approximately 12:10 UTC and 13:22 UTC on 3 November (about 1 hour 12 minutes), Grafana across multiple Grafana Cloud regions experienced elevated request errors, causing slow-loading or failing dashboards and Explore queries. The issue has been resolved and service has been fully restored.
-
We have identified the cause of the elevated request errors affecting Grafana across multiple Grafana Cloud regions and have applied a mitigation. We are seeing signs of recovery and are continuing to monitor closely. Customers may still see slow-loading or failing dashboards and Explore queries while recovery continues. Next update by 14:00 UTC.
-
We have identified the cause of the elevated request errors affecting Grafana across multiple Grafana Cloud regions and have applied a mitigation. We are seeing early signs of recovery and are monitoring closely. Customers may still see slow-loading or failing dashboards and Explore queries while recovery continues. Next update by 13:30 UTC.
-
We have identified the cause of the elevated request errors affecting Grafana across multiple Grafana Cloud regions and are applying mitigation. Customers may still see slow-loading or failing dashboards and Explore queries while recovery continues. Next update by 13:30 UTC.
-
We are investigating some failed requests affecting Grafana across multiple Grafana Cloud regions, beginning at approximately 12:10 UTC. Customers may see slow-loading or failing dashboards and Explore queries, and some requests may time out or be cancelled. Our engineers are actively investigating. Next update by 13:30 UTC.
Fixed Grafana Cloud: k6 timeouts
-
We had a transient database slowdown causing a limited number of customers' k6 cloud runs to time out or abort in a window of a few minutes after Nov 2, 15:00 UTC. We are investigating the cause.
Fixed Missing Metrics for Some Synthetic Monitoring Checks using the Montreal, North Virginia, and North California public probes
-
Between approximately 08:09 and 09:10 UTC on 2 November (about 1 hour 11 minutes), a subset of Synthetic Monitoring checks running from the Montreal, North Virginia, and North California public probe locations experienced missing metrics, which may have appeared as gaps in dashboards. Specifically this affected: Checks with the Montreal Public Probe from 08:09-09:00 UTC Checks with the North Virginia Public Probe from 08:22-09:06 UTC Checks with the North California Public Probe from 08:43-09:20 UTC This has been fully resolved and all services are operating normally.
Fixed Metrics Alert Rule Evaluation Failures in AWS Australia (prod-au-southeast-1)
Affected: AWS Australia - prod-au-southeast-1: Rule Evaluation, Alerting and SLO - AWS Australia - prod-au-southeast-1: Rule Evaluation
-
Between approximately 08:00 and 09:40 UTC (about 1 hour 40 minutes), some customers in AWS Australia (prod-au-southeast-1) experienced intermittent failures when evaluating alert and recording rules, which may have caused missed or delayed alert notifications and gaps in recorded series. This has been fully resolved and rule evaluation is operating normally.
-
We continue to investigate intermittent failures when evaluating alert and recording rules in AWS Australia (prod-au-southeast-1), first observed at approximately 08:00 UTC. Some customers may see rules fail to evaluate or be delayed, which can result in missed or delayed alert notifications and gaps in recorded series. We are continuing to investigate. Next update by 11:15 UTC.
-
We are investigating an elevated rate of failures when evaluating Metrics alert and recording rules in AWS Australia (prod-au-southeast-1). Some customers may see rules missed or delayed rule evaluations, which can result in missed or delayed alert notifications and gaps in recorded series. Next update by 10:20 UTC.
Fixed IRM Unable to Voice Call Brazil Numbers
Affected: Incident Management and Response (IRM)
-
Brazil calls recovered at about 13:00 UTC on 3 November. At this point, we are marking the incident as resolved.
-
We are starting to see signs of recovery therefore some users might see voice calls working fine for them, but the issue is not fully resolved yet. We are continuing our efforts towards a complete resolution and an update will follow as soon as we have more info. We encourage usage of SMS and mobile push as alternative notification mechanism in the meantime.
-
Our efforts towards a resolution continues. We encourage usage of SMS and mobile push as alternative way in the meantime. Thank you for your patience.
-
We are continuing to work on a resolution, and an update will follow as soon as we have more info. Users should configure mobile push or SMS as notifications.
-
We are currently investigating an issue impacting Voice calls to Brazil for IRM. We are working on a resolution, and an update will follow as soon as we have more info. Users should configure mobile push or SMS as notifications.
Fixed Frontend Observability Outage in prod-eu-west-2
Affected: AWS Germany - prod-eu-west-2, Frontend Observability - AWS Germany - prod-eu-west-2
-
This incident has been resolved.
-
We are currently investigating an issue impacting Frontend Observability since 15:20 UTC. We will provide another update as soon as we have more to share.
Fixed Degraded Cloud Integrations
Affected: Integrations
-
This incident has been resolved.
-
Things are no longer degraded. We are currently monitoring the issue
-
We are continuing to investigate this issue.
-
We are currently investigating an issue impacting Cloud Integrations in prod-eu-west-3. We will provide another update when we have more to share.
Fixed ingestion errors in mimir-prod-66
Affected: AWS US East (VA) - prod-us-east-3, Metrics - AWS US East (VA) - prod-us-east-3
-
the issue is resolved now, we're watching the cell
-
read path is also affected.
-
The issue has been identified, we are working on a fix
Fixed Some Grafana Instances Experiencing Issues Coming Online after Restart
Affected: AWS Australia - prod-au-southeast-1, AWS Australia - prod-au-southeast-2, AWS Brazil - prod-sa-east-1, AWS Canada prod-ca-central-1, AWS Canada - prod-ca-east-0, AWS Germany - prod-eu-west-2, AWS Germany - prod-eu-west-4, AWS Germany prod-eu-central-1, AWS India - prod-ap-south-1, AWS Indonesia - pr...
-
This incident has been resolved.
-
A fix as been implemented and Hosted Grafana instances are back to normal levels. We will continue to monitor the issue.
-
We are continuing to work on a fix for this issue.
-
Starting at approximately 12:37 UTC, a some Hosted Grafana instances across multiple regions have been experiencing availability issues. Our team has identified the root cause and a fix is currently in progress. Affected instances will recover automatically once the fix has been applied. No action is required on your end. We will provide further updates as they become available and apologize for any disruption this may cause.
Fixed Elevated Trace Ingestion Latency and Errors for Grafana Cloud Traces in AWS Germany
Affected: AWS Germany - prod-eu-west-2, AWS Germany - prod-eu-west-2: Ingestion, Traces - AWS Germany - prod-eu-west-2: Ingestion, OpenTelemetry Ingest Endpoint - AWS Germany - prod-eu-west-2
-
Between 09:31 and 10:13 UTC on 23 October 2026 (42 minutes), Grafana Cloud Traces in AWS Germany experienced elevated ingestion latency and intermittent trace write failures, affecting both direct trace ingestion and ingestion via the OpenTelemetry endpoint. All services are now operating normally.
-
We are investigating elevated latency and intermittent errors when ingesting traces for Grafana Cloud Traces in AWS Germany. Customers may see delayed trace ingestion and failed trace writes. Next update by 10:30 UTC.
Fixed Some GCK6 App Project Pages are Failing to Load
Affected: GCk6 App, Performance and Load Testing - GCk6 App
-
This incident has been resolved.
-
We are continuing to work on a fix for the issue.
-
We are currently investigating this issue impacting some GCK6 app project pages. We are in the process of providing a fix for this.
Fixed Increased timeout errors in alert rule evaluations (AWS Germany, prod-eu-west-2)
Affected: AWS Germany - prod-eu-west-2: Rule Evaluation, Alerting and SLO - AWS Germany - prod-eu-west-2: Rule Evaluation
-
This incident has been resolved.
-
Remediation measures have been applied, and we are monitoring the recovery.
-
The root cause of the issue has been indentified and we are working on the remediation steps.
-
Since approximately 20:30 UTC on October 20, we have observed an increase in alert rule evaluation errors affecting rules that query Grafana Cloud Prometheus (Mimir) data sources in Cluster AWS Germany. Our engineering team is actively investigating and working on remediation.
Fixed Possible incorrect evaluation of Synthetic Monitoring alert rules in cluster prod-us-east-3
Affected: AWS US East - prod-us-east-3: API, AWS US East - prod-us-east-3: Public Probes, Synthetic Monitoring - AWS US East - prod-us-east-3: API, Synthetic Monitoring - AWS US East - prod-us-east-3: Public Probes
-
As of 21 Oct, 06:20 am UTC, we became aware of an issue with possible incorrect evaluation of Synthetic Monitoring alert rules in cluster prod-us-east-3. The issue has been ended 07:00 am UTC
Fixed DB issues in prod-sa-east-1
Affected: AWS Brazil - prod-sa-east-1, AWS Brazil - prod-sa-east-1: API, AWS Brazil - prod-sa-east-1: Public Probes, Grafana - AWS Brazil - prod-sa-east-1, Synthetic Monitoring - AWS Brazil - prod-sa-east-1: API, Synthetic Monitoring - AWS Brazil - prod-sa-east-1: Public Probes
-
This incident has been resolved.
-
Synthetic Monitoring alerting has recovered. We are continuing to monitor.
-
Synthetic Monitoring alerting is also impacted. We are continuing to investigate this issue.
-
We are currently investigating an issue in the prod-sa-east-1 region causing slow requests, or some stacks struggling to start. We will provide an update as soon as we have more information to share.
Frequently asked questions
Is Grafana Cloud down right now?
No. As of 20:00 UTC on 19 November 2026, Grafana Cloud is working normally. If it is not working for you, try the checklist on this page.
When was the last Grafana Cloud outage?
The last incident was "Increased Read Latency In prod-us-central-0 Region" on 19 November 2026, fixed after 1 hour 18 minutes.
Why is Grafana Cloud not working for me?
If this page shows no problem and few readers report one, the cause is usually local: your connection, a VPN or firewall, an outdated app or a sign-in problem. Work through the checklist above, then report it here so other readers can see it.
Unofficial status page. Teczpert is not affiliated with Grafana Cloud. Status data comes from the official status page and is checked every 15 minutes; reports come from readers. Official source: status.grafana.com.