Changes / Rootly / Slack Outage (3rd Party) Impacting Rootly Slack App
Rootly: Critical incident: Slack Outage (3rd Party) Impacting Rootly Slack App
Summary
Summary pending. The diff below shows exactly what changed.
What changed
Before: not present
After: Slack Outage (3rd Party) Impacting Rootly Slack App
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2025-02-26 16:06 UTC
Before: not present
After: 2025-02-26 20:42 UTC
Before: not present
After: Rootly Slack App, Slack App
Before: not present
After: 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.
Before: not present
After: Latency and failure rates from Slack remain quite high still https://slack-status.com/2025-02/1b757d1d0f444c34.
Before: not present
After: 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.
Before: not present
After: 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.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Slack Outage (3rd Party) Impacting Rootly Slack App (this change) | Major incident |