Elevated write latency for AWS Metrics Streaming integration in us-east-3 region.

What to do

• Check whether you use Grafana Cloud in us, us-east-3. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-04-29 12:57 UTC and 2026-04-29 10:30 UTC may need a replay.

• Subscribe to Grafana Cloud's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=grafana-cloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Grafana Cloud 1

1. resolvedApr 29, 2026, 10:30 AM UTC

   We were facing an incident with AWS Metrics Streaming integration in us-east-3 region manifesting in elevated ingestion latency. The incident started at around 10:45 UTC and was resolved at around 12:30 UTC. Some tenants could see an elevated write latency, but all requests were being processed and we don't expect any data loss during the time of the incident. The incident is now resolved, but we keep monitoring the system's health.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.