Latency and failures when interacting with our app in Slack

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 1h 38m it lasted.

  Anything that failed between 2025-08-21 18:09 UTC and 2025-08-21 19:47 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 3

1. investigatingAug 21, 2025, 6:09 PM UTC

   We are currently investigating increased reports of latency and failures when interacting with our app in Slack. Our team is actively looking into the issue and will provide updates as more information becomes available

   provider

2. identifiedAug 21, 2025, 6:42 PM UTC

   We’ve investigated and found the issue is related to a broader ongoing incident at one of our infrastructure providers. You can follow their status updates here: https://www.cloudflarestatus.com/incidents/d9n3g1vnxdd2 While our Slack app is the most visibly impacted, we are also identifying potential effects on other services such as our web interface and APIs. Our on-call product remains operational. We’ll continue to share updates as we make progress.

   provider

3. resolvedAug 21, 2025, 7:47 PM UTC

   This incident has been fully resolved and all services are functioning normally. There was no impact to on-call paging at any time. We’ll continue to monitor, but no further action is required.

   provider

Corrections

None so far.

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