Brief disruption to outbound integrations during network maintenance
We will be restarting the network gateways that carry outbound traffic from Sentry in all regions. Each restart drops a portion of in-flight outbound connections, which may briefly delay alert deliveries to integrations and webhooks, fail fetches of source maps and symbols from customer servers, and cause isolated uptime check retries. Ingestion, the web app and the API are not affected.
The latest update from Sentry.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Sentry
We will be restarting the network gateways that carry outbound traffic from Sentry in all regions. Each restart drops a portion of in-flight outbound connections, which may briefly delay alert deliveries to integrations and webhooks, fail fetches of source maps and symbols from customer servers, and cause isolated uptime check retries. Ingestion, the web app and the API are not affected.
Sentry in the last 90 days
Full historyIncidents in 90 days
24
Days with an incident
18
Median duration
1 h 21 min
This incident
Not comparable
Other Sentry incidents
All incidentsSentry·US issues feed throwing intermittent errors
Sentry reports intermittent errors in issues queries on the Dashboard. Sentry identified the problem and deployed a fix. The incident is resolved and lasted 52 minutes.
Sentry·Account emails not being delivered
Sentry account emails did not reach users. The Email and Notification Delivery - Email components had a partial outage. Sentry says the incident is resolved. It lasted from 07:52 UTC to 08:34 UTC on November 11. Emails that failed between 21:37 UTC on November 10 and 08:15 UTC on November 11 are not re-sent. Request a new verification email, invite, or password reset if needed.
Sentry·EU region replay ingestion latency
Sentry reports replay event ingestion latency in the EU region. The affected components are EU Replay Ingestion and EU Ingestion - EU Replay Ingestion. Sentry resolved the issue, and the outage lasted about 48 minutes.
Sentry·Ingestion delays across all data
Sentry reported ingestion delays for all US data. The affected components were US Error, Transaction, Attachment, Profile, Replay, Span, Cron Monitoring, and Custom Metrics ingestion. Sentry resolved the incident after 70 minutes, and latency returned to normal.
Sentry·Delays in spans and transactions processing
Sentry span and transaction ingestion had delays in the US. The affected components were US Transaction Ingestion and US Span Ingestion. Sentry resolved the issue. The incident lasted about 105 minutes. No data was lost.
Follow Sentry
Your coding agent knows when Sentry is down, and tells you when a failure is theirs, not yours. You can also get Sentry 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.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 "sentry" and tell me if Sentry 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.live/feed.xml?providers=sentry/feed subscribe https://outages.live/feed.xml?providers=sentryFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane