- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 13of 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 7m it lasted.
Anything that failed between 2025-03-22 01:40 UTC and 2025-03-22 01:48 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
- investigating
We are currently investigating an issue impacting the performance of Slack and web-based services. Users may experience interruptions in accessing the Web Platform and Rootly Slack commands.
provider
- resolved
The issue affecting Web and Slack performance has been resolved. All services are functioning normally. We appreciate your patience during this incident and apologize for any inconvenience caused.
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-8a3f52d7a7
Is Rootly still down?
No, this incident was resolved 2025-03-22 01:48 UTC. For Rootly's live state, see https://down.guide/rootly.
How long did it last?
7m, from 2025-03-22 01:40 UTC to 2025-03-22 01:48 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.