rewindex

CompaniesSentryIncidents

Sentry: Incoherent number of processed logs

No impact listedStatus: resolvedStarted Resolved (5.8 h)2 updatesstspg.io (opens in new tab)

Affected components: Dashboard

Timeline of updates

  1. investigating

    We are currently investigating reports of inconsistent reported number of processed logs in Sentry for the last day

  2. resolved

    Between July 6th 20:25 UTC and July 7th 12:25 UTC, a wrong configuration change was deployed causing over-sampling of logs, spans and metrics.
    The configuration change is now reverted and the issue is fixed.

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-07-07 08:49 UTC, resolved after 5.8 h, 2 update(s).

Title
Incoherent number of processed logs
Vendor
Sentry
Date
URL
https://rewindex.com/company/sentry/incidents/rxjtcg6mnvdd

Sentry profileRecent Sentry incidentsAll outages on July 7, 2026Sentry in July 2026MarkdownJSON