Sentry: Crons ingestion backlogged
Timeline of updates
- resolved
Backlog has been processed and crons should be running as normal
From Sentry’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.sentry.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Sentry, started 2026-01-23 18:38 UTC, resolved after 5.8 h, 1 update(s).
- Title
- Crons ingestion backlogged
- Vendor
- Sentry
- Date
- URL
- https://rewindex.com/company/sentry/incidents/xz3bqg4bg438
Sentry profileRecent Sentry incidentsAll outages on January 23, 2026Sentry in January 2026MarkdownJSON