outages.live
Live
SentryIncident ·

Delays in spans and transactions processing

Partial outageOfficial update
0

Sentry reports delays in span and transaction processing in the US Transaction Ingestion and US Span Ingestion components. Sentry identified the issue and is rolling out a fix. No data has been lost.

State

Identified

Started

Ongoing for

1 h 30 min

Worst impact

Partial outage

Timeline

2 updates
15:4016:0316:2516:4817:10
Partial outageUpdate postedTimes in UTC

Investigating

14 min 15%

Identified

1 h 16 min 85%

Updates

Times in UTC

As posted by Sentry

Identified

We have identified the issue. We are working to roll out a fix.

Investigating

We are investigating an incident affecting ingestion of spans and transactions. No data has been lost.

Affected components

4
US Transaction IngestionUS Span IngestionUS Ingestion - US Transaction IngestionUS Ingestion - US Span Ingestion

Sentry in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

26

Days with an incident

19

Median duration

2 h 12 min

This incident

32% shorter than the median

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

6 h 18 min
median 2 h 12 min
90 days agoToday

Other Sentry incidents

All incidents

Sentry·Sentry.io dashboard and API is down

Sentry reported that the Dashboard and API did not work for US and EU customers. Sentry later reported that the issue was mitigated and the components were operational. Sentry reported that the issue is resolved. It lasted about 93 minutes.

Resolved

Sentry·Sentry dashboard is down

Sentry dashboard and API had a major outage. The problem affected both US and EU customers. Sentry reported the incident as resolved and it lasted 4 hours and 21 minutes.

Resolved

Sentry·Increased latency processing integration webhooks

We are working on mitigating an incident that affects external integrations such as GitHub, Slack, and Autofix PRs. No data is being lost.

Resolved

Sentry·Sentry.io not loading in US region

Native events ingestion has caught up, everything should be operational now

Resolved

Sentry·Sentry.io not loading

We have a mitigation in place that should prevent this from occurring again in the short term while we continue to work on a proper fix. We are going to close the Statuspage incident for now, but will reopen it if things become unstable again.

Resolved

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.

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

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane