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
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.
Degraded Performance with Increased Latency for Grafana Cloud Metrics and Traces in GCP US Central
GCP US Central - prod-us-central-0GCP US Central - prod-us-central-5GCP US Central - prod-us-central-0: IngestionGCP US Central - prod-us-central-5: IngestionGCP US Central - prod-us-central-0: Ingestion
investigating
We are investigating degraded performance and increased latency in the ingestion path for Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5) and Grafana Cloud Traces in prod-us-central-0.
Customers may experience intermittent errors or delays when sending metrics and traces.
We continue to investigate the issue with our cloud provider. We do not have an estimated time to resolution at this time.
investigating
We are investigating degraded performance and increased latency in the ingestion path for Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5) and Grafana Cloud Traces in prod-us-central-0.
Customers may experience intermittent errors or delays when sending metrics and traces.
We continue to investigate the issue with our cloud provider. We do not have an estimated time to resolution at this time.
investigating
We are investigating degraded performance and increased latency in the ingestion path for Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5) and Grafana Cloud Traces in prod-us-central-0.
Customers may experience intermittent errors or delays when sending metrics and traces. We have also received reports that some customers using Google Managed Prometheus in this region are experiencing issues when querying their GMP instances.
We continue to investigate the issue with our cloud provider. We do not have an estimated time to resolution at this time.
investigating
We are investigating degraded performance and increased latency in the ingestion path for Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5) and Grafana Cloud Traces in prod-us-central-0.
Customers may experience intermittent errors or delays when sending metrics and traces. We have also received reports that some customers using Google Managed Prometheus in this region are experiencing issues when querying their GMP instances.
We continue to investigate the issue with our cloud provider. We do not have an estimated time to resolution at this time.
investigating
We are investigating degraded performance with increased latency in the ingestion path for Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5) and for Grafana Cloud Traces in prod-us-central-0. Customers may experience intermittent errors or delays when sending metrics and traces. We continue to investigate this with our cloud provider. We do not have an estimated time of resolution at this time. Next update by 18:30 UTC
investigating
We continue seeing elevated error rates and latency, and keep working with our cloud provider on this issue.
Next update by 17:30 UTC.
investigating
We are investigating degraded performance with increased latency in the ingestion path for Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5) and for Grafana Cloud Traces in prod-us-central-0. Customers may experience intermittent errors or delays when sending metrics and traces. We are investigating this with our cloud provider. We do not have an estimated time of resolution at this time. Next update by 16:30 UTC.
investigating
We are investigating degraded performance with increased latency in the ingestion path for Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5) and for Grafana Cloud Traces in prod-us-central-0. Customers may experience intermittent errors or delays when sending metrics and traces. We are investigating this with our cloud provider. We do not have an estimated time of resolution at this time. Next update by 15:30 UTC.
investigating
We continue to investigate intermittent elevated error rates and latency affecting Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5), and periodic increased latency affecting Grafana Cloud Traces in prod-us-central-0. Intermittent errors and latency may still occur. We are working with our cloud provider as part of the investigation. We do not have an estimated time of resolution at this time. Next update by 14:30 UTC.
investigating
Update to scope: we have not confirmed any impact to Grafana Cloud Logs, and Logs has been removed from the affected components. We continue to investigate intermittent elevated error rates and latency affecting Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5), and periodic increased latency affecting Grafana Cloud Traces in prod-us-central-0. Error rates have decreased, but intermittent errors and latency may still occur. We are working with our cloud provider as part of the investigation. We do not have an estimated time of resolution at this time. Next update by 14:30 UTC.
investigating
We continue to investigate intermittent elevated error rates and latency affecting Grafana Cloud Metrics and Logs in GCP US Central (prod-us-central-0 and prod-us-central-5), and periodic increased latency affecting Grafana Cloud Traces in prod-us-central-0. Error rates have decreased, but intermittent errors and latency may still occur. We are working with our cloud provider as part of the investigation. We do not have an estimated time of resolution at this time. Next update by 14:30 UTC.
investigating
Beginning around 10:20 UTC, we have been seeing intermittent elevated error rates and latency affecting Grafana Cloud Metrics and Logs in GCP US Central (prod-us-central-0 and prod-us-central-5), and periodic increased latency and occasional errors affecting Grafana Cloud Traces in prod-us-central-0. Customers may see errors or delays when sending metrics, logs and traces. We are actively investigating. Next update by 13:40 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.
February 2026
Grafana Cloud Metrics - Intermittent Write Latency in prod-us-central, prod-us-central-5, and prod-eu-west-0
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are rolling out a mitigation across the environments in these regions, and preemptively where possible to ensure it doesn’t spread elsewhere.
monitoring
We have seen an increase in latency in our cloud providers services, and are rolling out a change to mitigate the issue. We are monitoring.
monitoring
We are continuing to investigate this issue alongside the CSP, and have taken steps to escalate through the appropriate channels. The mitigation in place continues to work as expected, and any notable updates will continue to be shared here for tracking.
monitoring
We are continuing to investigate this issue alongside the CSP. Any notable updates will continue to be shared here for tracking.
monitoring
We've implemented mitigation in place and are continuing to monitoring and investigating this issue.
investigating
We have begun rolling out mitigation steps to reduce write latency in the prod-us-central-0 and prod-us-central-5 regions. While these measures are expected to improve performance, we are continuing to investigate the underlying root cause of the issue. We will provide additional updates as more information becomes available.
investigating
Since February 19, we have been investigating an intermittent issue causing increased write latency in the prod-us-central-0 and prod-us-central-5 regions. The issue does not affect all traffic but may result in delayed write operations for some customers. Our engineering team is actively working to identify the root cause and stabilize performance. We will share additional updates as progress is made.
