Network · data from 2026-11-12
AS38247 VIETNAMOBILE-AS-VN - Vietnamobile Telecommunications Joint Stock Company
Registry name: VIETNAMOBILE-AS-VN - Vietnamobile Telecommunications Joint Stock Company, VN · not in PeeringDB
38IPv4 routes
100.0% RPKI valid · 100.0% with a route object
32IPv6 routes
100.0% RPKI valid · 3.1% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
31 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
48Route objects not announced
registered with origin AS38247, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS38247, 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.
| 2400:e240:8::/48 | Valid | Nonecovered by 2400:e240::/32 | 636 100% |
| 2400:e240:9::/48 | Valid | Nonecovered by 2400:e240::/32 | 636 100% |
| 2400:e240:a::/48 | Valid | Nonecovered by 2400:e240::/32 | 636 100% |
| 2400:e240:b::/48 | Valid | Nonecovered by 2400:e240::/32 | 636 100% |
| 2400:e240::/44 | Valid | Nonecovered by 2400:e240::/32 | 635 100% |
| 2400:e240:1::/48 | Valid | Nonecovered by 2400:e240::/32 | 635 100% |
| 2400:e240:2::/48 | Valid | Nonecovered by 2400:e240::/32 | 635 100% |
| 2400:e240:3::/48 | Valid | Nonecovered by 2400:e240::/32 | 635 100% |
| 2400:e240:4::/48 | Valid | Nonecovered by 2400:e240::/32 | 635 100% |
| 2400:e240:5::/48 | Valid | Nonecovered by 2400:e240::/32 | 635 100% |
| 2400:e240:6::/48 | Valid | Nonecovered by 2400:e240::/32 | 635 100% |
| 2400:e240:7::/48 | Valid | Nonecovered by 2400:e240::/32 | 635 100% |
| 2400:e240:d::/48 | Valid | Nonecovered by 2400:e240::/32 | 635 100% |
| 2400:e240:e::/48 | Valid | Nonecovered by 2400:e240::/32 | 635 100% |
| 2400:e240:f::/48 | Valid | Nonecovered by 2400:e240::/32 | 635 100% |
| 2400:e240:4000::/44 | Valid | Nonecovered by 2400:e240::/32 | 635 100% |
| 2400:e240:4001::/48 | Valid | Nonecovered by 2400:e240::/32 | 635 100% |
| 2400:e240:4002::/48 | Valid | Nonecovered by 2400:e240::/32 | 635 100% |
| 2400:e240:4003::/48 | Valid | Nonecovered by 2400:e240::/32 | 635 100% |
| 2400:e240:4004::/48 | Valid | Nonecovered by 2400:e240::/32 | 635 100% |
| 2400:e240:4005::/48 | Valid | Nonecovered by 2400:e240::/32 | 635 100% |
| 2400:e240:4006::/48 | Valid | Nonecovered by 2400:e240::/32 | 635 100% |
| 2400:e240:4007::/48 | Valid | Nonecovered by 2400:e240::/32 | 635 100% |
| 2400:e240:400d::/48 | Valid | Nonecovered by 2400:e240::/32 | 635 100% |
| 2400:e240:400e::/48 | Valid | Nonecovered by 2400:e240::/32 | 635 100% |
| 2400:e240:c000::/34 | Valid | Nonecovered by 2400:e240::/32 | 635 100% |
| 2400:e240:4008::/48 | Valid | Nonecovered by 2400:e240::/32 | 634 100% |
| 2400:e240:4009::/48 | Valid | Nonecovered by 2400:e240::/32 | 634 100% |
| 2400:e240:400a::/48 | Valid | Nonecovered by 2400:e240::/32 | 634 100% |
| 2400:e240:400b::/48 | Valid | Nonecovered by 2400:e240::/32 | 634 100% |
| 2400:e240:400c::/48 | Valid | Nonecovered by 2400:e240::/32 | 634 100% |
| 2400:e240::/48 | Valid | Other IRR onlyNTTCOM | 635 100% |
| 103.7.36.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.7.37.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.19.96.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.19.98.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.23.156.0/22 | Valid | RIR databaseAPNIC, NTTCOM | 672 100% |
| 103.23.158.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.23.159.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.129.188.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.249.20.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 202.79.232.0/21 | Valid | RIR databaseAPNIC, NTTCOM | 672 100% |
| 203.170.26.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 45.126.98.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 103.7.39.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 103.19.99.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 103.129.190.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 103.249.21.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 103.249.22.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 202.79.238.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.79.239.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 203.170.27.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 45.126.96.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 45.126.99.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 103.7.36.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 103.7.38.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 103.19.97.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 103.23.157.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 103.129.191.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 202.79.232.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 670 100% |
| 202.79.233.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 670 100% |
| 202.79.234.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 670 100% |
| 202.79.235.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 670 100% |
| 202.79.236.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 670 100% |
| 202.79.237.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 670 100% |
| 203.170.26.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 103.23.156.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 103.249.20.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 669 99% |
| 103.249.23.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 669 99% |
| 59.153.212.0/22 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
AS-SET
AS38247 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 80 are in fix.csv.
- Route object: none31
- Route object: RIR1
- Route object: not announced48
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2400:e240:8::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:9::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:a::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:b::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240::/44 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:1::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:2::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:3::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:4::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:5::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:6::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:7::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:d::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:e::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:f::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:4000::/44 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:4001::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:4002::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:4003::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:4004::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:4005::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:4006::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:4007::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:400d::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:400e::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:c000::/34 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:4008::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:4009::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:400a::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:400b::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: none | 2400:e240:400c::/48 | No route object for it. A route object for 2400:e240::/32 with origin AS38247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38247 in the RIR database for the space. |
| Route object: RIR | 2400:e240::/48 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38247 whose prefix no peer sees AS38247 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.126.96.0/23 | APNIC, NTTCOM, RADB | Valid |
| 45.126.96.0/24 | APNIC, NTTCOM, RADB | Valid |
| 45.126.97.0/24 | APNIC, NTTCOM, RADB | Valid |
| 45.126.98.0/23 | APNIC, NTTCOM, RADB | Valid |
| 59.153.212.0/23 | APNIC | Valid |
| 59.153.212.0/24 | APNIC | Valid |
| 59.153.213.0/24 | APNIC | Valid |
| 59.153.214.0/23 | APNIC | Valid |
| 59.153.214.0/24 | APNIC | Valid |
| 59.153.215.0/24 | APNIC | Valid |
| 103.7.36.0/23 | APNIC, NTTCOM, RADB | Valid |
| 103.7.38.0/23 | APNIC, NTTCOM, RADB | Valid |
| 103.19.96.0/23 | APNIC, NTTCOM, RADB | Valid |
| 103.19.96.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.19.98.0/23 | APNIC, NTTCOM, RADB | Valid |
| 103.23.156.0/23 | APNIC | Valid |
| 103.23.158.0/23 | APNIC | Valid |
| 103.129.188.0/22 | APNIC, NTTCOM, RADB | Valid |
| 103.129.188.0/23 | APNIC, NTTCOM, RADB | Valid |
| 103.129.189.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.129.190.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.249.20.0/23 | APNIC, NTTCOM, RADB | Valid |
| 103.249.22.0/23 | APNIC, NTTCOM, RADB | Valid |
| 202.79.232.0/22 | APNIC | Valid |
| 202.79.232.0/23 | APNIC | Valid |
| 202.79.234.0/23 | APNIC | Valid |
| 202.79.236.0/22 | APNIC | Valid |
| 202.79.236.0/23 | APNIC | Valid |
| 202.79.238.0/23 | APNIC | Valid |
| 202.172.4.0/23 | NTTCOM, RADB | No ROA |
| 202.172.4.0/24 | NTTCOM, RADB | No ROA |
| 202.172.5.0/24 | NTTCOM, RADB | No ROA |
| 203.160.96.0/21 | APNIC | Valid |
| 203.160.96.0/22 | APNIC | Valid |
| 203.160.96.0/23 | APNIC | Valid |
| 203.160.96.0/24 | APNIC | Valid |
| 203.160.97.0/24 | APNIC | Valid |
| 203.160.98.0/23 | APNIC | Valid |
| 203.160.98.0/24 | APNIC | Valid |
| 203.160.99.0/24 | APNIC | Valid |
| 203.160.100.0/22 | APNIC | Valid |
| 203.160.100.0/23 | APNIC | Valid |
| 203.160.100.0/24 | APNIC | Valid |
| 203.160.101.0/24 | APNIC | Valid |
| 203.160.102.0/23 | APNIC | Valid |
| 203.160.102.0/24 | APNIC | Valid |
| 203.160.103.0/24 | APNIC | Valid |
| 2400:e240::/32 | APNIC, NTTCOM | 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.