- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Incident Management and Response (IRM)
- Down Index
- 51of 100
What to do
Check whether you use Grafana IRM Incident Management and Response (IRM). 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 4h 46m it lasted.
Anything that failed between 2026-07-24 09:17 UTC and 2026-07-24 14:03 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 a possible error creating Slack integrations. Will update the status soon.
provider
- identified
We have identified the root cause of the problem, and we are working on a fix
provider
- identified
We have verified the fix, and we are starting to roll it out
provider
- resolved
This incident has been 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-3ec5cded6c
Is Grafana IRM still down?
No, this incident was resolved 2026-07-24 14:03 UTC. For Grafana IRM's live state, see https://down.guide/grafana-oncall.
How long did it last?
4h 46m, from 2026-07-24 09:17 UTC to 2026-07-24 14:03 UTC, by the times Grafana IRM posted.
What was affected?
Grafana IRM named Incident Management and Response (IRM).
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.