- Level
- confirmed
- Worst impact
- Degraded
- Components
- AWS Australia - prod-au-southeast-1, AWS Brazil - prod-sa-east-1, AWS Canada - prod-ca-east-0, AWS Germany - prod-eu-west-2, AWS India - prod-ap-south-1, AWS Ireland - prod-eu-west-6, AWS Japan - prod-ap-northeast-0, AWS Singapore - prod-ap-southeast-1, AWS Sweden - prod-eu-north-0, AWS Switzerland - prod-eu-central-0, AWS UAE - prod-me-central-1, AWS US East (OH) - prod-us-east-0, AWS US West - prod-us-west-0, Azure Netherlands - prod-eu-west-3, Azure US Central - us-central2, Azure US Central - us-central7, GCP Australia - prod-au-southeast-0, GCP Belgium - prod-eu-west-0, GCP Brazil - prod-sa-east-0, GCP India - prod-ap-south-0, GCP Singapore - prod-ap-southeast-0, GCP UK - prod-gb-south-0, GCP US Central - prod-us-central-0, GCP US Central - prod-us-central-5, Federal Cloud - AWS US Gov West
- Regions
- ap-northeast-0, ap-south-0, ap-south-1, ap-southeast-0, ap-southeast-1, apac, au, ca, ca-east-0, eu, eu-central-0, eu-north-0, eu-west-0, eu-west-2, eu-west-3, eu-west-6, in, jp, latam, me, me-central-1, sa-east-0, sa-east-1, us, us-central-0, us-central-5, us-central2, us-central7, us-east-0, us-west-0
- Down Index
- 39of 100
What to do
Check whether you use Grafana Cloud AWS Australia - prod-au-southeast-1, AWS Brazil - prod-sa-east-1, AWS Canada - prod-ca-east-0, AWS Germany - prod-eu-west-2 and 21 more in ap-northeast-0, ap-south-0, ap-south-1, ap-southeast-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 2h 17m it lasted.
Anything that failed between 2026-07-01 19:43 UTC and 2026-07-01 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
- investigating
We are investigating an issue where some customers may see higher Loki query byte usage reported than was actually consumed. This affects usage reporting only; there is no impact to query execution or service availability. The issue began at approximately 13:20 UTC and is ongoing. We expect the issue to be resolved soon and will provide another update as more information becomes available.
provider
- resolved
We’ve implemented a fix and can confirm the issue is fully resolved as of 20:25 UTC. 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-9fefda4d60
Is Grafana Cloud still down?
No, this incident was resolved 2026-07-01 22:00 UTC. For Grafana Cloud's live state, see https://down.guide/grafana-cloud.
How long did it last?
2h 17m, from 2026-07-01 19:43 UTC to 2026-07-01 22:00 UTC, by the times Grafana Cloud posted.
What was affected?
Grafana Cloud named AWS Australia - prod-au-southeast-1, AWS Brazil - prod-sa-east-1, AWS Canada - prod-ca-east-0, AWS Germany - prod-eu-west-2 and 21 more in ap-northeast-0, ap-south-0, ap-south-1, ap-southeast-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.