← Live dashboard

Elevated Errors Ingesting Metrics in AWS US East (VA)

ResolvedmajorOfficial source confirmedSpecific component onlyFirst recorded update Oct 12, 2026, 09:45 AM · Resolved Oct 12, 2026, 04:42 PM

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.

Grafana Cloud live status →

Free for 3 services · Pro adds recovery alertsAdd to Chrome

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Grafana Cloud now? Check the current status

Affected services

AWS US East (VA) - prod-us-east-3

Updates (8)

  1. Oct 12, 2026, 04:42 PM
    Elevated Errors Ingesting Metrics in AWS US East (VA)

    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.

    Grafana Cloud ↗
  2. Oct 12, 2026, 03:01 PM
    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.

    Grafana Cloud ↗
  3. Oct 12, 2026, 02:01 PM
    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.

    Grafana Cloud ↗
  4. Oct 12, 2026, 12:53 PM
    Elevated Errors Ingesting Metrics in AWS US East (VA)

    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.

    Grafana Cloud ↗
  5. Oct 12, 2026, 11:56 AM
    Elevated Errors Ingesting Metrics in AWS US East (VA)

    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.

    Grafana Cloud ↗
  6. Oct 12, 2026, 10:55 AM
    Elevated Errors Ingesting Metrics in AWS US East (VA)

    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.

    Grafana Cloud ↗
  7. Oct 12, 2026, 10:08 AM
    Elevated Errors Ingesting Metrics in AWS US East (VA)

    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.

    Grafana Cloud ↗
  8. Oct 12, 2026, 09:45 AM
    Elevated Errors Ingesting Metrics in AWS US East (VA)

    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.

    Grafana Cloud ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow Grafana Cloud's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.