Network · data from 2026-11-12
AS44788 Criteo Europe
Registry name: ASN-CRITEO-EUROPE Criteo Technology SAS, FR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS44788, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 2001:978:1d05::/48 | Valid | Other IRR onlyRADB | 605 95% |
| 2001:978:1d06::/48 | Valid | Other IRR onlyRADB | 605 95% |
| 2001:978:3c0d::/48 | Valid | Other IRR onlyRADB | 605 95% |
| 2001:978:3c0e::/48 | Valid | Other IRR onlyRADB | 605 95% |
| 178.250.1.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.250.7.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.235.84.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.235.85.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a02:2638:2::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:2638:3::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:2638:4::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:2638:7::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:2638:b::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:2638:d::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a02:2638:12::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a02:2638:13::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a02:2638:5::/48 | Valid | RIR databaseRIPE | 605 95% |
| 2a02:2638:6::/48 | Valid | RIR databaseRIPE | 605 95% |
| 91.199.242.0/24 | Valid | RIR databaseRIPE | 363 54% |
| 91.212.98.0/24 | Valid | RIR databaseRIPE | 363 54% |
AS-SET
PeeringDB's irr_as_set for AS44788: RIPE::AS-CRITEO-EU. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS44788 isn't in the set, or no route object for AS44788 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS44788 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-CRITEO-EU | RIPE | 1 | 1 | Yes | 0 |
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 25 are in fix.csv.
- Route object: RIR4
- Route object: not announced21
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 2001:978:1d05::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2001:978:1d06::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2001:978:3c0d::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2001:978:3c0e::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS44788 whose prefix no peer sees AS44788 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 178.250.0.0/21 | RIPE | Valid |
| 178.250.0.0/22 | RIPE | Valid |
| 178.250.2.0/24 | RIPE | Valid |
| 178.250.3.0/24 | RIPE | Valid |
| 178.250.4.0/24 | RIPE | Valid |
| 178.250.5.0/24 | RIPE | Valid |
| 178.250.6.0/24 | RIPE | Valid |
| 185.235.84.0/22 | RIPE | No ROA |
| 185.235.86.0/24 | RIPE | Valid |
| 185.235.87.0/24 | RIPE | Valid |
| 2a02:2638::/32 | RIPE | Valid |
| 2a02:2638::/48 | RIPE | Valid |
| 2a02:2638:1::/48 | RIPE | Valid |
| 2a02:2638:8::/48 | RIPE | Valid |
| 2a02:2638:9::/48 | RIPE | Valid |
| 2a02:2638:a::/48 | RIPE | Valid |
| 2a02:2638:c::/48 | RIPE | Valid |
| 2a02:2638:e::/48 | RIPE | Valid |
| 2a02:2638:f::/48 | RIPE | Valid |
| 2a02:2638:10::/48 | RIPE | Valid |
| 2a02:2638:11::/48 | RIPE | Valid |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.