Network · data from 2026-11-12
AS394474 WHITELABELCOLO393 - WhiteLabelColo
Registry name: WHITELABELCOLO393 - WhiteLabelColo, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS394474, 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.
| 212.6.51.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 191.102.128.0/21 | Valid | Nonecovered by 191.102.128.0/18 | 671 100% |
| 191.102.136.0/21 | Valid | Nonecovered by 191.102.128.0/18 | 671 100% |
| 191.102.144.0/21 | Valid | Nonecovered by 191.102.128.0/18 | 671 100% |
| 191.102.152.0/21 | Valid | Nonecovered by 191.102.128.0/18 | 671 100% |
| 191.102.160.0/20 | Valid | Nonecovered by 191.102.128.0/18 | 671 100% |
| 191.102.176.0/21 | Valid | Nonecovered by 191.102.128.0/18 | 671 100% |
| 191.102.184.0/21 | Valid | Nonecovered by 191.102.128.0/18 | 671 100% |
| 45.5.64.0/22 | Valid | RIR databaseLACNIC | 671 100% |
| 167.250.108.0/22 | Valid | RIR databaseALTDB, LACNIC | 671 100% |
| 170.244.92.0/22 | Valid | RIR databaseLACNIC | 671 100% |
| 170.254.176.0/22 | Valid | RIR databaseLACNIC | 671 100% |
AS-SET
AS394474 isn't in PeeringDB, where networks name their 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 9 are in fix.csv.
- ROA: none1
- Route object: none7
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 212.6.51.0/24 | No ROA covers it. Add a ROA for AS394474, maxLength 24. |
| Route object: none | 191.102.128.0/21 | No route object for it. A route object for 191.102.128.0/18 with origin AS394474 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394474 in the RIR database for the space. |
| Route object: none | 191.102.136.0/21 | No route object for it. A route object for 191.102.128.0/18 with origin AS394474 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394474 in the RIR database for the space. |
| Route object: none | 191.102.144.0/21 | No route object for it. A route object for 191.102.128.0/18 with origin AS394474 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394474 in the RIR database for the space. |
| Route object: none | 191.102.152.0/21 | No route object for it. A route object for 191.102.128.0/18 with origin AS394474 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394474 in the RIR database for the space. |
| Route object: none | 191.102.160.0/20 | No route object for it. A route object for 191.102.128.0/18 with origin AS394474 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394474 in the RIR database for the space. |
| Route object: none | 191.102.176.0/21 | No route object for it. A route object for 191.102.128.0/18 with origin AS394474 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394474 in the RIR database for the space. |
| Route object: none | 191.102.184.0/21 | No route object for it. A route object for 191.102.128.0/18 with origin AS394474 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394474 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS394474 whose prefix no peer sees AS394474 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 191.102.128.0/18 | LACNIC | 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.