Fivetran incident
3rd Party: Amazon Selling Partner Connection syncs are failing with 500 Internal Server Error
Affected components
Update timeline
- identified Apr 28, 2026, 06:15 PM UTC
The issue has been identified and we are working to resolve it.
- identified Apr 28, 2026, 06:35 PM UTC
We are currently seeing an increase in 500 Internal Server Error responses 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
- monitoring Apr 28, 2026, 06:54 PM UTC
The connections are recovering and we are currently monitoring the syncs.
- resolved Apr 28, 2026, 10:32 PM UTC
This incident has been resolved. We observed that syncs have recovered and are completing successfully without further failures. Incident Summary Description: We identified an issue with Amazon Selling Partner connections where syncs were failing with 500 Internal Server Error. Timeline: This issue began on 2026-04-28 at 17:39:00 UTC and was resolved on 2026-04-28 at 19:38:00 UTC. Cause: The failures were caused by a source-side outage in the Amazon Selling Partner API, resulting in 500 Internal Server Error responses. Resolution: No action was taken from our end. The issue was resolved on the source side, and syncs recovered automatically.
Looking to track Fivetran downtime and outages?
Pingoru polls Fivetran's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Fivetran reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Fivetran alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required