Fivetran incident

3rd Party: Twilio connections are failing with "504 Gateway Timeout ERROR"

Fivetran experienced a minor incident on May 8, 2026 affecting Twilio, lasting 1h 19m. The incident has been resolved; the full update timeline is below.

Started: May 08, 2026, 03:35 AM UTC
Resolved: May 08, 2026, 04:54 AM UTC
Duration: 1h 19m
Detected by Pingoru: May 08, 2026, 03:35 AM UTC

Affected components

Twilio

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.