Network · data from 2026-11-12
AS200435 Titan Datacenters France
Registry name: AS_DTHTDC Titan DataCenters France SAS, FR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS200435, 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.
| 154.41.73.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 185.63.172.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.63.173.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.63.174.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.63.175.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.248.50.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 213.225.239.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 46.37.120.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 2a04:f600:4454::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:f600:4455::/48 | Valid | RIR databaseRIPE | 605 95% |
AS-SET
AS200435's PeeringDB record names no AS-SET.
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 6 are in fix.csv.
- ROA: none1
- Route object: RIR1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 154.41.73.0/24 | No ROA covers it. Add a ROA for AS200435, maxLength 24. |
| Route object: RIR | 154.41.73.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS200435 whose prefix no peer sees AS200435 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 94.143.225.0/24 | RADB, RIPE | Valid |
| 185.63.172.0/22 | RIPE | Valid |
| 2a04:f600::/29 | RIPE | Valid |
| 2a04:f600:4456::/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.