Amplitude reported this minor-impact incident on its official status page on Nov 5, 2026, 14:56 UTC. It was resolved after 28 min.
Right now Amplitude is in an unknown state. Live Amplitude status →
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.
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.
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.
Overlapping incidents aren't necessarily related.
Amplitude reported 14 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 1h 42m. See Amplitude's uptime and incident history