3rd Party: Google Display & Video 360 connections are failing with error "Unknown Client Failure"
Incident
Report for Fivetran
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 Display & Video 360 connections, which resulted in sync failures with an "Unknown Client Failure" error.
Timeline:
This issue began on November 28, 2025, at 01:42 UTC and was resolved on November 29, 2025, at 08:43 UTC.
Cause:
This was caused by the Quota limit decreasing from 1.5k to 0.4k requests per minute for the Display & Video 360 API on the third-party side.
Resolution:
We temporarily disabled sync of all metadata tables in the Google Display & Video 360 connector. We will be working on a solution to re-enable them.
Incident Summary
Description:
We identified an issue with Google Display & Video 360 connections, which resulted in sync failures with an "Unknown Client Failure" error.
Timeline:
This issue began on November 28, 2025, at 01:42 UTC and was resolved on November 29, 2025, at 08:43 UTC.
Cause:
This was caused by the Quota limit decreasing from 1.5k to 0.4k requests per minute for the Display & Video 360 API on the third-party side.
Resolution:
We temporarily disabled sync of all metadata tables in the Google Display & Video 360 connector. We will be working on a solution to re-enable them.
Update
The latest fix has resolved the issue, and syncs are succeeding as expected. We are continuing to monitor the connections.
Update
A new fix has now been implemented, and we are currently monitoring the results.
Monitoring
A fix has been implemented and we are monitoring the results.
Update
We’ve implemented improvements to stabilize DV360 connector performance, and the fix is currently in testing. In parallel, we’re also working with the DV360 API Support team for further resolution. Connectors should run more reliably, and we’ll continue monitoring the situation closely.
Update
The issue is caused by a reduced API quota for the Display & Video 360 API on GCP. We are working to restore the quota and are also implementing improvements to better handle per-minute quota limits.
Update
We are continuing to investigate the issue
Identified
The issue has been identified and we are working to resolve it.
This incident affected: Systems (General Services).