- Level
- confirmed
- Worst impact
- Operational
- Grafana Cloud says
- 2026-11-10 07:05 to 07:08 UTC (3m), and 2026-11-10 07:25 to 07:45 UTC (20m)
- Components
- AWS Switzerland - prod-eu-central-0
- Regions
- eu, eu-central-0
What to do
Check whether you use Grafana Cloud AWS Switzerland - prod-eu-central-0 in eu, eu-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 17m it lasted.
Anything that failed between 2026-11-10 08:03 UTC and 2026-11-10 08:20 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
Cloud Logs writes have experienced elevated latency and error rates in prod-eu-central-0 from 07:05 UTC to 07:08 UTC, and 07:25 UTC to 07:45 UTC. The latency has been mitigated and we are currently monitoring.
provider
- resolved
We're observing a continued period of recovery and will mark this as 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-19d1b42152
Is Grafana Cloud still down?
No, this incident was resolved 2026-11-10 08:20 UTC. For Grafana Cloud's live state, see https://down.guide/grafana-cloud.
How long did it last?
17m, from 2026-11-10 08:03 UTC to 2026-11-10 08:20 UTC, by the times Grafana Cloud posted.
What was affected?
Grafana Cloud named AWS Switzerland - prod-eu-central-0 in eu, eu-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.