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
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.
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.
April 2026
Tempo Write Outage
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
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 within an hour.
investigating
We are currently investigating a write outage affecting prod-us-east-3. The issue began at 18:50 UTC. Users may experience errors, timeouts, or unavailability while we work to identify the cause and restore service.
K6 Browser Testing/Timeline Not Available
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We’re currently investigating an issue affecting browser testing.
Users running browser tests will not be able to see the browser timeline.
Our team is actively working to identify the cause and will share an update within two hours.
Thank you for your patience.
Unable to Edit Notification Policies
minorSource not attested
Last archived state: resolved
View archived record details
identified
We’ve identified the cause of the issue impacting notification policies. Our team is currently implementing a fix. We’ll provide another update in 2 hours or sooner if the situation changes.
identified
We’ve identified the cause of the issue impacting notification policies. Our team is currently implementing a fix. We’ll provide another update in 2 hours or sooner if the situation changes.
investigating
We’re currently investigating an issue affecting notification policies. Our team is actively working to identify the cause and will share an update within 2 hours. Thank you for your patience.
Notification Policies and Contact Points Missing in UI on the Slow Release Channel
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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 within 2 hours.
identified
We’ve identified the cause of the issue impacting the Notification Policy and Contact Point UI. Our team is currently implementing a fix.
We’ll provide another update when the fix is deployed and we monitor the expected improvement.
investigating
We’re continuing to investigate the issue with the alerting UI. While we don’t have new information to share yet, our team is working to identify the root cause. Next update in 2 hours.
investigating
We’re currently investigating an issue affecting notification policies and contact points for instances on the slow release channel. Alerting API calls for contact points and notification policies return data as expected, so this appears to be limited to the UI.
Our team is actively working to identify the cause and will share an update within 1-2 hours. Thank you for your patience.
Partial K6 Test Run Outage
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We're experiencing an outage affecting test runs that use k6 extensions. The issue prevents users from executing these types of test runs both locally and in Grafana Cloud.
Test runs that do not use extensions are not affected by this incident.
AWS integration Degraded Performance
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating a noticeable drop in active series for the AWS integration that began around 18:15 UTC.
This issue may cause scrapes to hit rate limits, which can result in individual data points not being collected for the serverless integration. The impact is intermittent and may affect any customer using the AWS integration, regardless of region.
We are currently working to identify the cause and will provide an update as soon as we have more information.
Query degradation and possible rule evaluation failure on prod-eu-west-0.cortex-prod-01
minorSource 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 currently observing delays in ingesting data, possibly causing partial query results and failed rule evaluations for prod-eu-west-0.cortex-prod-01 metrics cell.
March 2026
Some of the CloudWatch queries are failing
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
Some of the CloudWatch queries were failing.
Started at 08:37 UTC
Monitoring from 09:21 UTC
Some Grafana Instances Unavailable
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
identified
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.
investigating
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.
investigating
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.
investigating
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.
Prometheus writes in prod-eu-west-3 are degraded
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
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.
monitoring
We are still seeing intermittent issues and continue to seek a resolution
monitoring
We are continuing to monitor for any further issues.
monitoring
We are continuing to monitor this through the weekend.
monitoring
We are continuing to monitor the previously impacted environments.
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are continuing to investigate this issue.
investigating
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.
