Sentry: Sentry Denial of Service
Timeline of updates
- resolved
On November 27 between 21:46 - 21:57 UTC, there was a denial of service attack on Sentry sending up to 10x the normal volume of traffic. Our systems scaled up within 6 minutes to accommodate this traffic. Between 21:46 - 21:52 UTC some customers may have experienced traffic loss of up to 80%. We are implementing changes to our ingestion layer to reduce the impact of similar attacks in the future.
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 2024-11-27 19:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Sentry Denial of Service
- Vendor
- Sentry
- Date
- URL
- https://rewindex.com/company/sentry/incidents/8fmx5qrg2k5z
Sentry profileRecent Sentry incidentsAll outages on November 27, 2024Sentry in November 2024MarkdownJSON