Live

Event latency in our EU region

0

Sentry reports latency on error, transaction, and span events in the EU region. This affects EU Error Ingestion, EU Transaction Ingestion, and EU Span Ingestion. Sentry reports that the incident is resolved and that it lasted 36 minutes.

State

Resolved

Started

Lasted

36 min

Worst impact

Degraded

Timeline

3 updates
22:0022:0922:1822:2722:35
DegradedUpdate postedTimes in UTC

Investigating

27 min 76%

Monitoring

9 min 24%

Updates

Times in UTC

As posted by Sentry

Resolved

We have resolved the issue causing ingestion latency for spans, transactions and errors in our EU region.

Monitoring

We have applied a mitigation and are monitoring the latency on error, transaction, and span events in our EU region.

Investigating

We are investigating an issue causing latency on error, transaction, and span events in our EU region.

Affected components

6
EU Error IngestionEU Transaction IngestionEU Span IngestionEU Ingestion - EU Error IngestionEU Ingestion - EU Transaction IngestionEU Ingestion - EU Span Ingestion

Sentry in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

24

Days with an incident

18

Median duration

1 h 21 min

This incident

56% 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 21 min
90 days agoToday

Other Sentry incidents

All incidents

Sentry·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.

Resolved

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.

Resolved

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.

Resolved

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.

Resolved

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

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