- Level
- confirmed
- Worst impact
- Degraded
- Components
- AWS Germany - prod-eu-west-2: Ingestion
- Regions
- eu, eu-west-2
- Down Index
- 27of 100
What to do
Check whether you use Grafana Cloud AWS Germany - prod-eu-west-2: Ingestion in eu, eu-west-2. 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 2h 23m it lasted.
Anything that failed between 2026-10-15 14:35 UTC and 2026-10-15 16:58 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 4
- identified
We observed some spikes in latency starting at approximately 12:50 UTC. We are working on a resolution. Next update by 15:30 UTC
provider
- identified
We are continuing to work on a fix for this issue. Next update by 16:30 UTC
provider
- identified
Things are starting to stabilize as we continue to work on a mitigation.
provider
- resolved
This incident has been resolved.
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-ee9ba21239
Is Grafana Cloud still down?
No, this incident was resolved 2026-10-15 16:58 UTC. For Grafana Cloud's live state, see https://down.guide/grafana-cloud.
How long did it last?
2h 23m, from 2026-10-15 14:35 UTC to 2026-10-15 16:58 UTC, by the times Grafana Cloud posted.
What was affected?
Grafana Cloud named AWS Germany - prod-eu-west-2: Ingestion in eu, eu-west-2.
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.