Delayed S3 export
Amplitude S3 Data Export was delayed for some customers. The incident affected the Data Export components. Amplitude reports that the incident is resolved. It lasted about 109 minutes.
State
Resolved
Started
Lasted
1 h 49 min
Worst impact
Degraded
Timeline
5 updatesInvestigating
22 min 21%
Identified
27 min 25%
Monitoring
1 h 55%
Updates
Times in UTCAs posted by Amplitude
This incident has been resolved. We don't expect any data loss, and no action is required on your end.
We are continuing to monitor for any further issues. We will provide another update in 30 minutes.
A fix has been implemented, and exports are catching up. We’re monitoring progress and will provide another update in 30 minutes.
The issue has been identified and mitigated, and affected customers should see an improvement. We’re implementing a fix, but the issue may recur until that work is complete. We’ll provide another update in 30 minutes.
During November 5, from 5:00 AM to 10:18 AM UTC, S3 Data Export is delayed for some customers. Affected export pipelines are currently blocked, but no data loss is expected. We are actively working to restore the affected pipelines. We will provide another update in 30 minutes.
Affected components
2Amplitude in the last 90 days
Full historyIncidents in 90 days
23
Days with an incident
24
Median duration
1 h 15 min
This incident
1.5× the median
Other Amplitude incidents
All incidentsAmplitude·Session Replay capturing more sessions than configured
Amplitude Session Replay captured more sessions than the configured sample rate or targeting conditions allow for some web projects. Amplitude reports that the issue is resolved. The incident lasted 28 minutes and started on November 5, 2026.
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.cc/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.cc/feed.xml?providers=amplitude/feed subscribe https://outages.cc/feed.xml?providers=amplitudeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane