outages.live
Live
incident.ioIncident · 2026-11-02 15:39 UTC

Sentry integration degraded

DegradedOfficial update
0

The Sentry integration on incident.io has degraded performance. Sentry has an API outage. Sentry alerts still arrive, but actions such as comments on linked issues or automatic resolution may fail or be delayed. incident.io is monitoring the incident.

State

Monitoring

Started

2 h ago

2026-11-02 15:39 UTC

Ongoing for

1 h 30 min

Worst impact

Degraded

Timeline

2 updates
15:3916:0116:2416:4617:09
DegradedUpdate postedTimes in UTC

Identified

39 min 44%

Monitoring

51 min 56%

Updates

Times in UTC

As posted by incident.io

Monitoring2026-11-02 16:18 UTC

Sentry is experiencing an outage affecting their API. Alerts from Sentry are still being received. Other actions we take in Sentry, such as adding comments to linked issues or automatically resolving them, may fail or be delayed until Sentry recovers. You can follow Sentry's incident on their [status page](https://status.sentry.io/incidents/35sw8wr49l3p).

Identified2026-11-02 15:39 UTC

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

incident.io in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

3

Days with an incident

3

Median duration

1 h 31 min

This incident

About the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

1 h 49 min
median 1 h 31 min
90 days agoToday

Other incident.io incidents

All incidents

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.

Resolvedresolved 31 d ago

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.

Resolvedresolved 74 d ago

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane