Resolved on March 16, 2026.
Description We identified an issue with our public REST API that caused API calls to fail with a "column api.disabled_at does not exist" exception. Timeline: This issue began on 22:15 UTC on March 16, 2026 and was resolved on 22:50 UTC on March 16, 2026. Cause: A migration change caused the issue. Resolution: A fix was implemented to address the migration issue, after which instance rates and all implementations of the Fivetran public REST API returned to normal.
Update timeline
- resolved Mar 16, 2026, 11:23 PM UTC
Description We identified an issue with our public REST API that caused API calls to fail with a "column api.disabled_at does not exist" exception. Timeline: This issue began on 22:15 UTC on March 16, 2026 and was resolved on 22:50 UTC on March 16, 2026. Cause: A migration change caused the issue. Resolution: A fix was implemented to address the migration issue, after which instance rates and all implementations of the Fivetran public REST API returned to normal.
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.