- Level
- confirmed
- Worst impact
- Major outage
What to do
Check whether your product depends on Rootly. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 76d 2h it lasted.
Anything that failed between 2026-08-27 12:54 UTC and 2026-11-11 15:24 UTC may need a replay.Subscribe to Rootly's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=rootly works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Rootly 1
- investigating
We are investigating errors in creating incident channels due to an upstream Slack outage. Rootly On-Call remains fully operational, including alerting and paging. Incident creation inside the web platform is also unaffected. We are monitoring the situation and will provide updates as Slack restores their sevice.
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-52f3214051
Is Rootly still down?
No, this incident was resolved 2026-11-11 15:24 UTC. For Rootly's live state, see https://down.guide/providers/rootly.
How long did it last?
76d 2h, from 2026-08-27 12:54 UTC to 2026-11-11 15:24 UTC, by the times Rootly posted.
What caused it?
Rootly hasn't published a root cause. If it does, it shows here.
Where does this come from?
Rootly's official status page, https://status.rootly.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.