outages.live
Live
SentryMaintenance · 2026-11-03 21:00 UTC

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

in 19 h

2026-11-03 21:00 UTC

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by Sentry

Scheduled2026-11-03 00:24 UTC

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

Affected components

10
EU Transaction IngestionEU Replay IngestionEU Span IngestionEU Cron MonitoringEU Size Analysis IngestionEU Ingestion - EU Transaction IngestionEU Ingestion - EU Replay 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

2 h 17 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 2 h 17 min
90 days agoToday

Other Sentry incidents

All incidents

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.

Resolvedresolved 6 h ago

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.

Resolvedresolved 12 d ago

Sentry·Sentry.io not loading in US region

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

Resolvedresolved 13 d ago

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.

Resolvedresolved 13 d ago

Sentry·Sentry is down

Backlogs have been processed and we are back to normal.

Resolvedresolved 14 d ago

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