Outage in Fivetran
3rd Party: Twilio connections are failing with "504 Gateway Timeout ERROR"
Resolved MinorIncident Report
Summary AI Generated
Fivetran's Twilio connections experienced sync failures with "504 Gateway Timeout Error" due to degraded performance on Twilio's third-party service. The issue affected Twilio data syncs for approximately 1.4 hours on May 8th, 2026, from 01:20 AM to 02:41 AM UTC. The problem was automatically resolved from Twilio's side without requiring intervention from Fivetran, and all affected connections returned to normal syncing operations.
The issue has been identified and we are working to resolve it.
Components affected
Fivetran TwilioTrusted by 1,000+ teams
Never miss outages in third-party dependencies
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
Latest Updates ( sorted recent to last )
RESOLVED
1 day ago - at 05/08/2026 04:54AM
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.
MONITORING
1 day ago - at 05/08/2026 04:05AM
Syncs were failing with "504 Gateway Timeout Error" for the call endpoint due to degraded performance on the Twilio side, as indicated on their status page.
The syncs have been recovered automatically without any intervention from the Fivetran end, and we are monitoring the connections.
Twilio Status Page: https://status.twilio.com/incidents/rqlltbpn6m1z
IDENTIFIED
1 day ago - at 05/08/2026 03:35AM
The issue has been identified and we are working to resolve it.
Latest Fivetran outages
3rd Party: Amazon Selling Partner Connection syncs are failing with 500 Internal Server Error - 1 day ago
Many Connector SDK connections failed syncs with error "Failed to pull image after max retries" - 5 days ago
Fivetran: Hybrid connections are delayed - 5 days ago
Never miss outages in third-party dependencies
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with
