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.
April 2026
Delay in log delivery in customer's external log due to an issue with our external logging services
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
There is an outage in the external logging API “Splunk Log,” causing delays. Splunk has also reported this incident on their status page: https://status.splunkcloud.com/
This resulted in a buildup of Splunk log messages in our internal queue, impacting log delivery across other logging services. The team has deployed a fix to prevent delays to other logging services. The Splunk issue also appears to be resolved, and we are actively monitoring the system.
identified
The issue has been identified and we are working to resolve it.
March 2026
Fivetran: Few Pipedrive connections are failing with the Null exception.
minorSource not attested
Last archived state: identified
View archived record details
identified
The issue has been identified and we are working to resolve it.
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: PostgreSQL Connections Using RDS Proxy Are Failing with the Error: The source database does not support a provided lock_timeout parameter
minorSource not attested
Last archived state: identified
View archived record details
identified
We are continuing to work on a fix for this issue.
identified
The issue has been identified and we are working to resolve it.
Fivetran: Fivetran REST API Failing with 404 Errors
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
We have deployed a fix for the issue causing 404 errors in the Fivetran REST API.
We will continue to monitor the service to ensure normal operation.
If you continue to experience any issues, please reach out to our Support Team.
identified
We have identified the root cause of the issue causing 404 errors in the Fivetran REST API and are actively working on a fix. We will continue to share updates as we make progress.
identified
We are continuing to investigate the root cause of the issue. Our Engineering team is actively working to identify the underlying problem and will share further updates as more information becomes available.
The team is also reviewing recent changes to determine if they may have contributed to the issue.
identified
The issue has been identified and we are working to resolve it.
3rd Party: Multiple Twitter and Twitter Ads connections are failing with "HTTP 503 Service Unavailable"
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
Many Twitter and Twitter Ads connections have recovered, and the rate of severe errors has dropped significantly over the past 2 hours.
We are still seeing intermittent 500 and 503 errors for a small subset of connections.
X (Twitter) has not yet marked the incident as resolved on their status page, and we will continue to monitor for full recovery.
https://docs.x.com/status
monitoring
A fix has been implemented and we are monitoring the results.
identified
We have reached out to the third-party to obtain the latest status on this issue and are currently awaiting their response.
Additionally, we have started observing "HTTP 500 – Internal Server Error" for a few connections.
At this time, there are no further updates available on their status page. We are continuing to closely monitor the situation and will share updates as soon as we receive more information.
identified
The third-party is still working on this incident, and there have been no further updates on their status page at this time.
We are continuing to closely monitor the situation and will keep you informed as soon as we receive any new information.
identified
The issue has been identified as being caused by a problem on the third-party side. They have also acknowledged and posted an update on their page (link below).
https://docs.x.com/status
We are closely monitoring the situation and will provide further updates as soon as more information becomes available.
identified
The issue has been identified and we are working to resolve it.
Multiple connectors under the BigQuery destination are failing with a "GCS_BG_STORAGE" error.
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
Connections syncing to BigQuery destinations are impacted due to an internal configuration error. The issue has now been resolved, and we are monitoring sync.
identified
The issue has been identified and we are working to resolve it.
Some Box Connections are failing with HTTP "429 Too Many Requests" 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
The issue has been identified and we are working to resolve it.
Some itunes_connect Connections Failing Due to Intermittent Apple App Store Connect Reporter Unavailability
minorSource not attested
Last archived state: identified
View archived record details
identified
We identified an issue with the itunes_connect Connections where sync is failing with the "Unknown failure" error.
3rd Party: Sync delays in GCP Australia Southeast1 region
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.
