- Level
- confirmed
- Worst impact
- Partial outage
- Components
- AWS Australia - prod-au-southeast-1: Alertmanager and Rules Configuration API, AWS Australia - prod-au-southeast-1: Alertmanager, AWS Brazil - prod-sa-east-1: Alertmanager and Rules Configuration API, AWS Brazil - prod-sa-east-1: Alertmanager, AWS Canada - prod-ca-east-0: Alertmanager and Rules Configuration API, AWS Canada - prod-ca-east-0: Alertmanager, AWS Germany - prod-eu-west-2: Alertmanager and Rules Configuration API, AWS Germany - prod-eu-west-2: Alertmanager, AWS UAE - prod-me-central-1: Alertmanager and Rules Configuration API, AWS UAE - prod-me-central-1: Alertmanager, AWS India - prod-ap-south-1: Alertmanager and Rules Configuration API, AWS Japan - prod-ap-northeast-0: Alertmanager and Rules Configuration API, AWS Singapore - prod-ap-southeast-1: Alertmanager and Rules Configuration API, AWS Singapore - prod-ap-southeast-1: Alertmanager, AWS Sweden - prod-eu-north-0: Alertmanager and Rules Configuration API, AWS Sweden - prod-eu-north-0: Alertmanager, AWS US East (OH) - prod-us-east-0: Alertmanager and Rules Configuration API, AWS US East (OH) - prod-us-east-0: Alertmanager, AWS US West - prod-us-west-0: Alertmanager and Rules Configuration API, AWS US West - prod-us-west-0: Alertmanager, AWS Ireland - prod-eu-west-6, AWS Switzerland - prod-eu-central-0, Azure Netherlands - prod-eu-west-3: Alertmanager and Rules Configuration API, Azure Netherlands - prod-eu-west-3: Alertmanager, Azure US Central - us-central2: Alertmanager and Rules Configuration API, Azure US Central - us-central2: Alertmanager, GCP Australia - prod-au-southeast-0: Alertmanager and Rules Configuration API, GCP Australia - prod-au-southeast-0: Alertmanager, GCP Belgium - prod-eu-west-0: Alertmanager and Rules Configuration API, GCP Belgium - prod-eu-west-0: Alertmanager, GCP Brazil - prod-sa-east-0: Alertmanager and Rules Configuration API, GCP Brazil - prod-sa-east-0: Alertmanager, GCP India - prod-ap-south-0: Alertmanager and Rules Configuration API, GCP India - prod-ap-south-0: Alertmanager, GCP Singapore - prod-ap-southeast-0: Alertmanager and Rules Configuration API, GCP Singapore - prod-ap-southeast-0: Alertmanager, GCP UK - prod-gb-south-0: Alertmanager and Rules Configuration API, GCP UK - prod-gb-south-0: Alertmanager, GCP US Central - prod-us-central-0: Alertmanager and Rules Configuration API, GCP US Central - prod-us-central-0: Alertmanager
- 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-central2, us-east-0, us-west-0
- Down Index
- 53of 100
What to do
Check whether you use Grafana Cloud AWS Australia - prod-au-southeast-1: Alertmanager and Rules Configuration API, AWS Australia - prod-au-southeast-1: Alertmanager, AWS Brazil - prod-sa-east-1: Alertmanager and Rules Configuration API, AWS Brazil - prod-sa-east-1: Alertmanager and 36 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 14h it lasted.
Anything that failed between 2026-06-09 23:11 UTC and 2026-06-10 13:11 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 3
- investigating
We are currently investigating an issue affecting data source-managed alerting management functionality in Grafana Cloud. Customers may experience problems viewing, creating, updating, or managing alerts through Grafana when using data source-managed alerting. This issue is limited to alert management functionality within Grafana. Alert evaluation and backend alerting services continue to operate normally. Direct alerting APIs for Mimir and Loki remain fully operational and are unaffected. Grafana-managed alerting is not impacted. We identified this issue at approximately 20:45 UTC and are actively working on a resolution. We will provide additional updates as more information becomes available. Workaround: Customers can continue to use the direct Mimir and Loki alerting APIs while we work to restore normal functionality.
provider
- monitoring
Our team has implemented a fix and we are currently monitoring the results of this.
provider
- resolved
We continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.
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-cf2ff5fca0
Is Grafana Cloud still down?
No, this incident was resolved 2026-06-10 13:11 UTC. For Grafana Cloud's live state, see https://down.guide/grafana-cloud.
How long did it last?
14h, from 2026-06-09 23:11 UTC to 2026-06-10 13:11 UTC, by the times Grafana Cloud posted.
What was affected?
Grafana Cloud named AWS Australia - prod-au-southeast-1: Alertmanager and Rules Configuration API, AWS Australia - prod-au-southeast-1: Alertmanager, AWS Brazil - prod-sa-east-1: Alertmanager and Rules Configuration API, AWS Brazil - prod-sa-east-1: Alertmanager and 36 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.