3rd Party: Some Criteo Connection Syncs Failing Due to "HTTP 500 Internal Server Error"

This incident has been resolved. The fix for the "HTTP 401 Unauthorized" has been deployed. We have observed that instance rates returned to normal levels, and affected connectors are syncing successfully

Incident Summary

Description:
We identified an issue for Criteo, which resulted in syncs failing with a 500 Internal Server and 401 Unauthorized error.

Timeline:
This issue began on 2025-07-21 at 02:04 PM UTC and was resolved on 2025-07-22 at 12:44 AM UTC.

Cause:
The issue occurred from the source (Criteo) API endpoint, causing 500 and 401 errors

Resolution:
1. For 500 Internal Server error, we have deployed a fix to skip the problematic advertiser IDs
2. For 401 Unauthorized error, we have deployed a fix to lower the number of retries

The fix has been deployed and connectors are no longer failing with "Error: HTTP 500 Internal Server Error".

We have found a few instance still failing with "HTTP 401 Unauthorized" and a solution is currently being deployed.

We are currently skipping the problematic advertiser IDs that were causing 500 Internal Server Errors in the Creatives API to ensure successful syncs. A fix has been deployed, and we are monitoring the connectors.

Criteo API is currently returning an HTTP 500 Internal Server Error when accessing the Creatives API endpoints for certain advertisers

The issue has been identified and we are working to resolve it.