Network · data from 2026-11-12
AS42210 HOSTVIRTUAL-AS NetActuate Inc
Registry name: HOSTVIRTUAL-AS NetActuate Inc, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS42210, 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.
| 148.163.213.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 45.54.13.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 2400:a1c0:64::/48 | Valid | Other IRR onlyRADB | 634 100% |
| 2607:f740:e021::/48 | Valid | Other IRR onlyRADB | 632 99% |
AS-SET
AS42210 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 11 are in fix.csv.
- Route object: RIR4
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 148.163.213.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.54.13.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2400:a1c0:64::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2607:f740:e021::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS42210 whose prefix no peer sees AS42210 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a00:dd80::/32 | RIPE | No ROA |
| 2a00:dd80:3a::/48 | RIPE | Invalid: origin |
| 2a00:dd80:3b::/48 | RIPE | Invalid: origin |
| 2a00:dd80:3c::/48 | RIPE | Invalid: origin |
| 2a00:dd80:3d::/48 | RIPE | No ROA |
| 2a00:dd80:3e::/48 | RIPE | Invalid: origin |
| 2a00:dd80:3f::/48 | RIPE | Invalid: origin |
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.