rewindex

CompaniesSentryIncidents

Sentry: Stats Backend: Data Loss

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

Timeline of updates

  1. resolved

    We experienced an issue (due to an operational error) which caused historical data loss in many graphs. Specifically this affected the longer-range intervals, not our short-frame graphs used for calculating rate limits and various alerting. This was a one time event. Please contact us if you have any concerns.

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 2015-01-22 00:57 UTC, resolved after 0 min, 1 update(s).

Title
Stats Backend: Data Loss
Vendor
Sentry
Date
URL
https://rewindex.com/company/sentry/incidents/0f8k7g4ky835

Sentry profileRecent Sentry incidentsAll outages on January 22, 2015Sentry in January 2015MarkdownJSON