Network Degredation in prod-us-central-0

What to do

• Check whether you use Grafana Cloud in us, us-central-0. 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-07-10 21:31 UTC and 2026-07-10 21:31 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. resolvedJul 10, 2026, 9:31 PM UTC

   From approximately 20:24 UTC - 20:47 UTC a network issue in prod-us-central-0 isolated part of our infrastructure in one availability zone, temporarily cutting off connectivity to a subset of backend services. This caused elevated query latency and some delayed metric evaluations, along with related write-path errors in a logging subsystem. All systems recovered automatically once network connectivity was restored. Impacted customers may have had queries or rule evaluations fail during the incident, but ingestion was not impacted.

   provider

Corrections

None so far.

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