outages.live
Live
SentryMaintenance ·

Database maintenance in the EU region

MaintenanceOfficial update

We will be doing routine database upgrades in EU during this window. No interruption is expected

The latest update from Sentry.

State

Scheduled

Starts

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by Sentry

Scheduled

We will be doing routine database upgrades in EU during this window. No interruption is expected

Affected components

4
EU Transaction IngestionEU Span IngestionEU Ingestion - EU Transaction IngestionEU Ingestion - EU Span Ingestion

Sentry in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

26

Days with an incident

18

Median duration

1 h 58 min

This incident

Not comparable

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

6 h 18 min
median 1 h 58 min
90 days agoToday

Other Sentry incidents

All incidents

Sentry·Delays in spans and transactions processing

Sentry reports delays in span and transaction ingestion in the US region. The affected components are US Transaction Ingestion and US Span Ingestion. Sentry resolved the incident after 1 hour and 45 minutes.

Resolved

Sentry·Sentry.io dashboard and API is down

The Sentry dashboard and API did not work for customers in the US and EU regions. Sentry reports that the issue is resolved. The outage lasted 93 minutes.

Resolved

Sentry·Sentry dashboard is down

Sentry dashboard and API did not work for customers in the US and EU regions. Sentry reports that the incident is resolved. The outage 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.cc/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.cc/feed.xml?providers=sentry
Slack
/feed subscribe https://outages.cc/feed.xml?providers=sentry

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane