bgpreport

Network · data from 2026-11-12

AS149117 VTCMOBILE-VN - VTC MOBILE SERVICES JOINT STOCK COMPANY

Registry name: VTCMOBILE-VN - VTC MOBILE SERVICES JOINT STOCK COMPANY, VN · not in PeeringDB

7IPv4 routes 71.4% RPKI valid · 71.4% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
2RPKI invalid 0 origin · 2 maxLength
1No ROA 2 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS149117, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS149117, 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.190.202.0/24 Invalid: maxLength Nonecovered by 103.190.202.0/23 8 1%low visibility 4
103.190.203.0/24 Invalid: maxLength Nonecovered by 103.190.202.0/23 8 1%low visibility 4
2001:df0:f140::/48 No ROA Other IRR onlyNTTCOM 636 100% 67
103.82.28.0/22 Valid RIR databaseAPNIC, NTTCOM 670 100% 67
103.190.202.0/23 Valid RIR databaseAPNIC, NTTCOM 670 100% 67
103.227.112.0/23 Valid RIR databaseAPNIC 670 100% 67
103.227.113.0/24 Valid RIR databaseAPNIC 670 100% 67
103.227.114.0/23 Valid RIR databaseAPNIC 670 100% 67

AS-SET

AS149117 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.

  • ROA: maxLength2
  • ROA: none1
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: maxLength103.190.202.0/24ROA 103.190.202.0/23 AS149117 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 103.190.202.0/24.8 of 673
Route object: none103.190.202.0/24No route object for it. A route object for 103.190.202.0/23 with origin AS149117 covers it (filters allowing more-specifics accept it). Add a route object with origin AS149117 in the RIR database for the space.8 of 673
ROA: maxLength103.190.203.0/24ROA 103.190.202.0/23 AS149117 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 103.190.203.0/24.8 of 673
Route object: none103.190.203.0/24No route object for it. A route object for 103.190.202.0/23 with origin AS149117 covers it (filters allowing more-specifics accept it). Add a route object with origin AS149117 in the RIR database for the space.8 of 673
ROA: none2001:df0:f140::/48No ROA covers it. Add a ROA for AS149117, maxLength 48.636 of 636
Route object: RIR2001:df0:f140::/48Route object only in NTTCOM. Add it in the RIR database for the space.636 of 636

Route objects not announced

Route objects with origin AS149117 whose prefix no peer sees AS149117 announce. Many are kept on purpose (backup routes, space announced only in some places).

103.227.112.0/22APNICValid
103.227.112.0/24APNICValid
103.227.114.0/24APNICValid
103.227.115.0/24APNICValid
2001:df0:f140::/49NTTCOMNo ROA

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.