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: identified
After: monitoring
AddedUpdatemonitoring#2
Before: not present
After: We've deployed a fix for the issue causing some web projects to capture more Session Replay sessions than their configured sample rate or targeting conditions allow. New sessions should now be captured according to your settings. We're monitoring closely and will provide another update once we've confirmed the issue is fully resolved.

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:24 UTC (change 1 of 2).

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

All Amplitude changesAmplitude profileMarkdownJSON