Session Replay capturing more sessions than configured
Amplitude Session Replay captured more sessions than the configured sample rate or targeting conditions allowed for some web projects. Amplitude reports that the issue is resolved. The incident lasted 28 minutes.
State
Resolved
Started
Lasted
28 min
Worst impact
Degraded
Timeline
3 updatesIdentified
19 min 68%
Monitoring
9 min 32%
Updates
Times in UTCAs posted by Amplitude
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.
Affected components
1Amplitude in the last 90 days
Full historyIncidents in 90 days
23
Days with an incident
24
Median duration
1 h 13 min
This incident
61% shorter than the median
Other Amplitude incidents
All incidentsAmplitude·Delayed S3 export
Amplitude S3 Data Export is delayed for some customers. The Data Export components are affected. Amplitude reports that it implemented a fix and now monitors the exports as they catch up.
Amplitude·Data Ingestion Delays
The issue has been fully resolved and data ingestion has returned to normal operation. No data was lost during this incident. We apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the issue.
Amplitude·Delayed/Blocked Event Delivery to Amazon Kinesis Destination
This incident has been resolved. Event delivery to the Amazon Kinesis streaming destination has returned to normal operation. All affected events have been successfully delivered. We apologize for the disruption and appreciate your patience while we worked to resolve this issue.
Amplitude·Streaming to External Destinations Unavailable
The issue has been fully resolved. Our Engineering team has implemented the necessary mitigation measures and functionality is now operational. We apologize for the disruption and appreciate your patience and understanding while we worked to restore service.
Amplitude·Amplitude Website Outage
This incident has been resolved.
Follow Amplitude
Your coding agent knows when Amplitude is down, and tells you when a failure is theirs, not yours. You can also get Amplitude incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "amplitude" and tell me if Amplitude has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=amplitude/feed subscribe https://outages.live/feed.xml?providers=amplitudeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane