Network · data from 2026-11-12
AS199415 YORKHOST
Registry name: YORKHOST YORKHOST SAS, FR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS199415, 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.
| 2a12:bec4:1f0::/44 | Valid | None | 635 100% |
| 217.145.72.0/24 | Valid | Other IRR onlyRADB | 653 97% |
| 62.144.48.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 79.182.29.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 141.11.234.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 145.223.4.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 82.21.200.0/24 | Valid | RIR databaseRADB, RIPE | 653 97% |
| 82.41.119.0/24 | Valid | RIR databaseRADB, RIPE | 653 97% |
| 83.150.218.0/24 | Valid | RIR databaseRADB, RIPE | 653 97% |
| 141.11.103.0/24 | Valid | RIR databaseRADB, RIPE | 653 97% |
| 193.246.5.0/24 | Valid | RIR databaseRADB, RIPE | 653 97% |
| 2a10:4646:121::/48 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
AS199415'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 3 are in fix.csv.
- Route object: none1
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a12:bec4:1f0::/44 | No route object for it. Add a route object with origin AS199415 in the RIR database for the space. |
| Route object: RIR | 217.145.72.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS199415 whose prefix no peer sees AS199415 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a13:9500:11f::/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.