AWS Australia - prod-au-southeast-1: Public ProbesAWS Brazil - prod-sa-east-1: Public ProbesAWS Canada - prod-ca-east-0: Public ProbesAWS Germany - prod-eu-west-2: Public ProbesAWS India - prod-ap-south-1: Public ProbesAWS Japan - prod-ap-northeast-0: Public ProbesAWS Singapore - prod-ap-southeast-1: Public ProbesAWS Sweden - prod-eu-north-0: Public ProbesAWS US East - prod-us-east-0: Public ProbesAWS US East - prod-us-east-3: Public ProbesAWS US West - prod-us-west-0: Public ProbesAzure Netherlands - prod-eu-west-3: Public ProbesAzure US Central - prod-us-central2: Public ProbesAzure US Central - prod-us-central7: Public ProbesGCP Australia - prod-au-southeast-0: Public ProbesGCP Belgium - prod-eu-west-0: Public ProbesGCP Brazil - prod-sa-east-0: Public ProbesGCP India - prod-ap-south-0: Public ProbesGCP Singapore - prod-ap-southeast-0: Public ProbesGCP UK - prod-gb-south-0: Public ProbesGCP US Central - prod-us-central-0: Public ProbesAWS UAE - prod-me-central-1: Public ProbesAWS UK - prod-gb-south-1: Public ProbesAWS Switzerland - prod-eu-central-0: Public ProbesAWS Indonesia - prod-ap-southeast-2: Public ProbesAWS Ireland - prod-eu-west-6: Public ProbesGCP Saudi Arabia - prod-me-central-0: Public ProbesGCP 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
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.
AWS Australia - prod-ap-southeast-2AWS Brazil - prod-sa-east-1AWS Canada - prod-ca-east-0AWS Germany - prod-eu-west-2AWS Germany - prod-eu-west-4AWS India - prod-ap-south-1AWS Japan - prod-ap-northeast-0AWS UAE - prod-me-central-1AWS Singapore - prod-ap-southeast-1AWS Sweden - prod-eu-north-0AWS US East - prod-us-east-0AWS US East - prod-us-east-2AWS US West - prod-us-west-0AWS Australia - prod-au-southeast-1AWS UK - prod-gb-south-1AWS Ireland - prod-eu-west-6Azure US Central - us-central2AWS Switzerland - prod-eu-central-0Azure Netherlands - prod-eu-west-3GCP Australia - prod-au-southeast-0GCP Belgium - prod-eu-west-0GCP Brazil - prod-sa-east-0GCP India - prod-ap-south-0GCP Singapore - prod-ap-southeast-0GCP UK - prod-gb-south-0GCP US Central - prod-us-central-0GCP US Central - prod-us-central-3GCP US Central - prod-us-central-4GCP US East - prod-us-east-1play.grafana.orgFederal Cloud - AWS US Gov WestGCP Saudi Arabia - prod-me-central-0AWS 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...
GCP US Central - prod-us-central-0GCP US Central - prod-us-central-3GCP 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.
GCP US Central - prod-us-central-0: QueryingGCP US Central - prod-us-central-0: IngestionGCP US Central - prod-us-central-5: QueryingGCP US Central - prod-us-central-5: IngestionGCP US Central - prod-us-central-0: QueryingGCP US Central - prod-us-central-0: IngestionGCP US Central - prod-us-central-0: Metrics GeneratorGCP US Central - prod-us-central-5: QueryingGCP 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
AWS US East - prod-us-east-0: Alertmanager and Rules Configuration APIAWS 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.
AWS US West - prod-us-west-0: QueryingAWS US West - prod-us-west-0: IngestionAWS US West - prod-us-west-0: QueryingAWS 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.
AWS India - prod-ap-south-1AWS India - prod-ap-south-1AWS India - prod-ap-south-1: IngestionAWS 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.
Investigating issues in US Central (prod-us-central-0, prod-us-central-5)
We have identified the cause as an issue in our cloud provider’s US Central region. A mitigation is in place and recovery is in progress. Customers in prod-us-central-0 and prod-us-central-5 may still see errors or delays with metrics, logs, or Grafana while services come back. We will update this page as recovery continues.
investigating
We are investigating reports of errors affecting Grafana Cloud in US Central (prod-us-central-0, prod-us-central-5). Customers in this region may see timeouts or failed requests when writing or querying logs and metrics. We are looking into this and will post another update as soon as we have more information.
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.
August 2026
Incident Management unavailable in US Central
minorSource not attested
Last archived state: resolved
View archived record details
Incident Management and Response (IRM)
monitoring
A fix has been applied and Incident Management in US Central is recovering. The Incident public API is responding normally, and customers can create, view, and query Incidents again. We are continuing to monitor the recovery to confirm the service is fully stable.
investigating
We are investigating an outage affecting Grafana Incident in the US Central region (prod-us-central-0). Customers are unable to create, view, or query Incidents, and requests to the Incident public API are timing out. All customers in this region are affected.
Grafana OnCall is not impacted — alert ingestion, alert group creation, and notification delivery are all operating normally.
K6 Test Outage
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
Telemetry push APIs went down at 15:06 UTC, causing tests to lose telemetry data, like metrics, logs, traces, and browser screenshots.
This issue has now been mitigated, and we are monitoring to determine root cause as well as full resolution.
Some Grafana Instances Unavailable
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
We have rolled out a change to the affected regions to restore services.
investigating
We have identified the cause: our cloud provider has exhausted compute capacity in the affected region. We are working directly with them and are moving affected workloads to alternative capacity to restore service.
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating an issue that causing some Grafana deployments in prod-us-central-0 and prod-us-central-3 to become unavailable.
Logs latency increase within prod-eu-west-3
minorSource not attested
Last archived state: resolved
View archived record details
investigating
There's still a minor latency increase in this cell however we have identified that it is improving although not back to normal as of yet. We will continue to look into this.
investigating
We have identified minor latency increases in write endpoints within the prod-eu-west-3. Our team is currently monitoring and investigating this.
K6 - Cloud test-run issues
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A critical piece of infrastructure behaved poorly after a reboot. It has now been properly recovered
investigating
We are currently investigating an issue which is resulting in some test runs to abort and metrics data to be incomplete for a subset of tests
July 2026
Degraded Performance: Stack Provisioning Failures within certain reigons (PDC Setup)
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating an issue impacting stack provisioning. Attempting to set up PDC on newly created stacks will currently fail across several regions. We are currently looking into the cause of this.
PDC Authentication Issues
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are continuing to investigate this issue.
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating an issue impacting PDC authentication. We will provide additional updates as they become available.
Issues with Billing/Usage Dashboard Metrics and Panels.
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
We have identified the issue, and are working on deploying a fix.
investigating
We are investigating an outage for the Billing / Usage dashboard metrics and panels. This appears to be partially affecting organizations using Grafana Cloud.
We are working on identifying and resolving the issue
IRM Performance Degradation in EU Region
minorSource not attested
Last archived state: resolved
View archived record details
identified
We have identified the underlying issue affecting Grafana IRM in our EU region and are actively working to restore normal service.
Users may continue to experience a degraded or unresponsive IRM UI, reduced availability of the public API, and delays in notifications while mitigation efforts are underway.
Our engineering team is working to restore full functionality as quickly as possible. We will provide another update as more information becomes available.
investigating
We are currently investigating an issue affecting Grafana IRM in our EU region. Users may experience a degraded or unresponsive IRM UI, reduced availability of the public API, and delays in notifications.
Our engineering team is actively investigating the issue and working to restore normal service. We will provide another update as more information becomes available.
Partial OTLP Write Outage in prod-us-east-3
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating an issue affecting OTLP ingestion in the prod-us-east-3 region. Customers may experience intermittent failures when writing telemetry to the OTLP endpoint. Based on current information, logs are confirmed to be affected, and metrics and traces may also be impacted.
Our investigation indicates intermittent failures began around 08:00 UTC, with the primary period of impact occurring between 15:30 UTC and 17:45 UTC. We are continuing to investigate the scope and root cause ...
