Live  /  Grafana Cloud  /  Incident

Grafana Cloud: Elevated Errors Ingesting Metrics in AWS US East (VA)

Grafana Cloud · grafana.comMajor incidentResolved2026-10-12 16:42 UTC
Public — what happened

Summary

Grafana Cloud reported a major problem with accepting incoming metrics data for Grafana Cloud Metrics customers in its AWS US East (Virginia) region, prod-us-east-3, beginning at 09:45 UTC on October 12, 2026. The company said customers could see metric writes fail or arrive late, and that metrics sent by Frontend Observability and Synthetic Monitoring might also be affected. Around 11:56 UTC Grafana Cloud said it had found the cause, without describing it, and by 14:01 UTC it said it had isolated infrastructure it suspected was contributing while it checked recovery. The incident was marked resolved at 16:42 UTC the same day.

Affected

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

As listed on Grafana Cloud’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Grafana Cloud against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Grafana Cloud: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Grafana Cloud report →

More from Grafana Cloud

Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.

The full archive is on the Grafana Cloud status & history page.

Related: Grafana Cloud status & history. SquidGrid is not affiliated with Grafana Cloud.