outages.live
Live

incident.io

incident.io is operational

Checked 3 min ago Operational

History

90 days agoToday

Incidents in 90 days

2

Days with an incident

2

Median duration

1 h 31 min

Longest incident

1 h 49 min

Components

25
Alert ingestion, processing and paging Operational
90 days agoNo incidentsToday
Push notifications Operational
90 days agoNo incidentsToday
SMS Operational
90 days agoNo incidentsToday
Phone Operational
90 days agoNo incidentsToday
Slack Operational
90 days agoNo incidentsToday
Email Operational
90 days agoNo incidentsToday
Status pages Operational
90 days agoNo incidentsToday
Response Operational
90 days agoNo incidentsToday
Investigations Operational
90 days agoNo incidentsToday
Agent Operational
90 days agoNo incidentsToday
API Operational
90 days agoNo incidentsToday
Dashboard Operational
90 days agoNo incidentsToday
Desktop app Operational
90 days agoNo incidentsToday
Insights Operational
90 days agoNo incidentsToday
MCP Operational
90 days agoNo incidentsToday
Microsoft Teams app Operational
90 days agoNo incidentsToday
Mobile app Operational
90 days agoNo incidentsToday
Slack app Operational
90 days agoNo incidentsToday
Asana Operational
90 days agoNo incidentsToday
Atlassian Statuspage Operational
90 days agoNo incidentsToday
Azure DevOps Operational
90 days agoNo incidentsToday
ClickUp Operational
90 days agoNo incidentsToday
Confluence Operational
90 days agoNo incidentsToday
Cortex Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 2, 2026

Duration1 h 14 min22:33 to 23:47Login errors for subset of Slack Enterprise Grid customersDegraded

This incident has been resolved. Login via Slack is operating normally again, and no further action is required.

Aug 20, 2026

Duration1 h 49 min14:42 to 16:31Increased latency in Microsoft TeamsDegraded

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.

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 "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.

RSS
https://outages.live/feed.xml?providers=incidentio
Slack
/feed subscribe https://outages.live/feed.xml?providers=incidentio

Go from tracking outages to fixing production issues with Polylane.

Try Polylane