# Incident creation on Slack impacted due to upstream Slack incident

- Provider: [Rootly](https://down.guide/providers/rootly)
- Confidence: Confirmed
- Impact: Major outage
- lasted 76d 2h
- started 2026-08-27 12:54 UTC
- id: DWN-52f3214051
- Official page: https://status.rootly.com/incidents/71d7aa9a-eec3-497f-9ad3-3c12f9fbc557

## Updates from Rootly
### 2026-11-11 15:20 UTC: investigating
We are investigating errors in creating incident channels due to an upstream Slack outage. Rootly On-Call remains fully operational, including alerting and paging. Incident creation inside the web platform is also unaffected.
We are monitoring the situation and will provide updates as Slack restores their sevice.

From the builder: does your app depend on Rootly? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=rootly) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Rootly.

---
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://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-52f3214051), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.