- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 22of 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 7h 32m it lasted.
Anything that failed between 2026-04-14 15:51 UTC and 2026-04-14 23:23 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 reports loading issues on our marketing homepage, affecting users in some locations. This is related to an ongoing issue with our hosting provider, Webflow. You can follow their progress here: status.webflow.com/incidents/kdtchw1lvsfv. The Rootly application including on-call is not affected. A workaround is directly visiting https://rootly.com/account. We are monitoring the situation and will provide updates as they become available.
provider
- resolved
Webflow has resolved the issue and our marketing homepage is functioning as expected. Full details: https://status.webflow.com/incidents/kdtchw1lvsfv.
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-b58d79c6f4
Is Rootly still down?
No, this incident was resolved 2026-04-14 23:23 UTC. For Rootly's live state, see https://down.guide/rootly.
How long did it last?
7h 32m, from 2026-04-14 15:51 UTC to 2026-04-14 23:23 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.