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

As listed on Criteo’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the Criteo status & history page.

Related: Criteo status & history. SquidGrid is not affiliated with Criteo.