Live / Criteo / Incident
Criteo: Users may have trouble accessing Commerce Max - API component
Criteo · criteo.comMinor incidentResolved2026-10-13 19:07 UTC
Public — what happened
Summary
Criteo reported a minor incident in which some users might have been unable to reach the API component of its Commerce Max product, beginning at 15:42 UTC on October 13, 2026. The company posted two updates saying it was looking into the problem but did not share a cause. The incident was marked resolved at 19:07 the same day.
Affected
Campaigns, Campaigns, Campaigns, Campaign, Analytics, Analytics, Analytics, Analytics, Audiences, Audiences, Audiences, Audiences, Catalog, Catalog, Product Catalog, Creative library, Gateway, Account Management, Billing, Gateway, OneTag - Event Tracking, Account Settings, Advertiser, Creatives and 14 more
Timeline
- Started — 2026-10-13 15:42 UTC
- Investigating — 2026-10-13 15:42 UTC (2 updates)
- Resolved — 2026-10-13 19:07 UTC · 3h 24m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Criteo against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Criteo: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Criteo report →
More from Criteo
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.