Amplitude incident

Session Replay capturing more sessions than configured

Resolved after 28 minutes, affecting Session Replay, on November 5, 2026.

resolved Nov 05, 2026, 03:24 PM UTC

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.

Started
Nov 05, 2026, 02:56 PM UTC
Resolved
Nov 05, 2026, 03:24 PM UTC
Duration
28m
Detected by Pingoru
Nov 05, 2026, 02:56 PM UTC

Affected components

Session Replay

Update timeline

  1. identified Nov 05, 2026, 02:56 PM UTC

    We’ve identified an issue affecting Session Replay for some web projects. Since October 28, 2026, some projects may be capturing more sessions than their configured sample rate or targeting conditions allow, which can increase Session Replay usage. Our engineering team has identified the cause and is working on a fix. We’ll provide an update as soon as possible, and we’re reviewing the impact on Session Replay usage for affected customers.

  2. monitoring Nov 05, 2026, 03:15 PM UTC

    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.

  3. resolved Nov 05, 2026, 03:24 PM UTC

    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.

Your product runs on more than Amplitude

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →