Fivetran incident
3rd Party: Amazon Selling Partner Connection syncs are failing with 500 Internal Server Error
Fivetran experienced a minor incident on May 8, 2026 affecting Amazon Selling Partner, lasting 6h 36m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 08, 2026, 02:35 AM UTC
The issue has been identified and we are working to resolve it.
- identified May 08, 2026, 02:40 AM UTC
Syncs are failing with 500 Internal Server Error due to degraded performance in the Amazon Selling Partner API, as indicated on their status page. This is a third-party issue on ASP's side, and we are continuing to monitor the connections. ASP Status Page: https://sellercentral.amazon.com/sp-api-status
- identified May 08, 2026, 05:37 AM UTC
Syncs continue to fail due to the issue on ASP’s side. In parallel, we’re actively exploring potential workarounds to help mitigate the impact while the underlying issue is being resolved.
- monitoring May 08, 2026, 07:31 AM UTC
Connection syncs are succeeding, and we continue to monitor the connections closely.
- resolved May 08, 2026, 09:11 AM UTC
This incident has been resolved. We have observed that instance rates are returning to normal levels and affected connections are syncing successfully. Incident Summary Description: We identified an issue with Amazon Selling Partners connection, which resulted in syncs failing with "HTTP 500 Internal Server Error" Timeline: This issue began on 2026-05-08 01:00 UTC and was resolved on 2026-05-08 08:00 UTC. Cause: The issue was caused by the third-party, Orders endpoint failed with "HTTP 500 Internal Server Error" . due to degraded performance in the Amazon Selling Partner API, as indicated on their status page. Resolution: The issue was automatically resolved from the third-party side without any intervention from the Fivetran end.