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.
July 2026
Partial Outage in prod-eu-west-2
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.
investigating
We are continuing to investigate this issue.
investigating
We are investigating a broader issue affecting multiple Grafana Cloud products in prod-eu-west-2. This appears to be caused by a third-party provider issue rather than a Loki-specific problem.
Impact is currently inconsistent: some components are affected while others continue to function normally. We have also seen some impact to Tempo write paths.
We are continuing to investigate and will share another update as soon as we have more information.
investigating
We are investigating an issue affecting Loki queries in prod-eu-west-2.
We first observed this behavior at approximately 21:57 UTC. Affected users may see elevated query errors, timeouts, or intermittent failures when running Loki queries in this region.
The issue appears to be improving, but it is not fully resolved yet. We are continuing to investigate and will share another update as soon as we have more information.
Delayed Aggregated Metrics (prod-us-central-0)
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have applied the mitigation and are monitoring as the backlog catches up. We will post another update once that is complete.
Thank you for your patience.
identified
We are currently investigating a delay in aggregated metric results for tenants using Adaptive Metrics in the prod-us-central-0 region.
Our engineering team has identified the issue and is actively working on a mitigation. We will provide further updates as the investigation progresses.
Some Reports of Grafana Not Loading.
majorSource not attested
Last archived state: resolved
View archived record details
identified
The fix is in the process of being rolled out.
identified
We believe we have found the cause and are working on remediation. It is also worth mentioning that only stacks on the "slow" release channel are impacted.
investigating
We are currently investigating an issue impacting a small subset of stacks in the impacted regions. We will provide more details as they become available.
Mimir Write Performance Degradation
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
From 19:24 until 19:40 UTC, backend performance degradation impacted ingestion. We are currently monitoring.
Mimir Partial Write Outage
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The outage is recovered as of 16:56 UTC, and we're continuing to monitor.
identified
We're investigating backend degradation which has resulted in a partial write outage beginning around 16:40 UTC. This degradation has also impacted reads and rule evaluation. Issue has been identified and we are working on mitigation.
Issue with Dashboard Views Being Registered
minorSource not attested
Last archived state: resolved
View archived record details
identified
We are currently working on a fix related to this incident. There are no new updates to share at this time.
identified
We continue to work on resolving the issue impacting dashboard view and error counts. There are no new updates to share at this time. Our next update will be provided within 24 hours.
identified
We continue to work on resolving the issue impacting dashboard view and error counts. There are no new updates to share at this time. Our next update will be provided within 24 hours.
identified
We continue to work on resolving this issue. We'll provide another update within the next 24 hours, or sooner if additional information becomes available.
identified
We continue to work on resolving this issue. We'll provide another update within the next 24 hours, or sooner if additional information becomes available.
identified
We've identified the cause of the issue impacting dashboard view and error counts in the Dashboards and Folder list. Our team is currently working on implementing a fix and validating the solution. We will provide another update within the next 24 hours, or sooner if we have additional information to share.
investigating
This is related to https://status.grafana.com/incidents/rhrk2ck6ly0y which was resolved by mistake.
For some dashboards, the Views/Error counts in the Dashboards/Folder list renders as `-` and never updates, even after dashboards are viewed repeatedly. This is ultimately causing inaccurate or missing view counts.
We are continuing to investigate the underlying cause of this issue. At this time, the scope and impact remain unchanged, and we have no new information to share. We will provide ...
IRM Mobile App forcing some users to logout
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A new iOS mobile app version (v2.39.5) has been released, which includes a fix for this issue. We are monitoring the rollout and its impact to ensure the issue has been fully resolved. If you continue to experience any problems after updating to the latest version, please let us know.
identified
A fix has been submitted for review and will be released as Grafana Mobile v2.39.5 once it is approved.
If your app is currently on v2.39.3, we recommend not upgrading to v2.39.4 and instead waiting for v2.39.5 to become available.
Users who have already been signed out by this issue can log back into the app and continue using it.
We will provide another update once v2.39.5 is available.
investigating
Our investigation has narrowed the impact to version 2.39.4 of the Grafana mobile app on iOS. Users should avoid upgrading to this version until an updated release is available.
As a precaution, we also recommend ensuring you have alternative notification methods configured (such as SMS, email, or phone calls) if you rely on mobile push notifications for alerting.
We are actively working on a resolution and will provide another update as soon as more information is available.
investigating
We are aware of an issue in the latest mobile app release that is causing some users to be signed out and asked to log in again.
We have reproduced the behavior and are investigating and working on a fix. We will share another update as soon as we have more information.
Issue with Dashboard Views Being Registered
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are continuing to investigate the underlying cause of this issue. At this time, the scope and impact remain unchanged, and we have no new information to share. We will provide another update as soon as more information becomes available.
investigating
For some dashboards, the Views/Error counts in the Dashboards/Folder list renders as `-` and never updates, even after dashboards are viewed repeatedly
This is ultimately causing inaccurate or missing view counts.
PDC Degraded performance
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
We are now seeing recovery of PDC traffic to the affected customers. Our team will continue to monitor across shifts.
identified
We are continuing to see disruptions across multiple deployments, ranging from degraded performance to full outages for some customers.
Additional resources have been engaged to mitigate this issue. We will post updates as they become available.
monitoring
We are continuing to monitor for any further issues.
monitoring
We are seeing recovery in some deployments, while others not just yet. We are continuing to monitor this incident.
monitoring
A fix has been applied and we are seeing recovery. We will continue to monitor this.
investigating
We are still currently investigating the issue.
investigating
We are currently facing performance degradation on PDC service hosted on Multiple clusters. Our Engineering Team is currently working on fixing the issue, we do apologize for any inconvenience.
Delayed ingestion and recording rule evaluation failures for Mimir in prod-ap-south-1
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented. We are currently monitoring the results.
investigating
We are observing delayed ingestion and recording rule evaluation failures for Mimir in prod-ap-south-1. As of yet we have not noticed any customer impact however we are currently observing the cell.
