- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 15of 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 22m it lasted.
Anything that failed between 2023-10-30 20:13 UTC and 2023-10-30 20:35 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 4
- investigating
We are noticing our background jobs processing slower than normal. Any workflows queued to run are behind schedule. Our engineering team has identified the issue and is currently deploying a fix.
provider
- investigating
We are continuing to investigate this issue. Our engineering team has a fix currently being deployed.
provider
- investigating
We are continuing to investigate this issue. Our engineering team has a fix currently being deployed.
provider
- resolved
Looks like everything is working as normal, including incident creation in Slack. We had an upstream hiccup caused by Cloudflare.
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-a187f5f91b
Is Rootly still down?
No, this incident was resolved 2023-10-30 20:35 UTC. For Rootly's live state, see https://down.guide/rootly.
How long did it last?
22m, from 2023-10-30 20:13 UTC to 2023-10-30 20:35 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.