Export Destinations data delivery issue
This incident has been resolved. All affected export jobs have fully recovered and are running normally. We don't expect any data loss, and no action is required on your end.
The latest update from Amplitude.
State
Resolved
Started
39 d ago
2026-09-23 08:02 UTC
Lasted
6 h 5 min
until 2026-09-23 14:07 UTC
Worst impact
Partial outage
Timeline
10 updatesInvestigating
38 min 10%
Monitoring
5 h 28 min 90%
Updates
Times in UTCAs posted by Amplitude
This incident has been resolved. All affected export jobs have fully recovered and are running normally. We don't expect any data loss, and no action is required on your end.
We are continuing to monitor for any further issues.
Automatic export jobs are running again for most customers. Recovery looks on track, though we're still confirming full resolution and continuing to monitor closely. No customer action is required at this time
We're seeing recovery across most affected export jobs, and most customers should now see exports returning to normal. A subset of jobs are still catching up, and we're continuing to monitor until all exports are fully recovered. No customer action is required at this time.
We've identified that this issue can also affect exports without event filtering, due to backlog from the affected jobs. Previously we noted impact was limited to exports with event filtering, we're updating that guidance as we've confirmed broader impact. If you're experiencing delayed or stalled exports to S3, BigQuery, or Snowflake, this may be related, even without filtering configured. We're still working to confirm exports are getting back to normal. No customer action is required at this time.
We're still working to confirm that automated data exports are getting back to normal. No customer action is required at this time.
We continue to monitor system recovery following the deployed fix for automated data exports. No customer action is required at this time.
We continue to monitor system recovery following the deployed fix for automated data exports. No customer action is required at this time.
Since 2026-09-22 16:50 PT (23:50 UTC), we experienced an issue with automated data exports to export destinations that filter events before export. We have deployed a fix and are now monitoring the system to confirm exports and backfills fully recover. No data has been lost. No customer action is needed at this time.
Since 2026-09-22 16:50 PT (23:50 UTC), we have been experiencing an issue with automated data exports to all export destinations. This only affects exports that filter events before export. Customers using export destinations may notice that new data is not being delivered to your destination. Our team is actively investigating the source of the issue and working to restore exports as quickly as possible. No data will be lost; once resolved, exports will resume and backfill automatically. No customer action is needed at this time.
Affected components
2Amplitude in the last 90 days
Full historyIncidents in 90 days
21
Days with an incident
23
Median duration
1 h 15 min
This incident
4.9× the median
Other Amplitude incidents
All incidentsAmplitude·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.
Amplitude·Notice: Amplitude not impacted by recent PHP vulnerabilities
Amplitude has confirmed that no first-party Amplitude services are impacted by the PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619 (PHP2Shell Advisory). We are working with an affected third-party vendor to establish security updates on their end; however, internal hardening efforts should prevent potential escalation. No customer action is required at this time. As this is a developing advisory, any further updates will be communicated appropriately via our Trust Center at https://trust.amplitude.com/updates?tab=updates&update=65d46972-f7ed-4f53-bccf-f86f1d18393e. Please subscribe to our Trust Center for notification on updates as no further updates will be made on our Statuspage here.
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