Delayed Paging

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 2h 54m it lasted.

  Anything that failed between 2025-10-20 18:48 UTC and 2025-10-20 21:42 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 6

1. investigatingOct 20, 2025, 6:48 PM UTC

   We are currently investigating delays in paging notifications due to an issue with one of our upstream providers. As a result, incident alerts may be delayed in reaching on-call responders. We appreciate your patience and will provide updates as more information becomes available.

   provider

2. identifiedOct 20, 2025, 7:08 PM UTC

   Our engineers are still working to mitigate the issue. Paging continues to be delayed.

   provider

3. identifiedOct 20, 2025, 7:48 PM UTC

   Our engineers are still working to mitigate the issue. Paging continues to be delayed but alert ingestion remains unaffected.

   provider

4. identifiedOct 20, 2025, 8:22 PM UTC

   Our engineering team continues to actively work on the issue. Alerts are being ingested but sent out delayed.

   provider

5. monitoringOct 20, 2025, 8:34 PM UTC

   Our system has recovered and new notifications are being sent without delay. Some previously delayed pages are and other on-call notifications may arrive later than expected.

   provider

6. resolvedOct 20, 2025, 9:42 PM UTC

   This issue is now fully resolved as our upstream providers have recovered.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.