Fivetran incident
Fivetran: Postgres: Expanding column in schema tab throws "Fetch source columns failed"
Affected components
Update timeline
- identified Mar 11, 2026, 09:25 PM UTC
The issue has been identified and we are working to resolve it.
- identified Mar 11, 2026, 09:28 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Mar 12, 2026, 02:56 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 12, 2026, 03:31 AM UTC
This incident has been resolved. We have observed that instance rates are returning to normal levels and affected connectors are syncing successfully. Incident Summary Description: We identified an issue for PostgreSQL connectors which resulted in schema fetch failing with a "Fetch source columns failed" error. Users were unable to expand tables or edit column configs in the Schema tab. The issue also impacted Terraform users, who experienced HTTP 400 errors when attempting to retrieve schema columns. Timeline: The issue began on March 11, 2026 at 01:48 UTC and was fully resolved on March 12, 2026 at 02:48 UTC. Cause: The issue was caused by a recent code change made to the connector. Resolution: Engineering identified the root cause and reverted the recent changes. After deploying the revert and a hotfix, the connectors resumed normal operation.
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