outages.live
Live
SentryMaintenance ·

Database maintenance in the US region

MaintenanceOfficial update

We will be performing a routine database upgrade in US at this time. No interruptions are 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 performing a routine database upgrade in US at this time. No interruptions are expected

Affected components

6
US Transaction IngestionUS Span IngestionUS Cron MonitoringUS Ingestion - US Transaction IngestionUS Ingestion - US Span IngestionUS Ingestion - US Cron Monitoring

Sentry in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

23

Days with an incident

17

Median duration

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

Other Sentry incidents

All incidents

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

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

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