Session Replay capturing more sessions than configured

What to do

• Check whether you use Amplitude Session Replay. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 28m it lasted.

  Anything that failed between 2026-11-05 14:56 UTC and 2026-11-05 15:24 UTC may need a replay.

• Subscribe to Amplitude's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=amplitude works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Amplitude 3

1. identifiedNov 5, 2026, 2: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.

   provider

2. monitoringNov 5, 2026, 3: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.

   provider

3. resolvedNov 5, 2026, 3: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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.