Fivetran: Connections in some cloud service provider regions are intermittently missing scheduled sync runs
Incident
Report for Fivetran
Resolved
Description:
We identified an issue with our connector sync scheduler in the following regions. While no user-facing errors would have been observed, connector syncs would not have been running as scheduled.
aws/ap-southeast-2
aws/eu-central-1
aws/eu-west-1
aws/eu-west-2
azure/australiaeast
azure/germanywestcentral
azure/switzerland-north
azure/westeurope
gcp/asia-northeast1
gcp/asia-southeast1
gcp/australia-southeast1
gcp/europe-west3
Timeline:
This issue began on May 23, 2025, at 3:36 PM UTC and was resolved on May 23, 2025, at 6:56 PM UTC.
Cause:
Our infrastructure resources in the regions referenced above were at full capacity due to a recently introduced issue that impacted built-in autoscaling. This prevented the initialization of some sync runs as the required resources were not available.
Resolution:
We resolved the issue and increased our infrastructure resources in these regions, allowing all syncs to run again according to schedule.
We identified an issue with our connector sync scheduler in the following regions. While no user-facing errors would have been observed, connector syncs would not have been running as scheduled.
aws/ap-southeast-2
aws/eu-central-1
aws/eu-west-1
aws/eu-west-2
azure/australiaeast
azure/germanywestcentral
azure/switzerland-north
azure/westeurope
gcp/asia-northeast1
gcp/asia-southeast1
gcp/australia-southeast1
gcp/europe-west3
Timeline:
This issue began on May 23, 2025, at 3:36 PM UTC and was resolved on May 23, 2025, at 6:56 PM UTC.
Cause:
Our infrastructure resources in the regions referenced above were at full capacity due to a recently introduced issue that impacted built-in autoscaling. This prevented the initialization of some sync runs as the required resources were not available.
Resolution:
We resolved the issue and increased our infrastructure resources in these regions, allowing all syncs to run again according to schedule.
This incident affected: Systems (General Services).