- Level
- confirmed
- Worst impact
- Degraded
- Components
- Incident Management and Response (IRM)
- Regions
- us, us-central-0
What to do
Check whether you use Grafana IRM Incident Management and Response (IRM) in us, us-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 23m it lasted.
Anything that failed between 2026-08-25 10:39 UTC and 2026-08-25 11:02 UTC may need a replay.Subscribe to Grafana IRM's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=grafana-oncall works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Grafana IRM 4
- investigating
We are investigating an outage affecting Grafana Incident in the US Central region (prod-us-central-0). Customers are unable to create, view, or query Incidents, and requests to the Incident public API are timing out. All customers in this region are affected. Grafana OnCall is not impacted — alert ingestion, alert group creation, and notification delivery are all operating normally.
provider
- monitoring
A fix has been applied and Incident Management in US Central is recovering. The Incident public API is responding normally, and customers can create, view, and query Incidents again. We are continuing to monitor the recovery to confirm the service is fully stable.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- resolved
This incident has been resolved. Incident Management in US Central is operating as normal. Customers can create, view, and query Incidents, and the Incident public API is fully available. Grafana OnCall was not affected at any point during this incident.
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-1b3a0c1406
Is Grafana IRM still down?
No, this incident was resolved 2026-08-25 11:02 UTC. For Grafana IRM's live state, see https://down.guide/grafana-oncall.
How long did it last?
23m, from 2026-08-25 10:39 UTC to 2026-08-25 11:02 UTC, by the times Grafana IRM posted.
What was affected?
Grafana IRM named Incident Management and Response (IRM) in us, us-central-0.
What caused it?
Grafana IRM hasn't published a root cause. If it does, it shows here.
Where does this come from?
Grafana IRM's official status page, https://status.grafana.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.