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.
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.
