Live / Criteo / Incident
Criteo: Data Processing Delays - Reporting Tools Affected
Criteo · criteo.comMinor incidentResolved2026-10-27 04:45 UTC
Public — what happened
Summary
Criteo said its data processing systems fell behind starting at 01:58 UTC on 2026-10-26, which caused inaccurate figures in its reporting tools. The company stated that no data was lost. About two hours later, at 04:02 UTC, it said the problem had been identified and a fix was being put in place. The incident, which Criteo rated as minor, was marked resolved at 04:45 on 2026-10-27.
Affected
Analytics, Analytics
Timeline
- Started — 2026-10-26 01:58 UTC
- Investigating — 2026-10-26 01:58 UTC
- Identified — 2026-10-26 04:02 UTC
- Resolved — 2026-10-27 04:45 UTC · 26h 48m 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 45, 2026, our weekly internet health report.