Minor impactResolvedMonitoring

Sentry incident: Ingestion delays across all data

Sentry reported this minor-impact incident on its official status page on Nov 4, 2026, 17:31 UTC. It was resolved after 1h 10m.

Right now Sentry is operational. Live Sentry status →

🔔 Get alerted when Sentry has issuesFree · email alerts · no credit card
Nov 4, 2026, 17:31 UTC
started
Nov 4, 2026, 18:41 UTC
resolved
1h 10m
duration
Minor
impact

Affected components

  • Custom Metrics (beta)
  • US Attachment Ingestion
  • US Cron Monitoring
  • US Error Ingestion
  • US Profile Ingestion
  • US Replay Ingestion
  • US Span Ingestion
  • US Transaction Ingestion
  1. resolvedNov 4, 2026, 18:41 UTC

    The issue causing ingestion delays in our US region has been resolved, all data has been backfilled and latency has returned to normal.

  2. monitoringNov 4, 2026, 18:10 UTC

    We are backfilling transaction events ingested received >1 hour ago, and still burning our backlog for uptime events in US. All other event types in our US region are being ingested with normal latency.

  3. monitoringNov 4, 2026, 17:46 UTC

    We have identified the issue causing ingestion delays in our US region, and have deployed a fix. We are monitoring the fix while we burn our event backlog.

  4. monitoringNov 4, 2026, 17:31 UTC

    We are monitoring an issue involving increased ingestion latency across all our datasets.

What APIStatus.watch saw

  • Nov 4, 2026, 17:34 UTCoperational → degraded
  • Nov 4, 2026, 18:44 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Sentry have incidents?

Sentry reported 25 incidents in the last 90 days, 16 of them major or critical. A typical incident lasted 1h 45m. See Sentry's uptime and incident history