Skip to content

Outage tracker / Criteo / In the US

Is Criteo down in the US?

Vendor reports no incidentWhat Criteo reports

Criteo reports no incident on its status page.

As of the last successful poll, 2026-11-08 17:33 UTC.

Criteo's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingin the US, measured from Ashburn and San Jose

All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Criteo at Nov 8, 2026, 6:10 PM UTC.

Over the last 24 hours we completed 272 checks from Ashburn and San Jose and 272 answered cleanly, 100.00% availability.

Of the 2 other regions we check Criteo from, all 2 read checks passing right now.

Email me when Criteo reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Criteo's own statement from its status page, with our regional reading beside it.

What our Ashburn and San Jose probes measured

AshburnChecks passing137 checks in 24h, 100.00%
San JoseChecks passing135 checks in 24h, 100.00%

Last checked Nov 8, 2026, 6:10 PM UTC.

Criteo from Ashburn and San Jose over the last 30 days

Over the last 30 days, Criteo answered our Ashburn probe in 1,502 ms on average, and 1 check in 20 took longer than 2,291 ms.

Over the last 30 days, Criteo answered our San Jose probe in 2,282 ms on average, and 1 check in 20 took longer than 3,046 ms.

Ranked by average response time across the 4 cities we check Criteo from, Ashburn 2nd, San Jose 3rd; Frankfurt was fastest at 862 ms and Tokyo slowest at 2,613 ms.

From Ashburn and San Jose we ran 1,570 checks of Criteo in 7 days, and 1,570 answered cleanly: 100.00% availability.

Every one of those days was clean: not one failed check.

In Ashburn local time (EST), Criteo was slowest around 7 AM, at 1,841 ms on average over the last 14 days, and quickest around 12 PM, at 1,208 ms.

Day (UTC)ChecksAvailabilityAverage response
Sun, Nov 8200100.00%1,820 ms
Sat, Nov 7269100.00%1,815 ms
Fri, Nov 6250100.00%2,123 ms
Thu, Nov 5252100.00%1,893 ms
Wed, Nov 4251100.00%1,598 ms
Tue, Nov 3245100.00%1,769 ms
Mon, Nov 2103100.00%2,086 ms

Criteo outages measured from the US

Our Ashburn and San Jose probes measured no confirmed Criteo outage in the last 90 days.

How the other regions read right now

Of the 2 other regions we check Criteo from, all 2 read checks passing right now.

Probe cityRight nowLast 24h
FrankfurtChecks passing100.00% of 139 checks
TokyoChecks passing100.00% of 79 checks

Other countries we check Criteo from

How we measured this

The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Criteo's public endpoints. They are not user reports, and they are not Criteo's own status page.

See Criteo's full check readings, the 90-day history by region, or the outage tracker methodology.

The US readings here are taken from that country and show the time of the last one, but Criteo has not yet accumulated enough continuous history for us to publish this page to search engines.

Check your own site from Ashburn

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter