New Multi-region uptime checks and custom-domain status pages

Grafana Cloud Outage History

Daily provider-status observations and published incident history for Grafana Cloud.

Regional incident

Grafana Cloud has an active regional incident; no global outage is indicated. Verified . Official provider source.

Looking for an update now? Check the current status, or follow Grafana Cloud for future changes.

21.1% of 38 verified observed days had no reported provider issue

90-Day Trend

Jul 23Oct 20

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Recorded Daily Status (Last 91 Days)

Jul 22 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

September 2026
IRM Access Issues for a Small Group of Users
major Observed active window 20h 12m

View incident details and source

Started:

Incident Management and Response (IRM)
monitoring
The fix has been deployed to the majority of deployments. We continue to monitor progress.
monitoring
A fix is currently being rolled out and will be deployed progressively over the next few hours. We appreciate your patience as this reaches all affected customers.
identified
The issue has been identified, and we are working on a fix.
investigating
We are currently investigating an issue that may cause a small group of users to experience unexpected IRM access issues, or undelivered pages. Most users should not be affected.
Increased Execution Time for Browser Checks in Synthetic Monitoring
minor Observed active window 1h 19m

View incident details and source

Started:

AWS Australia - prod-au-southeast-1: Public Probes AWS Brazil - prod-sa-east-1: Public Probes AWS Canada - prod-ca-east-0: Public Probes AWS Germany - prod-eu-west-2: Public Probes AWS India - prod-ap-south-1: Public Probes AWS Japan - prod-ap-northeast-0: Public Probes AWS Singapore - prod-ap-southeast-1: Public Probes AWS Sweden - prod-eu-north-0: Public Probes AWS US East - prod-us-east-0: Public Probes AWS US East - prod-us-east-3: Public Probes AWS US West - prod-us-west-0: Public Probes Azure Netherlands - prod-eu-west-3: Public Probes Azure US Central - prod-us-central2: Public Probes Azure US Central - prod-us-central7: Public Probes GCP Australia - prod-au-southeast-0: Public Probes GCP Belgium - prod-eu-west-0: Public Probes GCP Brazil - prod-sa-east-0: Public Probes GCP India - prod-ap-south-0: Public Probes GCP Singapore - prod-ap-southeast-0: Public Probes GCP UK - prod-gb-south-0: Public Probes GCP US Central - prod-us-central-0: Public Probes AWS UAE - prod-me-central-1: Public Probes AWS UK - prod-gb-south-1: Public Probes AWS Switzerland - prod-eu-central-0: Public Probes AWS Indonesia - prod-ap-southeast-2: Public Probes AWS Ireland - prod-eu-west-6: Public Probes GCP Saudi Arabia - prod-me-central-0: Public Probes GCP US East - prod-us-east-1: Public Probes
monitoring
A fix has been deployed and CPU throttling is returning to normal. Check execution times should return to baseline shortly. We will continue monitoring recovery. Next update by 11:56 UTC.
identified
A fix has been merged and is now being rolled out across affected locations. We are monitoring deployment progress. Next update by 11:49 UTC.
identified
Since September 9, 2026, some browser checks in Synthetic Monitoring may take longer to complete than usual, with impact varying by location. We have identified the cause and are actively working on a fix. Next update by 10:49 UTC.
Investigating elevated database load in AWS Germany
minor Observed active window 2h 32m

View incident details and source

Started:

AWS Germany - prod-eu-west-4
monitoring
A fix has been implemented and we have been seeing recovery to the affected region. We will continue to monitor.
investigating
We are investigating elevated database load affecting infrastructure supporting a subset of Grafana Cloud instances in the AWS Germany region (prod-eu-west-4). Affected users may experience slow responses when accessing Grafana. We will provide an update as more information becomes available.
Issues with Geomap Tiles
minor Observed active window 4h 39m

View incident details and source

Started:

