- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 20of 100
What to do
Check whether your product depends on Rootly. 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 3h 7m it lasted.
Anything that failed between 2025-11-07 02:32 UTC and 2025-11-07 05:39 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 3
- investigating
We’re currently observing degraded Slack performance due to an upstream issue with Slack. You can follow updates directly from Slack here: https://slack-status.com/2025-11/66f5fbbfdb8d6f73
provider
- identified
It appears Slack has identified the issue and is implementing a fix. We are continuing to monitor here: https://slack-status.com/2025-11/66f5fbbfdb8d6f73.
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-d46123a56a
Is Rootly still down?
No, this incident was resolved 2025-11-07 05:39 UTC. For Rootly's live state, see https://down.guide/rootly.
How long did it last?
3h 7m, from 2025-11-07 02:32 UTC to 2025-11-07 05:39 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.