- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 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 15h 54m it lasted.
Anything that failed between 2025-02-26 22:22 UTC and 2025-02-27 14:16 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 2
- monitoring
We are still noticing a minority of errors failing on Slack's end due to their outage impacting /rootly commands on Slack. Stay up to date with Slack: https://slack-status.com/2025-02/1b757d1d0f444c34.
provider
- resolved
Slack reported this morning issues impacting their app have been resolved. However, historical events are still attempting to get replayed through their system queue. Stay up to date with Slack: https://slack-status.com/2025-02/1b757d1d0f444c34.
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-253cd75a31
Is Rootly still down?
No, this incident was resolved 2025-02-27 14:16 UTC. For Rootly's live state, see https://down.guide/rootly.
How long did it last?
15h 54m, from 2025-02-26 22:22 UTC to 2025-02-27 14:16 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.