AWS Australia - prod-ap-southeast-2 AWS Brazil - prod-sa-east-1 AWS Canada - prod-ca-east-0 AWS Germany - prod-eu-west-2 AWS Germany - prod-eu-west-4 AWS India - prod-ap-south-1 AWS Japan - prod-ap-northeast-0 AWS UAE - prod-me-central-1 AWS Singapore - prod-ap-southeast-1 AWS Sweden - prod-eu-north-0 AWS US East - prod-us-east-0 AWS US East - prod-us-east-2 AWS US West - prod-us-west-0 AWS Australia - prod-au-southeast-1 AWS UK - prod-gb-south-1 AWS Ireland - prod-eu-west-6 Azure US Central - us-central2 AWS Switzerland - prod-eu-central-0 Azure Netherlands - prod-eu-west-3 GCP Australia - prod-au-southeast-0 GCP Belgium - prod-eu-west-0 GCP Brazil - prod-sa-east-0 GCP India - prod-ap-south-0 GCP Singapore - prod-ap-southeast-0 GCP UK - prod-gb-south-0 GCP US Central - prod-us-central-0 GCP US Central - prod-us-central-3 GCP US Central - prod-us-central-4 GCP US East - prod-us-east-1 play.grafana.org Federal Cloud - AWS US Gov West GCP Saudi Arabia - prod-me-central-0 AWS US East - prod-us-east-3
identified
Some geomap tiles are displaying the “api key required". The issue has been identified, and our team is working on a fix. As a workaround, you can open the Geomap panel, navigate to the Map layers section, and change the Basemap layer from CARTO, or "Default base layer," to OpenStreetMap. The watermark should disappear immediately. Alternatively, if you would prefer to retain a dark-styled map similar to the current CARTO appearance, you can select MapLibre as the basemap and configure th...
High Latency in prod-us-east-2
minor Observed active window 4h 20m

View incident details and source

Started:

AWS US East - prod-us-east-2
monitoring
We have observed latency return to normal levels, and we will continue to monitor this incident.
investigating
We are currently investigating an issue causing high latency for deployments in the prod-us-east-2 cluster.
Degradation of Hosted Grafana in US Central Region
major Observed active window 3h 41m

View incident details and source

Started:

GCP US Central - prod-us-central-0 GCP US Central - prod-us-central-3 GCP US Central - prod-us-central-4
monitoring
We are currently observing minimal impact and continuing to monitor the situation.
identified
We are aware of an issue causing some Grafana Cloud stacks in the US region to be unavailable or fail to load. The cause is reduced compute capacity in one of our cloud provider's availability zones, which is preventing affected stacks from starting. Other regions are unaffected. We are working with our cloud provider to restore capacity.
US Central Region Instability
minor Observed active window 6h 14m

View incident details and source

Started:

GCP US Central - prod-us-central-0: Querying GCP US Central - prod-us-central-0: Ingestion GCP US Central - prod-us-central-5: Querying GCP US Central - prod-us-central-5: Ingestion GCP US Central - prod-us-central-0: Querying GCP US Central - prod-us-central-0: Ingestion GCP US Central - prod-us-central-0: Metrics Generator GCP US Central - prod-us-central-5: Querying GCP US Central - prod-us-central-5: Ingestion
monitoring
The underlying cloud provider issue is not yet fully resolved, but our systems have recovered and affected Grafana Cloud stacks are loading normally again. Some customers may still see brief intermittent slowness. We are continuing to monitor until our provider confirms resolution.
identified
We’re currently investigating an issue affecting the us central region due to ongoing cloud provider incident. Multiple components impacted. Our team is actively working on this. Thank you for your patience.
Alert rule creation, deletion, and update degradation in prod-us-east-2
minor Observed active window 2h 58m

View incident details and source

Started:

AWS US East - prod-us-east-0: Alertmanager and Rules Configuration API AWS US East - prod-us-east-0: Alertmanager
investigating
We’re currently investigating an issue affecting alert rule creation, deletion, and updates in prod-us-east-2. Our team is actively working to identify the cause. Thank you for your patience.
Tempo and Mimir Read and Write Failures
minor Observed active window 2h 46m

View incident details and source

Started:

AWS US West - prod-us-west-0: Querying AWS US West - prod-us-west-0: Ingestion AWS US West - prod-us-west-0: Querying AWS US West - prod-us-west-0: Ingestion
monitoring
Tempo recovered.
identified
Cluster Metrics are healthy for the last 15 minutes
identified
The issue has been identified and a fix is being implemented.
High Latency in prod-ap-south-1
major Observed active window 3h 17m

View incident details and source

Started:

AWS India - prod-ap-south-1 AWS India - prod-ap-south-1 AWS India - prod-ap-south-1: Ingestion AWS India - prod-ap-south-1: Ingestion
monitoring
A fix has been applied and we are seeing signs of recovery. We will continue to monitor the recovery.
investigating
We are currently investigating an issue impacting deployments in prod-ap-south-1. Impacted customers may be experiencing increased latency and issues with ingestion.

Legacy Incident Archive

101 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

February 2026
Grafana Cloud Metrics - Intermittent Write Latency in prod-us-central, prod-us-central-5, and prod-eu-west-0
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We are rolling out a mitigation across the environments in these regions, and preemptively where possible to ensure it doesn’t spread elsewhere.
monitoring
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.
monitoring
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.
monitoring
We are continuing to investigate this issue alongside the CSP. Any notable updates will continue to be shared here for tracking.
monitoring
We've implemented mitigation in place and are continuing to monitoring and investigating this issue.
investigating
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.
investigating
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.