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.
May 2026
Intermittent Errors and High latency Writing to Cloud Metrics, Cloud Logs and Cloud Traces
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We continue to see signs of recovery and improved stability across impacted services. Our teams continue to closely monitor the situation while working with the cloud provider.
monitoring
We continue to see signs of recovery and improved stability across impacted services. Our teams continue to closely monitor the situation while working with the cloud provider.
monitoring
We are seeing signs of recovery and improved stability across impacted services over the past hour. Our teams continue to closely monitor the situation while working with the cloud provider.
investigating
We have identified expanded impact affecting Grafana Cloud Logs and Grafana Cloud Traces in addition to Cloud Metrics, causing intermittent errors and increased latency when writing data. Our teams continue working on a fix and investigating the issue with the cloud provider’s support team.
investigating
We’re continuing to investigate the issue causing intermittent errors and high latency when writing to Cloud Metrics. We are in contact with the cloud provider’s support team, and they are investigating the issue alongside us.
investigating
We’re currently investigating an issue causing intermittent errors and high latency when writing to Cloud Metrics. Our team is actively working to identify the cause. Thank you for your patience.
"Failed to Load Dashboard" Errors
majorSource not attested
Last archived state: resolved
View archived record details
identified
The fix is currently being rolled out to all impacted environments.
identified
Our teams continue working on a fix for this issue. We do not have additional information to share at this time, but we will continue to provide updates as progress is made.
identified
We are continuing to work on a fix for this issue. While we do not have additional updates to share at this time, our teams remain actively engaged and we will provide further updates as soon as they become available.
identified
Customers on Grafana Cloud may see an error on dashboard panels with "Failed to load dashboard ... json unmarshal number ...". We have identified the issue and are working to deploy out the fix.
SSL/TLS Connectivity Issues
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating reports of service disruption affecting a subset of customers.
Customers may experience intermittent connectivity issues, degraded performance, or SSL/TLS certificate validation errors when accessing affected services. Our engineering teams are actively working to identify the scope of impact and restore full functionality as quickly as possible.
We will continue to provide updates as more information becomes available.
Cloud Metrics -High Write Latency and Errors in prod-us-central-7
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
From approximately 20:40-21:00 UTc, we experienced an issue affecting Grafana Cloud Metrics in prod-us-central-7. Affected users may have experienced high latency and/or errors during ingestion and rule evaluation.
Our team has identified the cause and mitigated. We are currently monitoring for long-term stability.
Metrics read errors in prod-ap-south-1 region
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
Engineering has released a fix and as of 07:50 UTC, customers should no longer experience errors when querying metrics. We will continue to monitor for recurrence and provide updates accordingly.
investigating
From approximately 06:24 UTC, we were alerted to an issue with read errors in mimir-prod-43. Users with instances hosted in the prod-ap-south-1 region experiencing this issue may encounter an error message when querying metrics.
Engineering is actively engaged and assessing the issue. We will provide updates accordingly.
Datasource Query Performance Issues
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We’re currently investigating an issue affecting Datasource query performance in prod-us-east-4. Our team is actively working to identify the cause. Thank you for your patience.
Elevated Error Rate of Browser Checks in PoP Oregon
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.
identified
We’ve identified the cause of the issue impacting browser checks. Our team is currently implementing a fix.
investigating
We’re currently investigating an issue affecting browser checks in the PoP Oregon region. Our team is actively working to identify the cause. Thank you for your patience.
k6 Partial 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.
investigating
After further investigation, this issue may also be affecting Synthetic Monitoring.
We continue to identify the cause and will update as soon as we have more information.
investigating
We’re currently investigating an issue affecting k6. Our team is actively working to identify the cause. Thank you for your patience.
Ingestion Errors for AWS Cloud Provider Observability Metric Streams in prod-us-central-7
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 investigating an issue with ingesting Metrics for AWS Cloud Provider Observability with Metric Streams. Users experiencing this issue may encounter ingestion errors in the "prod-us-central-7" region only starting from ~06:30UTC.
Engineering is actively engaged and assessing the issue. We will provide updates accordingly.
We’ve identified the cause of the issue impacting SQL datasources. Our team is currently implementing 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 currently investigating reports of issues affecting SQL-based data sources where users are unable to save credentials.
This appears to impact a subset of customers and may be occurring across multiple regions. We are actively working to determine the scope and root cause.
We will provide updates as more information becomes available.
