Provider resolved: . The notice publication date does not establish the outage start.
Samsara
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 identified an issue affecting Samsara connections that caused syncs to fail with the error: 'java.lang.RuntimeException: java.lang.IllegalArgumentException: Schema and name must not be null' .
Timeline:
This issue began on Sep 16, 2026, at 6:24 PM UTC and was resolved on Sep 16, 2026, at 11:10 PM UTC.
Cause:
The failure was caused by an issue in the schema migration code introduced during a recent rollout.
Resolution:
We implemented a fix to address the schema migration issue, after which syncs began succeeding again.
monitoring
We’ve implemented changes related to schema migration, and syncs are now succeeding. We’re continuing to monitor the connections
We will continue to monitor all affected connectors until they resume their normal sync functionality.
Next Expected Update: 3 hours
identified
We’ve identified the cause of the connection failure and are actively investigating further. The issue appears to be related to a schema migration failure, which is preventing the connection from completing successfully. Our engineering team is working on a fix.
identified
The issue has been identified and we are working to resolve it.
3rd Party: Microsoft Advertising/Bing Ads connections are failing due to source-side errors.
Provider resolved: . The notice publication date does not establish the outage start.
Microsoft Advertising
resolved
Bing Ads' Bulk Download API stalled broadly on 2026-09-16, ~13:00–18:00 UTC; polls returned RequestStatus=InProgress, PercentComplete=1 for the entire sync duration and never advanced.
This, along with intermittent RequestStatus=Failed, ErrorCode=InternalError responses confirmed a true Microsoft backend issue.
This issue has been resolved source-side and connectors are syncing successfully.
monitoring
It looks like the issue is on the Microsoft Advertising side, and the same has already been reported on their status page: https://status.ads.microsoft.com/
The connections have started recovering, and we are currently monitoring the situation to ensure they continue to recover as expected.
identified
The issue has been identified and we are working to resolve it.
3rd Party: Salesforce syncs are failing due to source availability issues and HTTP 504 Gateway Timeout errors.
Provider resolved: . The notice publication date does not establish the outage start.
Salesforce
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 identified an issue affecting Salesforce connectors which resulted in syncs failing with HTTP 504 Gateway Timeout and Salesforce source is not available at this time errors.
Timeline: This issue began on 2026-09-16 at 07:58:00 UTC and was resolved on 2026-09-16 at 14:50:00 UTC.
Cause: An upstream outage on Salesforce's platform rendered their API endpoints unavailable for over 6 hours.
Resolution: Salesforce deployed a fix to resolve their third-party service disruption. Once API availability was restored, connector success rates returned to normal.
Note on Required Re-authorization: Because Salesforce couldn't handle requests during this 6+ hour window, routine OAuth token refreshes failed, causing access and refresh tokens to lapse.
Connections whose tokens lapsed during the outage are currently displaying a Reconnect or Reauthorize OAuth task with the error invalid_grant: expired access/refresh token.
Impacted customers must re-authenticate their connection in the Fivetran Dashboard to obtain new tokens and resume syncs. Direct product communications are being sent to affected customers with re-authorization instructions.
monitoring
The third-party service provider has completed the fix deployment.
We will continue to monitor all affected connectors.
Next Expected Update: 3 hours
identified
We are closely monitoring the rollout and investigating the remaining failures.
Next Expected Update: 1 hour
identified
The third-party service provider has validated a fix and is rolling it out to all impacted instances: https://status.salesforce.com/incidents/20004433
Next Expected Update: 1 hour
identified
The issue is still ongoing, and Salesforce connections continue to intermittently failing.
We are monitoring the related third-party service disruption: https://status.salesforce.com/incidents/20004433 and will provide further updates as they become available.
**Next expected update:** In 1 hour
identified
We have identified an issue where Salesforce connections are intermittently failing due to source availability issues and HTTP 504 Gateway Timeout errors. We are currently investigating in more detail.
The issue is related to an ongoing third-party service disruption: https://status.salesforce.com/incidents/20004433
Next Expected Update: 1 hour
3rd Party: Pinterest Ads Third Party Outage Service Unavailable
Provider resolved: . The notice publication date does not establish the outage start.
Google Ads
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 identified an issue with Google Ads connections, which resulted in syncs failing with an `Unknown failure.com/google/api/gax/rpc/ResourceNameExtractor` error.
Timeline:
The issue began on September 10th, 2026, at 16:10 UTC and was resolved on September 10th, 2026, at 19:32 UTC
Cause:
A change was inadvertently applied to the affected connections, resulting in sync failures.
Resolution:
The issue was resolved by reverting the change for all affected connections. Affected syncs have since recovered.
identified
We have identified that the sync failures were caused by a recent code update. Our team is currently deploying a fix to revert the change and restore normal sync functionality.
Next Expected Update: 1 hour
identified
We have identified an issue where Google Ads connectors are failing with an "Unknown failure" exception. We are currently investigating in more detail.
Next Expected Update: 1 hour
3rd Party: Apple Search Ads Connections Failing With a Reconnect Task
Provider resolved: . The notice publication date does not establish the outage start.
Apple Search Ads
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 identified an issue for Apple Search Ads which resulted in syncs failing with a 403 error.
Timeline:
This issue began on Sep 9, 2026 at 09:00 UTC and was resolved on Sep 9, 2026 at 13:50 UTC.
Cause:
This was caused due to product-page* endpoints being disabled on Apple's end.
Resolution:
A hotfix was deployed that disabled syncing for product-page* tables.
monitoring
We have deployed a fix to skip the disabled Product Pages endpoint, which has seen a reduction in failures.
We will continue monitoring all affected connectors to ensure they resume normal sync functionality.
investigating
Our engineering team have merged a hotfix for the issue and is awaiting deployment.
Next Expected Update: 2 hours
investigating
We have identified an issue where Apple Search Ads connections are failing with a 403 - Reconnect task.
This appears to be due to a disabled endpoint on Apple's end. We are working on a hotfix to handle this behaviour.
Next Expected Update: 1 hour
Fivetran: Transformations are failing with a “dbt job terminated unexpectedly” error.
Provider resolved: . The notice publication date does not establish the outage start.
General Services
resolved
This incident has been resolved. We have observed that instance rates are returning to normal levels and affected transformations are syncing successfully.
Incident Summary
Description:
We identified an issue where Transformations are failing with a “dbt job terminated unexpectedly” error.
Timeline:
This issue began on 2026-09-03 at 12:54 UTC and was resolved on 2026-09-03 at 14:23 UTC.
Cause:
A configuration issue temporarily prevented transformation jobs from accessing the components required to run. As a result, affected transformation jobs were unable to start as expected.
Resolution:
We fixed the configuration issue and restored the permissions for the affected services.
monitoring
We have deployed a fix for this issue.
We will continue to monitor all affected transformations until they resume their normal sync functionality.
Next Expected Update: 3 hours
identified
The issue has been identified and we are working to resolve it.
Next Expected Update: 1 hour
3rd Party: Navan connections are failing due to an HTTP 504 Gateway Timeout error
Provider resolved: . The notice publication date does not establish the outage start.
Navan
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 identified an issue for Navan connections, which resulted in syncs failing with an HTTP 504 Gateway Timeout error on the expense/transactions endpoint.
Timeline:
This issue began on 2026-09-02 at 4:30 AM UTC and was resolved on 2026-09-02 at 1:00 PM UTC.
Cause:
The failures were caused by intermittent HTTP 504 Gateway Timeout responses from Navan’s expense/transactions API endpoint.
Resolution:
The source API recovered, and subsequent sync attempts completed successfully without any changes required to the Fivetran connector. We monitored the affected connections and confirmed that failure rates returned to normal levels.
monitoring
A fix has been implemented and we are monitoring the results.
identified
We have identified an issue where Navan connections are failing with HTTP 504 Gateway Timeout errors on the expense/transactions endpoint.
Some affected connections completed successfully during subsequent sync attempts, indicating that the issue may be intermittent and source-side.
We are contacting Navan to investigate the endpoint timeouts, as Navan’s status page currently shows no related incident. We will continue monitoring affected connections.
identified
The issue has been identified and we are working to resolve it.
Provider resolved: . The notice publication date does not establish the outage start.
General Services
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
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
Legacy Incident Archive
66 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
July 2026
3rd Party: Some Ramp connections failing with 529 response errors
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
We have identified that the source API is repeatedly returning HTTP 529 responses, causing sync failures.
We are actively working with the third-party source to resolve the issue and will continue to provide updates.
<b>Next Expected Update: 1 hour</b>
identified
The issue has been identified and we are working to resolve it.
3rd Party: QuickBooks connections failing with “Failed to sync 1 endpoint” error
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
We have deployed a fix for this issue by switching to the new entity for data retrieval for the table CreditCardPayment
We will continue to closely monitor all affected connections until they have fully recovered and returned to normal sync operations.
<b>Next Expected Update: 1 Hour </b>
identified
We have identified that the issue occurs when querying the CreditCardPaymentTxn entity. The source API is returning the following error:
"invalid context declaration: creditcardpaymenttxn"
This appears to be happening because the source may have changed the entity name from CreditCardPaymentTxn to CreditCardPayment. Our team is working on accommodating this change.
<b>Next Expected Update:</b> 1 hour
identified
The issue has been identified and we are working to resolve it.
June 2026
Fivetran: Apple Search Ads connections are failing with error "HTTP 400 Bad Request"
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
A hotfix has been deployed, and the syncs are recovering. We will continue monitoring the syncs
<b>Next Expected Update: 3 hours</b>
identified
We have identified that this issue was caused by a recent change, and we are currently working on reverting the changes via a hotfix.
<b>Next Expected Update: 2 hours</b>
identified
The issue has been identified and we are working to resolve it.
Fivetran: Multiple Hybrid Deployment Connections are failing
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
We have deployed a fix for this issue.
We will continue to monitor all affected connectors until they resume their normal sync functionality.
<b>Next Expected Update: 3 hours</b>
identified
We are continuing to work on a fix for this issue.
<b>Next Expected Update: 1 hour</b>
identified
We have identified that this issue was caused by a recent change, and we are currently working on a HotFix.
<b>Next Expected Update: 1 hour</b>
identified
We have identified an issue where Hybrid Deployment Connections are failing with a "Failed to generate data key for HD encryption context" or "Failed to receive message length" exception. We are currently investigating in more detail.
<b>Next Expected Update: 1 hour</b>
3rd Party: Multiple Customer.io connections are failing with 5xx error
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
We observed a shift in the issue behavior around 12:00 UTC for the Customer export api. While initial failures occurred during job creation, the connector is now failing during the report download phase.
- We have implemented a skip mechanism to mitigate these 502 errors on the affected endpoints, and are continuing to closely monitor all active syncs.
- Additionally, we reported the ongoing behavior to Customer.io, as their initial fix did not resolve the issue. We are currently awaiting th...
monitoring
We noticed that the connections were failing again with "502 Server Error". We've raised a hotfix, and the failures are gradually reducing. We're monitoring the affected connections.
<b>Next Expected Update:</b> < 3 hours >
monitoring
We are continuing to monitor all affected connectors after the recent fix deployment.
<b>Next Expected Update:3 hours </b> <3 hours = P2, 2 hours = P1>
monitoring
A hotfix has been deployed to skip the failing endpoints until the source resolves the issue. We will continue monitoring the connections while we wait for a response from the source team.
<b>Next Expected Update: 3 hours</b> <3 hours = P2, 2 hours = P1>
identified
We are preparing a fix to skip the failing endpoints until the source resolves the issue.
<b>Next Expected Update: 1 hour</b> <1 hour = P2, 30 minutes = P1>
identified
We identified that multiple REST API requests are failing with 502 Bad Gateway errors returned by the source API.
We have reached out to the source regarding this.
<b>Next Expected Update: 1 hour</b> <1 hour = P2, 30 minutes = P1>
identified
The issue has been identified and we are working to resolve it.
3rd Party: Some Impact Brand connections are failing with "HTTP 500 Internal server" error
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
We identified that this issue is caused by the source API returning 500 Internal Server Errors, impacting the following tables: performance_by_partner, performance_by_day, adv_performance_by_ad_media_date.
We have reached out to the source regarding this issue. We are also observing that affected connectors are recovering without any intervention from Fivetran.
<b>Next Expected Update: 1 hour</b>
identified
The issue has been identified and we are working to resolve it.
May 2026
Fivetran: Hybrid Deployment Agent jobs failing to start with error "Connection pool shut down"
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
We are monitoring the results of the fix. Customers are advised to restart their HD agents.
identified
The hot fix should be reflected in the new HD agent images.
For existing HD agents, restarting the controller should resolve the issue. Customers are advised to restart their controller with the following commands:
cd ~/fivetran
./hdagent.sh stop
./hdagent.sh start
identified
We have identified the root cause and have deployed a hot fix.
identified
The Fivetran Hybrid Deployment Agent is experiencing an issue that may cause syncs to fail to start or connections to fail during setup tests and syncs. HD agent logs show the following error
"Return CreateJobResponse/Failure, Caused By User: false - CREATE_JOB_ERROR/Connection pool shut down {process_id=XXX}"
This issue only affects HD deployments in Docker/Podman environments.
3rd Party: Google Display & Video 360 connections are failing with "HTTP 502 Bad Gateway" error
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and we are working to resolve it.
Multiple connection syncs are failing with an "Internal: Failed to read token" error.
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and we are working to resolve it.
Fivetran: Delay in User facing logs and External logs delivery
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and we are working to resolve it.
