Sentry Status · History · Incident #5192

RESOLVED

Incoherent number of processed logs

Minor · Started Jul 7, 2026 · 8:49 AM

  • Duration

    5h 46m

  • Severity

    Minor

  • Detection lead

  • User reports

Summary

Incoherent number of processed logs

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.


  • Started

    Jul 7, 2026 · 8:49 AM

  • Resolved

    Jul 7, 2026 · 2:36 PM

  • Duration

    5h 46m

  • Severity

    None

Event timeline

How this incident unfolded

  • Investigating

    Jul 7 · 8:49 AM Sentry

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

  • Resolved

    Jul 7 · 2:36 PM Sentry

    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.

Get alerted before the next Sentry outage.

Pulsetic catches degradations minutes before vendors acknowledge them.

Start monitoring free