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

- Provider: [Rootly](https://down.guide/rootly)
- Level: confirmed
- Impact: Major outage
- lasted 4h 36m
- started 2025-02-26 16:06 UTC
- id: DWN-6974f73226
- Official page: https://status.rootly.com/incidents/a8b2adda-401d-440c-b4c1-ada51c8d168b

## Updates from Rootly
### 2025-02-26 16:06 UTC: 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.

### 2025-02-26 16:57 UTC: identified
Latency and failure rates from Slack remain quite high still https://slack-status.com/2025-02/1b757d1d0f444c34.

### 2025-02-26 17:04 UTC: 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.

### 2025-02-26 20:42 UTC: 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.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).