- Level
- confirmed
- Worst impact
- Degraded
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.Rootly says a fix is out: check your own error rates before you undo any failover.
Watch Rootly's own updates; this page re-reads them every minute.
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 2
- 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 service. You can follow along here: https://slack-status.com/2026-11/b8bb993128ac94f5.
provider
- monitoring
We are seeing errors drop significantly and only a few intermittent issues. We are continuing to monitor and you can continue to follow along Slack's progress here: https://slack-status.com/2026-11/b8bb993128ac94f5. Rootly remains available via Web Platform and On-Call is unaffected.
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-d9a6f3f359
Is Rootly down right now?
Rootly reports degraded (Incident creation on Slack impacted due to upstream Slack incident), open since 2026-11-11 15:03 UTC; it says a fix is out and it is monitoring. Live state for every component: https://down.guide/providers/rootly.
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.