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.
May 2026
3rd Party: Talkdesk connections are failing with "HTTP 404: Report file not found" Error
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
We have coordinated with Talkdesk, and mitigation measures have been implemented on their end. Their team is actively monitoring systems as they recover.
On our end, we are observing that connector syncs are recovering from prior failures and are now completing successfully.
We will continue to closely monitor the connector syncs and provide further updates as needed.
identified
Multiple report endpoints in the US region are returning HTTP 404 errors. Initial investigation indicates this may be linked to warning statuses for Talkdesk Explore™ Reporting and Talkdesk Workforce Management™ in the US region, as shown on the Talkdesk status page. We have reached out to Talkdesk support for more details on these failures.
Talkdesk status page:
https://status.talkdesk.com/
identified
The issue has been identified and we are working to resolve it.
3rd Party: Twilio connections are failing with "504 Gateway Timeout ERROR"
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
Syncs were failing with "504 Gateway Timeout Error" for the call endpoint due to degraded performance on the Twilio side, as indicated on their status page.
The syncs have been recovered automatically without any intervention from the Fivetran end, and we are monitoring the connections.
Twilio Status Page: https://status.twilio.com/incidents/rqlltbpn6m1z
identified
The issue has been identified and we are working to resolve it.
3rd Party: Amazon Selling Partner Connection syncs are failing with 500 Internal Server Error
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
Connection syncs are succeeding, and we continue to monitor the connections closely.
identified
Syncs continue to fail due to the issue on ASP’s side. We are continuing to monitor the connections.
identified
Syncs are failing with 500 Internal Server Error due to degraded performance in the Amazon Selling Partner API, as indicated on their status page. This is a third-party issue on ASP's side, and we are continuing to monitor the connections.
ASP Status Page: https://sellercentral.amazon.com/sp-api-status
identified
The issue has been identified and we are working to resolve it.
3rd Party: Hubspot connection syncs are failing with "HTTP 500 Internal Server Error" and message: "Your HubSpot source is not available at this time. We'll retry the sync later."
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
Syncs are recovering, and we are monitoring the results.
identified
HubSpot has updated their status page, confirming the regional degradation due to the AWS outage. We are also observing that sync failure rates are decreasing. We are monitoring the situation closely.
https://status.hubspot.com/incidents/f0s8vh3hsftw ("HubSpot is experiencing a regional degradation causing issues with loading related to an AWS outage")
identified
Syncs are failing due to an issue on the third-party side, due to "HTTP 500 Internal Server Error" for the events endpoint.
At this time, there are no reported incidents or updates on the HubSpot status page related to this behaviour. We have reached out to HubSpot support for more details on these failures.
HubSpot status page link: https://status.hubspot.com/
identified
The issue has been identified and we are working to resolve it.
3rd Party: Klaviyo connection syncs are failing with Reconnect Error
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
We have deployed a fix for this issue, and a few of the connectors have recovered since then.
We will continue to monitor all affected connectors until they resume their normal sync functionality.
identified
Syncs are failing due to an issue on the third-party side with "HTTP 401 Unauthorized error" and the reconnect task: "We could not connect to Klaviyo due to an invalid API key. Please update the credentials."
We have reached out to Klaviyo support for more details on these failures. We are also exploring possible workarounds to mitigate the issue in the meantime.
identified
The issue has been identified and we are working to resolve it.
Many Connector SDK connections failed syncs with error "Failed to pull image after max retries"
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
This incident has been resolved. We have observed that instance rates are returning to normal levels and affected connectors are syncing successfully.
<b>Incident Summary</b>
Description:
We identified an issue for Connector SDK connections, which resulted in syncs failing with a "Failed to pull image after max retries" error.
Timeline:
Incident Start Time: 2026-05-04 21:51 UTC
Incident End Time: 2026-05-04 23:49 UTC
Cause:
An automated cleanup process removed a required image used for C...
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: Hybrid connections are delayed
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
A workaround has been applied. We've rolled back the image affecting Hybrid Deployment connectors, and syncs have resumed. Our team is working on a permanent fix.
identified
The issue has been identified and we are working to resolve it.
The Connector SDK Connection state not advancing
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 are continuing to work on a fix for this issue.
identified
We have identified the root cause and are working on the fix.
identified
We identified an issue where the connector SDK connection state is not advancing, resulting in the same data sync for the last few days.
3rd Party: Hubspot connection syncs are failing with error "Your HubSpot source is not responding at this time. We'll retry the sync later"
minorSource not attested
Last archived state: identified
View archived record details
identified
The issue has been identified and we are working to resolve it.
April 2026
3rd Party: Amazon Selling Partner Connection syncs are failing with 500 Internal Server Error
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
The connections are recovering and we are currently monitoring the syncs.
identified
We are currently seeing an increase in 500 Internal Server Error responses due to degraded performance in the Amazon Selling Partner API, as indicated on their status page. This is a third-party issue on ASP's side, and we are continuing to monitor the connections.
ASP Status Page: https://sellercentral.amazon.com/sp-api-status
identified
The issue has been identified and we are working to resolve it.
