Fivetran: A few Google Ads connector syncs are unable to ingest complete data for some reports
View the provider incident record →Current answer
Fivetran experienced a minor incident: Fivetran: A few Google Ads connector syncs are unable to ingest complete data for some reports. Resolved on Oct 3, 2026.
The notice publication date does not establish the outage start. Provider resolved: .
Looking for an update now? Check the current status, or follow Fivetran for future changes.
Provider notice timeline
Affected Components
Google Ads
Incident Timeline
Resolved
This incident has been resolved. We have observed that instance rates are returning to normal levels and affected connectors are completing syncs successfully.
Incident Summary
Description:
We identified an issue with the Google Ads connector, which resulted in syncs failing to ingest complete data for some reports due to a RESOURCE_EXHAUSTED (gRPC message exceeds maximum size) error.
Timeline:
This issue began on October 2 at approximately 4:30 PM UTC and was resolved on October 3 at 7:45 PM UTC.
Cause:
A recent update to our system accidentally lowered the limit on the size of data batches we can receive at one time. Because of this, our system began rejecting larger data responses coming from Google Ads.
Resolution:
We released a quick fix to restore the data limit back to its normal, higher capacity. We have closely monitored the affected connections and confirmed that data is now syncing completely and normally. Any previously skipped data has automatically caught up, and no manual action is required on your part.
Incident Summary
Description:
We identified an issue with the Google Ads connector, which resulted in syncs failing to ingest complete data for some reports due to a RESOURCE_EXHAUSTED (gRPC message exceeds maximum size) error.
Timeline:
This issue began on October 2 at approximately 4:30 PM UTC and was resolved on October 3 at 7:45 PM UTC.
Cause:
A recent update to our system accidentally lowered the limit on the size of data batches we can receive at one time. Because of this, our system began rejecting larger data responses coming from Google Ads.
Resolution:
We released a quick fix to restore the data limit back to its normal, higher capacity. We have closely monitored the affected connections and confirmed that data is now syncing completely and normally. Any previously skipped data has automatically caught up, and no manual action is required on your part.
Oct 3, 2026 at 9:51 PM UTC
Monitoring
We have deployed a fix for this gRPC message size issue and are seeing the previously skipped reports catch up.
We will continue to monitor all affected connectors until they resume their normal sync functionality.
Next Expected Update: 3 hours
We will continue to monitor all affected connectors until they resume their normal sync functionality.
Next Expected Update: 3 hours
Oct 3, 2026 at 7:58 PM UTC
Identified
A fix for the gRPC message size issue affecting Google Ads connectors has been raised and is currently being reviewed by our team. Once approved, we will deploy the fix and monitor sync stability.
Next Expected Update: 1 hour
Next Expected Update: 1 hour
Oct 3, 2026 at 6:24 PM UTC
Identified
We have identified that this issue was caused by a recent code change on our end and we are currently working on a fix.
Next Expected Update: 1 hour
Next Expected Update: 1 hour
Oct 3, 2026 at 5:15 PM UTC
Identified
We have identified an issue where Google Ads connectors are experiencing an issue, causing the syncs to be unable to ingest complete data for some reports.
Logs show the "RESOURCE_EXHAUSTED, Fault: gRPC message exceeds maximum size 4194304." messages.
We are currently investigating in more detail.
Next Expected Update: 1 hour
Logs show the "RESOURCE_EXHAUSTED, Fault: gRPC message exceeds maximum size 4194304." messages.
We are currently investigating in more detail.
Next Expected Update: 1 hour
Oct 3, 2026 at 5:13 PM UTC
Identified
The issue has been identified and we are working to resolve it.
Oct 3, 2026 at 5:10 PM UTC
Was your business affected by this Fivetran outage?
Follow Fivetran and route available status alerts to email or a team channel.