outages.live
Live
SentryIncident ·

Ingestion delays across all data

DegradedOfficial update
0

Sentry reports ingestion delays in the US region. The affected components are US Error, Transaction, Attachment, Profile, Replay, Span, Cron Monitoring, and Custom Metrics ingestion. Sentry deployed a fix and monitors the result while it clears the backlog.

State

Monitoring

Started

Ongoing for

58 min

Worst impact

Degraded

Timeline

3 updates
17:3117:4618:0018:1518:29
DegradedUpdate postedTimes in UTC

Monitoring

58 min 100%

Updates

Times in UTC

As posted by Sentry

Monitoring

We are backfilling transaction events ingested received >1 hour ago, and still burning our backlog for uptime events in US. All other event types in our US region are being ingested with normal latency.

Monitoring

We have identified the issue causing ingestion delays in our US region, and have deployed a fix. We are monitoring the fix while we burn our event backlog.

Monitoring

We are monitoring an issue involving increased ingestion latency across all our datasets.

Affected components

16
US Error IngestionUS Transaction IngestionUS Attachment IngestionUS Profile IngestionUS Replay IngestionUS Span IngestionUS Cron MonitoringCustom Metrics (beta)

Sentry in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

26

Days with an incident

19

Median duration

1 h 45 min

This incident

45% 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 1 h 45 min
90 days agoToday

Other Sentry incidents

All incidents

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.

Resolved

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

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