Network · data from 2026-11-12
AS147002 VMSHELL-AS-AP - VMShell Inc.
Registry name: VMSHELL-AS-AP - VMShell Inc., HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS147002, 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.
| 103.235.18.0/24 | Valid | Other origin only | 648 96% |
AS-SET
AS147002 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 6 are in fix.csv.
- Route object: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 103.235.18.0/24 | Route objects for it name AS40065. Add a route object with origin AS147002 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS147002 whose prefix no peer sees AS147002 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.173.216.0/24 | ARIN | Valid |
| 103.20.222.0/24 | APNIC | Valid |
| 103.172.134.0/24 | APNIC | Valid |
| 2407:d340::/32 | APNIC | Valid |
| 2407:d340:7121::/48 | ALTDB | Invalid: maxLength |
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.