Network · data from 2026-11-12
AS63730 VNSO TECHNOLOGY JOINT STOCK COMPANY
Registry name: VNSO-VN - VNSO TECHNOLOGY JOINT STOCK COMPANY, VN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS63730, 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.
| 2405:e0c0::/48 | No ROA | RIR databaseAPNIC, NTTCOM | 636 100% |
| 103.9.156.0/22 | Valid | RIR databaseAPNIC, NTTCOM | 672 100% |
| 103.168.36.0/23 | Valid | RIR databaseAPNIC, NTTCOM | 672 100% |
| 103.185.184.0/23 | Valid | RIR databaseAPNIC, NTTCOM | 672 100% |
AS-SET
AS63730'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 7 are in fix.csv.
- ROA: none1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2405:e0c0::/48 | No ROA covers it. Add a ROA for AS63730, maxLength 48. |
Route objects not announced
Route objects with origin AS63730 whose prefix no peer sees AS63730 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.161.174.0/23 | NTTCOM, RADB | No ROA |
| 103.161.174.0/24 | NTTCOM | No ROA |
| 103.161.175.0/24 | NTTCOM | No ROA |
| 103.185.184.0/24 | APNIC, NTTCOM | Valid |
| 103.185.185.0/24 | APNIC, NTTCOM | Valid |
| 2400:69e0::/48 | APNIC | 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.