Provider resolved: . The notice publication date does not establish the outage start.
Tiktok 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 TikTok Connectors which resulted in syncs failing with an "Invalid Parameter" error.
Timeline:
This issue began on 2026-08-31 at 14:00:00 UTC and was resolved on 2026-09-01 at 16:30 UTC.
Cause:
TikTok's Marketing API started rejecting requests that combine the country_code dimension with the billed_cost metric in GMV Max ads reports. Since all those errors were unexpected, it caused the syncs to fail.
Resolution:
Our team deployed a fix to update the code, enabling it to detect conflicts between metrics and dimensions. The connector now smoothly skips the problematic report table for each advertiser and logs a UI warning, ensuring the rest of the sync process finishes without issues.
monitoring
We have deployed a fix to handle the errors originating from the third-party TikTok Ads service.
We will continue monitoring all affected connectors to ensure they resume normal sync functionality.
Next Expected Update: 3 hours
identified
Our team has created a fix for this issue and is currently working on deploying it to resolve the failures.
Next Expected Update: 1 hour
identified
Our team is continuing to work on a fix for the third-party issue affecting TikTok Ads connections.
Next expected update: 1 hour.
identified
TikTok API is currently returning errors for the gmv_advertiser_country_report_daily and gmv_campaign_country_report_daily report APIs.
We have identified the issue, and we are currently working on a fix.
Next Expected Update: 1 hour
3rd Party: YouTube Analytics — sync failures caused by a YouTube API change
Provider resolved: . The notice publication date does not establish the outage start.
YouTube Analytics
resolved
The additional hotfix has been deployed and we are noticing connections being recovered.
We'll continue to monitor the remaining affected connections and will provide an update on the resolution within the next hour.
monitoring
Most connections have recovered post the fix deployment that incorporates the recent changes made to the additional thumbnail quality level returned by YouTube's Data API.
We are working on an additional fix to handle type casting for any remaining affected connections for complete resolution.
Next Update: 4 PM UTC, Aug 28
identified
We are aware of an issue affecting YouTube Analytics connections.
Affected connections may show sync failures, or syncs that are delayed or rescheduled rather than completing.
Our engineering team is actively investigating.
No action is required on your side. We will provide a further update as soon as we have more information.
Fivetran: OpenAI connections failing with 429 rate limit errors for the newly added cost_api_key table
Provider resolved: . The notice publication date does not establish the outage start.
OpenAI
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:
OpenAI connections failed with 429 rate limit errors for the newly added cost_api_key table.
Timeline:
This issue began on 25 August at around 10:30 AM UTC and was resolved on 26 August at around 2:30 AM UTC.
Cause:
The issue was caused by API rate limiting affecting syncs for the newly added cost_api_key table.
Resolution:
After the fix was deployed to address the rate-limiting behaviour, the affected connections began recovering, and syncs resumed successfully.
monitoring
The fix has been deployed. We will continue to monitor all affected connectors until they resume their normal sync functionality.
identified
We have identified an issue causing some syncs to fail due to API rate limiting.We have prepared a fix and it is awaiting deployment. Once deployed, the affected connections should begin recovering. We will continue to provide updates as deployment progresses.
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.
Tiktok 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 TikTok Connectors which resulted in syncs failing with a "Server error", "Adgroup does not exist", or "Invalid Value: no permission to access this ad or id not exist." error.
Timeline:
This issue began on 2026-08-11 at 08:00:00 UTC and was resolved on 2026-08-11 at 18:00:00 UTC.
Cause:
For some advertisers, TikTok API started unexpected responses like "Server error", "Adgroup does not exist", or "Invalid Value: no permission to access this ad or id not exist." Since all those errors were unexpected, it caused the syncs to fail. Only metadata endpoints were affected. Ad, smart plus ad and ad group endpoints.
Resolution:
The resolution was a metadata skip + a customer warning on all those endpoints. The TikTok service should now identify and skip all unknown errors with metadata, leading to a sync completion.
monitoring
We have deployed a fix to handle the errors originating from the third-party TikTok Ads service.
We will continue monitoring all affected connectors to ensure they resume normal sync functionality.
Next expected update: Within 3 hours.
identified
Our team is working on deploying the fix to resolve the issue.
Next expected update: 1 hour.
identified
Our team is continuing to work on resolving the third-party issue affecting TikTok Ads connections.
Next expected update: 1 hour.
identified
Our team continues to work on a fix for the third-party issue affecting TikTok Ads connections.
Next expected update: 1 hour.
identified
We have identified that this issue was caused by the 3rd party, and we are currently working on a fix.
Next Expected Update: 1 hour
identified
The issue has been identified and we are working to resolve it.
Fivetran: Some Google Search Console, Google Campaign Manager and Google Ad Manager Connections Fail With Reauthorize OAuth Access Error
Provider resolved: . The notice publication date does not establish the outage start.
Google Search Ads 360Google Campaign Manager 360Google Ad Manager
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 Search Console, Google Campaign Manager and Google Ad Manager Connectors which resulted in syncs failing with a Reauthorize OAuth Access Error
Timeline:
This issue began on 2026-08-10 at 15:27:32 UTC and was resolved on 2026-08-10 at 22:08:01 UTC.
Cause:
A routine maintenance change caused an issue with a shared OAuth authentication component used by Fivetran for Google-based connectors. As a result, authentication requests failed.
Resolution:
Our Engineering team has now restored the affected authentication component, and the fix has been successfully deployed.
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.
3rd Party: YouTube Analytics connections are getting rescheduled with "Daily request quota exceeded" error
Provider resolved: . The notice publication date does not establish the outage start.
YouTube Analytics
resolved
This incident has been resolved. We have observed that instance rates are returning to normal levels, and affected connections are syncing successfully.
Incident Summary
Description:
We identified an issue affecting YouTube Analytics connections that caused connections to be rescheduled with a “Daily request quota exceeded” error. The issue also caused setup tests to fail.
Timeline:
This issue began on 2026-08-03 18:05 UTC and was resolved on 2026-08-11 20:41 UTC.
Cause:
Google reduced the YouTube API quota, causing YouTube Analytics connections to be rescheduled and setup tests to fail. The impact was limited to metadata tables and setup tests; reporting tables continued to sync as expected.
Resolution:
Google has increased the YouTube API quota limit, resolving the connection rescheduling issue. Additionally, Fivetran deployed a fix that allows setup tests to pass when API quota issues occur, resolving the setup test failures.
monitoring
We are continuing to monitor
Next Expected Update: 3 hours
monitoring
Google has increased the YouTube API quota limit, and syncs are recovering.
We will continue to monitor the results.
Next Expected Update: 3 hours
monitoring
A fix has been deployed for the setup test failures, and the tests are now passing.
We continue to encounter the API quota exceeded error from Google and await their response regarding a potential resolution.
Next Expected Update: Aug 12, 2026
monitoring
We are continuing to work on the fix for the setup test failures and are awaiting a response from Google regarding increasing the YouTube API Quota.
Next Expected Update: Aug 11, 2026
monitoring
A fix has been implemented and we are monitoring the results.
identified
We have followed up with Google Support and are awaiting a response regarding the resolution of the issue.
We are also working on fixing the failures on the setup tests and will provide another update as we make progress.
Next Expected Update: 3 hours
identified
We are awaiting an update from Google Support regarding the request to increase the YouTube API Quota.
We will follow up on the same and provide the next steps as we hear further.
Next Expected Update: 3 hours
identified
Google has reduced the YouTube API quota, causing YouTube Analytics connections to be rescheduled and setup tests to fail. The impact is limited to metadata tables and setup tests; reporting tables continue to sync as expected.
We have contacted Google Support requesting an increase to the quota, and their team is currently reviewing our request.
We are actively monitoring the situation and will provide another update as we make progress.
Next Expected Update: 1 hour
identified
The issue has been identified and we are working to resolve it.
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.
