New Multi-region uptime checks and custom-domain status pages

Syncs did not start on schedule.

Minor Impact Resolved Notice published: August 31, 2026
View the provider incident record →

Current answer

Fivetran experienced a minor incident: Syncs did not start on schedule.. Resolved on Aug 31, 2026.

Official Fivetran status page Current Fivetran status Provider update:

The notice publication date does not establish the outage start. Provider resolved: .

Looking for an update now? Check the current status, or follow Fivetran for future changes.

Provider notice timeline

Investigating
Affected Components
General Services

Incident Timeline

Resolved
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 saw a drop in the number of syncs across all regions starting at about 18:50 UTC (11:50 PT) lasting until ~19:25 UTC (12:35 PT).

Cause:
We are investigating with the cloud vendor we use for our job scheduling service to uncover a possible service outage.

Resolution:
Automatic recovery mechanisms
Aug 31, 2026 at 8:59 PM UTC
Investigating
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 saw a drop in the number of syncs across all regions starting at about 18:50 UTC (11:50 PT) lasting until ~19:25 UTC (12:35 PT).

Cause:
We are investigating with the cloud vendor we use for our job scheduling service to uncover a possible service outage.

Resolution:
Automatic recovery mechanisms
Aug 31, 2026 at 8:58 PM UTC
Was your business affected by this Fivetran outage?
Follow Fivetran and route available status alerts to email or a team channel.