Grafana.comSupport TicketsIntegrationsCost Management and BillingFleet ManagementIncident Management and Response (IRM)GCP UK - prod-gb-south-0Public SnapshotsGCP UK - prod-gb-south-0GCP UK - prod-gb-south-0GCP UK - prod-gb-south-0GCP UK - prod-gb-south-0GCP UK - prod-gb-south-0GCP UK - prod-gb-south-0GCP UK - prod-gb-south-0GCP UK - prod-gb-south-0GCP UK - prod-gb-south-0: APIGCP UK - prod-gb-south-0: QueryingGCP UK - prod-gb-south-0: Public ProbesGCP UK - prod-gb-south-0: IngestionGCP UK - prod-gb-south-0: Rule EvaluationGCP UK - prod-gb-south-0: Alertmanager and Rules Configuration APIGCP UK - prod-gb-south-0: QueryingGCP UK - prod-gb-south-0: AlertmanagerGCP UK - prod-gb-south-0: IngestionGCP UK - prod-gb-south-0: Metrics Generator
identified
We are seeing errors in Frontend o11y again. We are continuing to investigate and monitor the impacted services.
identified
Between 06:15 and 12:15 UTC, Grafana Cloud Frontend Observability in GCP UK (prod-gb-south-0) experienced errors accepting incoming telemetry data. This has been resolved and Frontend Observability is operating normally in this region. We are continuing to investigate and monitor the remaining impacted services.
investigating
We are continuing to investigate this issue.
investigating
We are continuing to investigate this issue.
investigating
As of 06:30 UTC, we became aware of to an issue with Grafana Cloud unavailibity in the prod-gb-south-0 region.
Engineering is actively engaged and assessing the issue. We will provide updates accordingly.
We are continuing to monitor for any further issues.
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are continuing to investigate this issue.
investigating
We’re currently investigating an issue affecting metrics reads and rule evaluations in mimir-prod-66. Our team is actively working to identify the cause. Thank you for your patience.
The fix has been implemented, and we are monitoring the results.
identified
We have noticed improvements across services. We will now be applying a more permanent fix. Impacted users may experience a disruption in the auth-api service of up to 15min while we apply a DB patch that will improve performance.
identified
The issue has been identified, and we have applied mitigations on our end. We are currently observing the progress.
investigating
We are investigating increased authentication errors affecting Grafana Cloud in the prod-us-west-0 region.
Customers may experience intermittent failures for requests that require authentication.
Our engineering team has identified database performance degradation affecting the authentication service and is investigating the underlying cause.
We will provide another update as more information becomes available.
We have put some mitigations in place which seem to have helped with the errors.
We continue to monitor the results.
investigating
We are continuing to investigate this issue.
investigating
A small number of customers with stacks in prod-us-central-4 are receiving "forbidden" errors when querying Prometheus data sources.
We are investigating and will provide an update soon.
Phone call notifications to numbers in Russia and Kazakhstan are blocked
Phone call notifications to numbers in Russia and Kazakhstan are still blocked. We are working to resolve the issue.
As SMS support is limited in these countries, we recommend using mobile push notifications as an alternative.
We do not currently have an estimated resolution time. We will provide further updates as more information becomes available.
investigating
Phone call notifications to numbers in Russia and Kazakhstan are currently blocked. We are working to resolve the issue.
As SMS support is limited in these countries, we recommend using mobile push notifications as an alternative.
We do not currently have an estimated resolution time. We will provide further updates as more information becomes available.
investigating
Phone call notifications to numbers in Russia and Kazakhstan are currently blocked. We are working to resolve the issue.
As SMS support is limited in these countries, we recommend using mobile push notifications as an alternative.
We do not currently have an estimated resolution time. We will provide further updates as more information becomes available.
Elevated Errors Ingesting Metrics in AWS US East (VA)
We have isolated infrastructure suspected of contributing to the metrics ingestion issue in AWS US East (VA) - prod-us-east-3. We are validating recovery and completing mitigation steps. Customers may continue to experience failed or delayed metric writes while this work continues.
identified
We have isolated infrastructure suspected of contributing to the metrics ingestion issue in AWS US East (VA) - prod-us-east-3. We are validating recovery and completing mitigation steps. Customers may continue to experience failed or delayed metric writes while this work continues.
identified
We have identified the cause of an issue affecting metrics ingestion for Grafana Cloud Metrics customers in AWS US East (VA) - prod-us-east-3. Customers may see failed or delayed writes to Grafana Cloud Metrics, this may also impact Metrics written by Frontend Observability and/or Synthetic Monitoring. We are continuing to work on mitigations and are monitoring the impact to Grafana Cloud Metrics. Next update by 14:00 UTC.
identified
We have identified the cause of an issue affecting metrics ingestion for Grafana Cloud Metrics customers in AWS US East (VA) - prod-us-east-3. Customers may see failed or delayed writes to Grafana Cloud Metrics, this may also impact Metrics written by Frontend Observability and/or Synthetic Monitoring. We are continuing to work on mitigations and are monitoring the impact to Grafana Cloud Metrics. Next update by 13:00 UTC.
investigating
We are continuing to investigate an issue affecting metrics ingestion for Grafana Cloud Metrics customers in AWS US East (VA). Customers may see failed or delayed writes to Grafana Cloud Metrics, this may also impact Metrics written by Frontend Observability and/or Synthetic Monitoring. Next update by 12:00 UTC.
investigating
We are continuing to investigate an issue affecting metrics ingestion for Grafana Cloud Metrics customers in AWS US East (VA). Customers may see failed or delayed writes. Next update by 11:00 UTC.
investigating
We are investigating an issue affecting metrics ingestion for Grafana Cloud Metrics customers in AWS US East (VA). Customers may see failed or delayed writes. Next update by 10:15 UTC.
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.
