- Level
- confirmed
- Worst impact
- Degraded
- Regions
- ca
What to do
Check whether you use Grafana Cloud in ca. 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-11-02 12:14 UTC and 2026-11-02 08: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 1
- resolved
Between approximately 08:09 and 09:10 UTC on 2 November (about 1 hour 11 minutes), a subset of Synthetic Monitoring checks running from the Montreal, North Virginia, and North California public probe locations experienced missing metrics, which may have appeared as gaps in dashboards. Specifically this affected: Checks with the Montreal Public Probe from 08:09-09:00 UTC Checks with the North Virginia Public Probe from 08:22-09:06 UTC Checks with the North California Public Probe from 08:43-09:20 UTC This has been fully resolved and all services are operating normally.
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-5cef5dc4a2
Is Grafana Cloud still down?
No, this incident was resolved 2026-11-02 08:00 UTC. For Grafana Cloud's live state, see https://down.guide/grafana-cloud.
How long did it last?
0m, from 2026-11-02 12:14 UTC to 2026-11-02 08:00 UTC, by the times Grafana Cloud posted.
What was affected?
Grafana Cloud named in ca.
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.