Minor impactResolvedMonitoring

Sentry incident: Span ingestion is degraded in US

Sentry reported this minor-impact incident on its official status page on Sep 1, 2026, 14:16 UTC. It was resolved after 6h 14m.

Right now Sentry is operational. Live Sentry status →

🔔 Get alerted when Sentry has issuesFree · email alerts · no credit card
Sep 1, 2026, 14:16 UTC
started
Sep 1, 2026, 20:29 UTC
resolved
6h 14m
duration
Minor
impact

Affected components

  • US Ingestion - US Span Ingestion

Timeline

updates from Sentry's status page ↗
  1. resolvedSep 1, 2026, 20:29 UTC

    Spans ingestion is now operating normally.

  2. monitoringSep 1, 2026, 19:31 UTC

    Latency is almost fully recovered.

  3. monitoringSep 1, 2026, 18:30 UTC

    A fix has been implemented, and latency is coming down.

  4. investigatingSep 1, 2026, 17:50 UTC

    We are continuing to investigate an issue that affects spans ingestion latency

  5. investigatingSep 1, 2026, 16:41 UTC

    We are continuing to investigate an issue that affects spans ingestion latency

  6. investigatingSep 1, 2026, 15:40 UTC

    We are continuing to investigate an issue that affects spans ingestion latency

  7. investigatingSep 1, 2026, 14:16 UTC

    We are experiencing slow ingestion for spans in US

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Sentry's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

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, 15 of them major or critical. A typical incident lasted 3h. See Sentry's uptime and incident history

← Previous: Sentry requests timing out / 504's (Sep 1, 2026)Next: Sentry.io elevated number of 500 errors (Sep 10, 2026) →
Sentry incident on Sep 1, 2026: Span ingestion is degraded in US · APIStatus.watch