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.
June 2026
Rule Evaluation Outage in prod-us-central-0
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We’re continuing to track progress post-mitigation. While we don’t have new information to share yet, our team remains actively engaged.
monitoring
We had an outage affecting rule evaluations between 15:16-15:59 UTC in the prod-us-central-0 region.
Our team quickly identified the issue and has since mitigated. The engineering team is monitoring.
Issues with actions in the Grafana IRM mobile app
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We've verified a fix in our staging environment to restore functionality to the mobile app. The fix is currently being deployed to production. Thanks for your patience as we continue to roll this out and monitor the resolution.
identified
We're noticing an uptick in users being unable to respond to actions on the mobile app (acknowledging and silencing alerts, for example). Users working in the web UI should not be affected. Ingestion and notification delivery are working as expected. We have a fix in place and are in the process of deploying.
Potential Issues Loading Grafana for Users in India
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Error rates have remained near zero, and we continue to monitor.
monitoring
We are continuing to monitor for further issues.
monitoring
We have deployed additional mitigations that should help with remaining errors. We are continuing to monitor error rates.
monitoring
We’ve verified and begun to implement a fix that will improve loading errors. We are continuing to roll this out to all regions and monitor for efficacy.
monitoring
We're actively monitoring this issue and working with our 3rd party provider. The next update will be sent on Monday unless there's new information to share.
monitoring
Due to the linked GCP outage below, users located in India may have trouble loading parts of Grafana.
https://status.cloud.google.com/incidents/5fGQt4VbkDnr3Yp8PXPr
We are continuing to work with our CSP on this investigation.
Impacted users may receive intermittent error messages such as "Error Loading" or "Failed to load Assets". To be clear, it does not matter the region the stack is located, but the geography where the user is physically in.
monitoring
Due to the linked GCP outage below, users located in India may have trouble loading parts of Grafana.
https://status.cloud.google.com/incidents/5fGQt4VbkDnr3Yp8PXPr
Impacted users may receive intermittent error messages such as "Error Loading" or "Failed to load Assets". To be clear, it does not matter the region the stack is located, but the geography where the user is physically in. We continue to work with our CSP on this investigation.
investigating
Due to the linked GCP outage below, users located in India may have trouble loading parts of Grafana.
https://status.cloud.google.com/incidents/5fGQt4VbkDnr3Yp8PXPr
Impacted users may receive error messages such as "Error Loading" or "Failed to load Assets". To be clear, it does not matter the region the stack is located, but the geography where the user is physically in. We are currently investigating this issue from our end, and will provide updates as they are available.
Degraded k6 cloud UI performance
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
The root cause of the issue has been identified and a fix has been successfully deployed. We are observing widespread improvements across all systems. Our team is currently monitoring the environment to ensure performance remains stable.
investigating
We are continuing to investigate this issue.
investigating
We’re currently investigating an issue resulting in degraded k6 cloud UI performance and API response time. Our team is actively working to rectify this issue.
Frontend Observability - Suspected commit feature not working as expected
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We’re currently investigating an issue affecting Frontend Observability product. The "Suspected commit" feature is not currently working as expected. Ingestion and querying is unaffected by this. Our team has identified the cause and is actively working on a fix. Thank you for your patience.
Loki data source-managed alert rules not visible in the Grafana Cloud Alerting UI
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 are continuing to deploy the fix and monitor recovery efforts. As part of the rollout, we identified an issue that required adjustments to our deployment plan, which has extended the timeline for mitigation. Work remains actively underway, and we will share additional updates as progress continues.
identified
Deployment of the fix is still in progress. We are continuing to monitor the rollout and validate recovery across affected systems. We will share further updates as they become available.
identified
Our Engineering Team has implemented a fix which is now being rolled out. We will continue to monitor the situation and update as soon as we have more information.
identified
We have identified an issue where alert rules and alerts managed directly in a Loki data source (data source-managed alerting) are not displayed in the Grafana Cloud Alerting UI. Rules created via Prometheus/Mimir data sources and Grafana-managed alert rules are not affected.
Impact is limited to visibility and management in the UI. Affected alert rules continue to evaluate and send notifications normally — there is no impact to alert delivery.
Workaround: Loki alert rules can still be vi...
Grafana Dashboards page not displaying when set to ‘View by Folders’
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We’re currently investigating an issue affecting The Grafana Dashboards page. When set to view by folders, is currently experiencing an issue where no dashboards are shown. Our team is working on fixing the problem. In the meantime, switching to ‘View as list’ allows access to dashboards as usual”.
Investigating Issues with Data Source-Managed Alerting
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Our team has implemented a fix and we are currently monitoring the results of this.
investigating
We are currently investigating an issue affecting data source-managed alerting management functionality in Grafana Cloud.
Customers may experience problems viewing, creating, updating, or managing alerts through Grafana when using data source-managed alerting. This issue is limited to alert management functionality within Grafana.
Alert evaluation and backend alerting services continue to operate normally. Direct alerting APIs for Mimir and Loki remain fully operational and are unaffected.
...
IRM Degraded Performance
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We've released a fix to the IRM app that should restore service for affected customers with issues related to labels. Thanks for your patience while investigating. We're continuing to monitor as we confirm the resolution in place.
identified
We are continuing to work on a fix for this. To further clarify, this issue is not about accessing IRM or alert ingestion/notification/delivery, but rather with handling labels.
identified
The degraded performance is about labels, and we have seen this degradation in more regions.
identified
We are continuing to work on a fix for this issue.
identified
The issue has been identified and a fix is being implemented.
investigating
We are continuing to investigate this issue.
investigating
We are experiencing access issues in IRM as there are elevated 500 API responses in prod-us-central-0.
Brief Rule Evaluation Failures in prod-eu-west-3
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The incident has been mitigated, and services are operating normally. We continue to monitor the service to ensure full stability.
monitoring
The incident has been mitigated, and services are operating normally. We are currently monitor the service to ensure full stability.
investigating
We’re making ongoing progress on the investigation alongside our upstream provider.
investigating
We are continuing to investigate this issue.
investigating
Intermittent spikes in rule evaluations continuing.
investigating
From 00:20:00 to 00:27:00 and again 00:32:00 to 00:38:00 there were brief spikes in rule evaluation failures. Engineers are investigating.
