- Level
- confirmed
- Worst impact
- Degraded
- Components
- GCP US Central - prod-us-central-0: Ingestion
- Regions
- us, us-central-0
- Down Index
- 26of 100
What to do
Check whether you use Grafana Cloud GCP US Central - prod-us-central-0: Ingestion 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 1h 32m it lasted.
Anything that failed between 2026-07-14 20:28 UTC and 2026-07-14 22:00 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 2
- monitoring
From 19:24 until 19:40 UTC, backend performance degradation impacted ingestion. We are currently monitoring.
provider
- resolved
This incident has been resolved. Thank you for your patience.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-dad88f92d9
Is Grafana Cloud still down?
No, this incident was resolved 2026-07-14 22:00 UTC. For Grafana Cloud's live state, see https://down.guide/grafana-cloud.
How long did it last?
1h 32m, from 2026-07-14 20:28 UTC to 2026-07-14 22:00 UTC, by the times Grafana Cloud posted.
What was affected?
Grafana Cloud named GCP US Central - prod-us-central-0: Ingestion in us, us-central-0.
What caused it?
Grafana Cloud hasn't published a root cause. If it does, it shows here.
Where does this come from?
Grafana Cloud's official status page, https://status.grafana.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.