Disruption to Slack incident channels and messages
incident.io reports a disruption to Slack incident channels and messages. Slack incident channel creation fails, and some Slack actions such as posting messages and renaming channels also fail. incident.io is monitoring the situation and reports that channel creation and message delivery appear to have recovered.
State
Monitoring
Started
Ongoing for
2 h 35 min
Worst impact
Partial outage
Timeline
5 updatesInvestigating
29 min 18%
Monitoring
2 h 7 min 82%
Updates
Times in UTCAs posted by incident.io
We're no longer seeing errors creating Slack channels or delivering messages. We are continuing to monitor the situation to ensure this recovery holds. You can follow Slack’s updates on [their status page](https://slack-status.com/2026-11/b8bb993128ac94f5).
Slack incident channel creation and message delivery appear to have recovered. We’re continuing to monitor the situation to ensure this recovery holds. You can follow Slack’s updates on [their status page](https://slack-status.com/2026-11/b8bb993128ac94f5).
Slack incident channel creation and message delivery both appear to be recovering. We’re continuing to monitor the situation. You can follow Slack's updates on [their status page](https://slack-status.com/2026-11/b8bb993128ac94f5).
A Slack outage is causing failures when creating incident channels and posting messages in Slack. We’ve reached out to Slack for assistance. You can follow their updates on [Slack’s status page](https://slack-status.com/2026-11/b8bb993128ac94f5). Incidents remain available in the incident.io dashboard.
We’re investigating an issue where Slack incident channels are not being created when new incidents are declared. Some Slack actions (such as posting messages or renaming channels) are also failing. Incidents remain available in the incident.io dashboard while we work to resolve this.
incident.io in the last 90 days
Full historyIncidents in 90 days
4
Days with an incident
4
Median duration
1 h 49 min
This incident
1.4× the median
Other incident.io incidents
All incidentsincident.io·Sentry integration degraded
incident.io reports that its Sentry integration was degraded. This affects Sentry alerts, comments on linked issues, and automatic issue resolution. incident.io resolved the incident on 2 November 2026 after 1 hour and 57 minutes.
incident.io·Login errors for subset of Slack Enterprise Grid customers
This incident has been resolved. Login via Slack is operating normally again, and no further action is required.
incident.io·Increased latency in Microsoft Teams
Latency has now returned to normal. Between 13:00 and 15:08 UTC there were periods of increased latency from some Microsoft APIs. Messages in Microsoft Teams were delivered with increased latency. Our dashboard and mobile app were not affected.
Follow incident.io
Your coding agent knows when incident.io is down, and tells you when a failure is theirs, not yours. You can also get incident.io incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "incidentio" and tell me if incident.io has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=incidentio/feed subscribe https://outages.live/feed.xml?providers=incidentioFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane