Grafana incident
Elevated Latency and Errors for Grafana Cloud Logs in AWS US East (VA)
Resolved after 2 hours 58 minutes, affecting AWS US East (VA) - prod-us-east-3, on September 30, 2026.
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.
Affected components
Update timeline
- investigating Sep 30, 2026, 12:40 PM UTC
We are investigating elevated latency and a small number of failed requests for Grafana Cloud Logs in AWS US East (VA). Some customers writing logs to this region may see delayed ingestion or occasional write errors. We are actively investigating and will share more as we learn it. Next update by 13:38 UTC.
- investigating Sep 30, 2026, 01:40 PM UTC
We are continuing to investigate this issue.
- identified Sep 30, 2026, 01:43 PM UTC
We have identified a contributing factor to the elevated latency and are rolling out a mitigation to increase write capacity in AWS US East (VA). We continue to investigate a related, longer-running pattern. Next update by 14:40 UTC.
- identified Sep 30, 2026, 02:31 PM UTC
An additional brief recurrence affected a small number of requests after our mitigation was deployed, though impact was smaller than earlier today. We continue to monitor and investigate a related, longer-running pattern. Next update by 15:40 UTC.
- resolved Sep 30, 2026, 03:39 PM UTC
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.
Your product runs on more than Grafana
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services