Slack Outage (3rd Party) Impacting Rootly Slack App

What to do

• Check whether your product depends on Rootly. Check your stack

  Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 4h 36m it lasted.

  Anything that failed between 2025-02-26 16:06 UTC and 2025-02-26 20: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 4

1. identifiedFeb 26, 2025, 4:06 PM UTC

   Slack is running into an incident that is impacting /slash commands (e.g. /rootly new) and messaging capabilities https://slack-status.com/2025-02/1b757d1d0f444c34. This means button interactions and messages are delayed or will fail completely. Some users have also reported being unable to load Slack completely. Rootly On-Call and Web Platform remain unaffected.

   provider

2. identifiedFeb 26, 2025, 4:57 PM UTC

   Latency and failure rates from Slack remain quite high still https://slack-status.com/2025-02/1b757d1d0f444c34.

   provider

3. identifiedFeb 26, 2025, 5:04 PM UTC

   Our engineering team is continuing to monitor closely. We've pushed a few changes to modify our retry logic despite Slack API reporting an outage. We are continuing to look for alternative methods. Stay up to date with Slack: https://slack-status.com/2025-02/1b757d1d0f444c34.

   provider

4. resolvedFeb 26, 2025, 8:42 PM UTC

   Error rates have come down significantly. Scattered delays when creating channels. The /rootly command is now working as intended. Stay up to date with Slack: https://slack-status.com/2025-02/1b757d1d0f444c34.

   provider

Corrections

None so far.

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