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