rewindex

ChangesAmplitudeSession Replay capturing more sessions than configured

Amplitude: Incident updated: Session Replay capturing more sessions than configured

Incident updateNormal progress (rule, 100%)Changed status.amplitude.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Amplitude removed; blue is what they added. Muted text is unchanged context.

ChangedStatus#1
Before: monitoring
After: resolved
AddedResolved time#2
Before: not present
After: 2026-11-05 15:24 UTC
AddedUpdateresolved#3
Before: not present
After: We've now confirmed that the fix is fully resolved. Session Replay is now capturing sessions according to each project's configured sample rate and targeting conditions. We apologize for any impact this may have caused and thank you for your patience while we investigated.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

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 these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this incident

Thursday, November 5

2 incident changes

Cite this

Incident updated: Session Replay capturing more sessions than configured on Amplitude’s status page, changed 2026-11-05 15:34 UTC (change 2 of 2).

Title
Incident updated: Session Replay capturing more sessions than configured
Vendor
Amplitude
Date
URL
https://rewindex.com/change/r6d8818f3adc94a

All Amplitude changesAmplitude profileMarkdownJSON