rewindex

CompaniesSentryIncidents

Sentry: Ingestion Issue in US Legacy

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestspg.io (opens in new tab)

Timeline of updates

  1. resolved

    Between 07:25 UTC and 07:28 UTC, customers sending data to the legacy ingestion endpoint in our US region experienced a brief ingestion disruption lasting approximately 3 minutes. The issue has been fully resolved and ingestion is operating normally.

    Customers using modern DSN endpoints (*.ingest.us.sentry.io) were not affected.

    The disruption occurred during a scheduled configuration change. We're investing in additional tooling to detect and mitigate this class of issue faster. We apologize for the inconvenience and appreciate your patience.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Sentry, started 2026-04-22 08:26 UTC, resolved after 0 min, 1 update(s).

Title
Ingestion Issue in US Legacy
Vendor
Sentry
Date
URL
https://rewindex.com/company/sentry/incidents/9g0nslrzjd11

Sentry profileRecent Sentry incidentsAll outages on April 22, 2026Sentry in April 2026MarkdownJSON