# Increased rate of disconnections from Sentry

- Provider: [incident.io](https://down.guide/incident-io)
- Level: confirmed
- Impact: Degraded
- lasted 3h 28m
- started 2025-12-22 10:29 UTC
- us
- id: DWN-66050d3219
- Official page: https://status.incident.io/incidents/01KD2SP5NKHRAJJ6Q7D05FN3NK

## Updates from incident.io
### 2025-12-22 10:29 UTC: identified
We have identified an increased rate of Sentry integrations becoming disconnected. Alert ingestion is unaffected. Please don't uninstall our application from Sentry: we are working to restore these connections on our side, and no action is currently required. We will provide an update in 30 minutes.

### 2025-12-22 10:58 UTC: identified
We're currently testing the fix that will allow us to re-connect any disconnected Sentry integrations on behalf of customers, and will have another update on this in 30 minutes.

### 2025-12-22 11:34 UTC: identified
We've verified a fix locally, and we're starting to roll this out in production now.

### 2025-12-22 12:04 UTC: monitoring
We have confirmed that we are able to restore these connections, and we are now in the process of restoring these. When this happens, you'll see that the Sentry integration no longer flags up as requiring reconnection. Once we have finished restoring access, we'll post another update here.

### 2025-12-22 13:57 UTC: resolved
We have managed to re-establish a connection to Sentry for almost all of the affected customers. If Sentry is still showing up as disconnected, you will need to remove the incident.io integration from the Sentry side, and then go through the reinstallation flow by opening incident.io and going to Settings → Integrations → Sentry.
If you do this, please note that Sentry will remove the "Notify incident.io" action from alert rules when you uninstall the integration. If that was the only action in the alert rule, the entire rule is disabled. You will therefore need to verify any alert rules after re-installing.

From the builder: does your app depend on incident.io? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=incident-io) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention incident.io.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-66050d3219), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.