Sentry reported "Sentry API timeouts (US)" on its status page at 2026-08-12 12:58 UTC.

Sentry lists these components: US Ingestion - US Error Ingestion.

When did the incident start and end?

It started at 2026-08-12 12:58 UTC and ended at 2026-08-12 14:24 UTC. It lasted 1 h 26 min.

How do I get alerts for Sentry?

Subscribe to the Sentry live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Sentry. outages.live reads it every few minutes and keeps every update.

SentryIncident · 2026-08-12 12:58 UTC

Sentry API timeouts (US)

ResolvedOfficial update

API performance has returned to expected levels.

The latest update from Sentry.

State

Resolved

Started

81 d ago

2026-08-12 12:58 UTC

Lasted

1 h 26 min

until 2026-08-12 14:24 UTC

Worst impact

Degraded

Timeline

3 updates

12:5813:2013:4114:0314:24

DegradedUpdate postedTimes in UTC

Investigating

15 min 18%

Monitoring

1 h 11 min 82%

Updates

Times in UTC

As posted by Sentry

Resolved2026-08-12 14:24 UTC

API performance has returned to expected levels.

Monitoring2026-08-12 13:14 UTC

API performance has returned to expected levels. We are continuing to monitor.

Investigating2026-08-12 12:58 UTC

We are currently investigating reports of API timeouts for the Sentry API in our US region.

Affected components

US Ingestion - US Error Ingestion

Sentry in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

2 h 12 min

This incident

35% 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 2 h 12 min

90 days agoToday

Other Sentry incidents

All incidents

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 11 d ago

Sentry·Sentry.io not loading in US region

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

Resolvedresolved 11 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 12 d ago

Sentry·Sentry is down

Backlogs have been processed and we are back to normal.

Resolvedresolved 13 d ago

Sentry·Ingestion Halted for EAP data in EU

The issue with EAP ingestion in EU has been resolved.

Resolvedresolved 18 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