Fivetran incident
3rd Party: Twilio connections are failing with "504 Gateway Timeout ERROR"
Resolved after 1 hour 19 minutes, affecting Twilio, on May 8, 2026.
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 the Twilio connection, which resulted in syncs failing with "504 Gateway Timeout Error" Timeline: This issue began on 8th May 2026 at 01:20 AM UTC and was resolved on 8th May 2026 at 02:41 AM UTC. Cause: The issue was caused by the third-party call endpoint failing with "504 Gateway Timeout Error". Twilio has also updated their status page, confirming the degraded performance. Resolution: The issue was automatically resolved from the third-party side without any intervention from the Fivetran end.
Affected components
Update timeline
- identified May 08, 2026, 03:35 AM UTC
The issue has been identified and we are working to resolve it.
- monitoring May 08, 2026, 04:05 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 08, 2026, 04:54 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 the Twilio connection, which resulted in syncs failing with "504 Gateway Timeout Error" Timeline: This issue began on 8th May 2026 at 01:20 AM UTC and was resolved on 8th May 2026 at 02:41 AM UTC. Cause: The issue was caused by the third-party call endpoint failing with "504 Gateway Timeout Error". Twilio has also updated their status page, confirming the degraded performance. Resolution: The issue was automatically resolved from the third-party side without any intervention from the Fivetran end.
Your product runs on more than Fivetran
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services