Network · data from 2026-11-12
AS135912 VNETWORK JOINT STOCK COMPANY
Registry name: VNETWORK-AS-VN - VNETWORK Joint Stock Company, VN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS135912, 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.90.221.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 2405:f540:1::/48 | No ROA | Other IRR onlyNTTCOM | 636 100% |
| 103.90.223.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 160.19.159.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.183.109.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.162.93.0/24 | Valid | RIR databaseAPNIC | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS135912: AS-135912. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS135912 isn't in the set, or no route object for AS135912 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS135912 in it | Not covered |
|---|---|---|---|---|---|
| AS-135912 | RADB | 1 | 1 | Yes | 0 |
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: none2
- Route object: RIR2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.90.221.0/24 | No ROA covers it. Add a ROA for AS135912, maxLength 24. |
| Route object: RIR | 103.90.221.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 2405:f540:1::/48 | No ROA covers it. Add a ROA for AS135912, maxLength 48. |
| Route object: RIR | 2405:f540:1::/48 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS135912 whose prefix no peer sees AS135912 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.90.220.0/22 | NTTCOM | No ROA |
| 103.90.222.0/24 | NTTCOM | No ROA |
| 2401:9ee0::/48 | RADB | No ROA |
| 2405:f540:9::/48 | APNIC | Valid |
| 2405:f540:a::/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.