Sentry integration degraded
The Sentry integration at incident.io has increased error rates and latency. Incident.io has identified the problem. The incident started at 15:39 UTC and is not resolved.
State
Identified
Started
1 h ago
2026-11-02 15:39 UTC
Ongoing for
1 h 6 min
Worst impact
Degraded
Timeline
1 updateIdentified
1 h 6 min 100%
Updates
Times in UTCAs posted by incident.io
We have identified increased error rates and latency with our Sentry integration. We are currently investigating how this is impacting our platform and we will update with more information shortly as we learn more. Sentry's incident can be tracked on their status page [here](https://status.sentry.io/incidents/35sw8wr49l3p).
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.cc/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.cc/feed.xml?providers=incidentio/feed subscribe https://outages.cc/feed.xml?providers=incidentioFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane