Elevated Errors Ingesting Metrics in AWS US East (VA)
Oct 12, 09:45 UTCOct 12, 16:42 UTC
Duration
6h 57m
Impact
Major
Root cause
Not disclosed
Grafana Labs, 90 days
66 incidents
Affected
AWS US East (VA) - prod-us-east-3Metrics - AWS US East (VA) - prod-us-east-3
Final update
From 09:45 UTC on 2026-10-12, customers in AWS US East (VA) experienced failed or delayed metric writes to Grafana Cloud Metrics, which may have also affected Frontend Observability and Synthetic Monitoring data in that region. This has been fully resolved and all services are operating normally again.
Timeline
- Resolved · Oct 12, 16:42 UTC
From 09:45 UTC on 2026-10-12, customers in AWS US East (VA) experienced failed or delayed metric writes to Grafana Cloud Metrics, which may have also affected Frontend Observability and Synthetic Monitoring data in that region. This has been fully resolved and all services are operating normally again.
- Identified · Oct 12, 15:01 UTC
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 · Oct 12, 14:01 UTC
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 · Oct 12, 12:53 UTC
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 · Oct 12, 11:56 UTC
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 · Oct 12, 10:55 UTC
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 · Oct 12, 10:08 UTC
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 · Oct 12, 09:45 UTC
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.
More from Grafana Labs
Full historyElevated Errors Ingesting Metrics in AWS US East (OH) - prod-us-east-0lasted 0mIssues with Private Data Source Connect (PDC) in AWS US East (OH)lasted 0mDegraded Performance with Increased Latency for Grafana Cloud Metrics and Traces in GCP US Centrallasted 11h 33mGrafana Cloud k6 – Brief metrics unavailabilitylasted 0mIRM Unable to Send SMS to Thailand, Bangladesh, and Austrian Numbersstill openDegraded data source querieslasted 14m