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.
The issue on Qualtrics’ side has been resolved, and connector syncs are now recovering. We are continuing to monitor the results closely.
identified
Sync failures are occurring due to an outage in Qualtrics’ Ticket Export API.
We are monitoring the situation. For more details, please visit: https://status.qualtrics.com/incidents/wj65y7rwfx2j
identified
The issue has been identified and we are working to resolve it.
Fivetran: SharePoint and Microsoft Lists connections are failing with error "Authentication failed: The client secret or certificate has expired"
minorSource not attested
Last archived state: identified
View archived record details
identified
The issue has been identified and we are working to resolve it.
Fivetran: SharePoint and Microsoft Lists connections are failing with error "Authentication failed: The client secret or certificate has expired"
majorSource not attested
Last archived state: monitoring
View archived record details
monitoring
We have updated all the regions with the new secret keys and will continue to monitor the connections.
monitoring
A new secret key credential has been created to resolve the issue. Syncs are now recovering, and we are monitoring the results.
identified
Fivetran's OAuth app secret key has expired, and the team is working on creating new secret key credentials to fix the issue.
identified
The issue has been identified and we are working to resolve it.
Fivetran: SharePoint and Microsoft Lists connections are failing with error "Authentication failed: The client secret or certificate has expired"
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
A new secret key credential has been created to resolve the issue. Syncs are now recovering, and we are monitoring the results.
monitoring
A fix has been implemented and we are monitoring the results.
identified
Fivetran's OAuth app secret key has expired, and the team is working on creating new secret key credentials to fix the issue.
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
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.
3rd Party: All Amazon Selling Partner connections are rescheduled due to rate limit changes
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
We have implemented a mitigation on our end to temporarily skip the SALES_AND_TRAFFIC_BUSINESS_* tables while we await further updates from the third-party. We will continue to monitor the connections.
identified
We have observed that all the Amazon Selling Partner connections across Fivetran app, custom app and customer_oauth app are re-scheduling due to the change in rate limits from 3rd party.
identified
The issue has been identified and we are working to resolve it.
The issue has been identified and we are working to resolve it.
3rd Party: Multiple Twitter Ads connections failing due to 500 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 are continuing to work on a fix for this issue.
identified
We are receiving 500 Internal Server Errors from the Twitter API when querying the accounts endpoint.
identified
The issue has been identified and we are working to resolve it.
Sync start delays caused by Azure outage in East-US-2 region
minorSource not attested
Last archived state: identified
View archived record details
identified
Azure is continuing to rollout a fix in the East US region. We have observed our backlog of syncs are caught up, but pod scaling is still affected. Once Azure confirms they have competed their fix, we will test pod scaling to ensure it works as expected.
identified
Azure has identified the issue and they expect recovery within the next hour. Fivetran engineering will continue to monitor as Azure works through this incident.
identified
The issue was caused by an outage on Azure. You can find more details at the following link:
https://azure.status.microsoft/en-us/status
identified
The issue has been identified and we are working to resolve it.
Some syncs are failing starting at 8AM Pacific time.
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
In the last hour, we have observed sync failure rates drop to normal rates. We are continuing to monitor.
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.
