Companies / Rootly / incidents

Rootly: Slack Outage (3rd Party) Impacting Rootly Slack App

Impact: criticalStatus: resolvedStarted Resolved (4.6 h)4 updatesSource: stspg.io (opens in new tab)
Summary

A critical Slack outage disrupted Rootly Slack App slash commands, messaging and button interactions from 2025-02-26 16:06 UTC until resolution at 2025-02-26 20:42 UTC (4 h 35 min). Rootly modified retry logic; /rootly recovered, with scattered channel-creation delays remaining. Rootly On-Call and Web Platform were unaffected.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: Rootly Slack AppSlack App

Timeline of updates

  1. identified

    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.

  2. identified

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

  3. identified

    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.

  4. resolved

    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.

Rewindex changes for this incident

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Rootly profile · Recent Rootly incidents · Markdown · JSON