Grafana Cloud: Elevated Latency and Errors for Grafana Cloud Logs in AWS US East (VA)

Grafana Cloud · grafana.comImpact: minorResolved2026-09-30 15:39 UTC

Public — what happened

Summary

Between 12:09 and 15:39 UTC on September 30, Grafana Cloud Logs in AWS US East (VA) experienced intermittent elevated latency and a small number of failed requests. Impact has returned to normal levels and all services are operating as expected. Thank you for your patience.

Timeline

Started — 2026-09-30 12:40 UTC
Last update — 2026-09-30 15:39 UTC
Resolved — 2026-09-30 15:39 UTC

Source of record: provider status page. Mirrored as reported; times in UTC.

With SquidGrid — where it starts on the route

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 →

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