Slack
Slack is operational
Checked 2 min ago Operational
History
90 days agoToday
Incidents in 90 days
0
Days with an incident
0
Median duration
No data
Longest incident
No data
Components
11Login/SSO Operational
90 days agoNo incidentsToday
Messaging Operational
90 days agoNo incidentsToday
Notifications Operational
90 days agoNo incidentsToday
Search Operational
90 days agoNo incidentsToday
Workspace/Org Administration Operational
90 days agoNo incidentsToday
Canvases Operational
90 days agoNo incidentsToday
Connectivity Operational
90 days agoNo incidentsToday
Files Operational
90 days agoNo incidentsToday
Huddles Operational
90 days agoNo incidentsToday
Apps/Integrations/APIs Operational
90 days agoNo incidentsToday
Workflows Operational
90 days agoNo incidentsToday
No incident in the last 90 days.
Follow Slack
Your coding agent knows when Slack is down, and tells you when a failure is theirs, not yours. You can also get Slack incidents in a feed reader or in Slack.
Prompt
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 "slack" and tell me if Slack 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.
RSS
https://outages.live/feed.xml?providers=slackSlack
/feed subscribe https://outages.live/feed.xml?providers=slackGo from tracking outages to fixing production issues with Polylane.
Try Polylane