Rootly incident
Slack Outage (3rd Party) Impacting Rootly Slack App
Rootly experienced a critical incident on February 26, 2025 affecting Slack App, lasting 4h 35m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Feb 26, 2025, 04: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.
- identified Feb 26, 2025, 04:57 PM UTC
Latency and failure rates from Slack remain quite high still https://slack-status.com/2025-02/1b757d1d0f444c34.
- identified Feb 26, 2025, 05: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.
- resolved Feb 26, 2025, 08: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.