bgpreport

Network · data from 2026-11-12

AS63641 MVNET - Mega Vantage Information Consulting Co., Ltd.

Registry name: MVNET - Mega Vantage Information Consulting Co., Ltd., CN · not in PeeringDB

17IPv4 routes 100.0% RPKI valid · 52.9% with a route object
3IPv6 routes 100.0% RPKI valid · 33.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 10 with no route object for this origin
16Low visibility seen by under 10% of full-table peers
7Route objects not announced registered with origin AS63641, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS63641, 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.

123.49.231.0/24 Valid None 105 16% 44
2405:6c0:2::/48 Valid None 60 9%low visibility 37
2405:6c0:4::/48 Valid None 60 9%low visibility 37
123.49.232.0/24 Valid None 7 1%low visibility 6
123.49.237.0/24 Valid Other origin only 4 1%low visibility 7
123.49.238.0/24 Valid Other origin only 4 1%low visibility 7
123.49.239.0/24 Valid Other origin only 4 1%low visibility 7
123.49.244.0/24 Valid Other origin only 1 0%low visibility 4
123.49.246.0/24 Valid Other origin only 1 0%low visibility 4
123.49.247.0/24 Valid Other origin only 1 0%low visibility 4
123.49.243.0/24 Valid Other IRR onlyNTTCOM, RADB 106 16% 41
123.49.240.0/24 Valid Other IRR onlyNTTCOM, RADB 103 15% 41
123.49.242.0/24 Valid Other IRR onlyNTTCOM, RADB 103 15% 41
2405:6c0:1::/48 Valid Other IRR onlyRADB 30 5%low visibility 16
123.49.194.0/24 Valid Other IRR onlyRADB 27 4%low visibility 16
103.74.124.0/24 Valid Other IRR onlyRADB 4 1%low visibility 7
103.74.127.0/24 Valid Other IRR onlyNTTCOM, RADB 4 1%low visibility 7
123.49.196.0/24 Valid Other IRR onlyRADB 4 1%low visibility 7
103.74.125.0/24 Valid Other IRR onlyRADB 1 0%low visibility 4
103.74.126.0/24 Valid Other IRR onlyRADB 1 0%low visibility 4

AS-SET

AS63641 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 27 are in fix.csv.

  • Route object: none10
  • Route object: RIR10
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
Route object: none123.49.231.0/24No route object for it. Add a route object with origin AS63641 in the RIR database for the space.105 of 673
Route object: none2405:6c0:2::/48No route object for it. Add a route object with origin AS63641 in the RIR database for the space.60 of 636
Route object: none2405:6c0:4::/48No route object for it. Add a route object with origin AS63641 in the RIR database for the space.60 of 636
Route object: none123.49.232.0/24No route object for it. Add a route object with origin AS63641 in the RIR database for the space.7 of 673
Route object: none123.49.237.0/24Route objects for it name AS4515. Add a route object with origin AS63641 in the RIR database for the space.4 of 673
Route object: none123.49.238.0/24Route objects for it name AS4515. Add a route object with origin AS63641 in the RIR database for the space.4 of 673
Route object: none123.49.239.0/24Route objects for it name AS4515. Add a route object with origin AS63641 in the RIR database for the space.4 of 673
Route object: none123.49.244.0/24Route objects for it name AS4515. Add a route object with origin AS63641 in the RIR database for the space.1 of 673
Route object: none123.49.246.0/24Route objects for it name AS4515. Add a route object with origin AS63641 in the RIR database for the space.1 of 673
Route object: none123.49.247.0/24Route objects for it name AS4515. Add a route object with origin AS63641 in the RIR database for the space.1 of 673
Route object: RIR123.49.243.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.106 of 673
Route object: RIR123.49.240.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.103 of 673
Route object: RIR123.49.242.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.103 of 673
Route object: RIR2405:6c0:1::/48Route object only in RADB. Add it in the RIR database for the space.30 of 636
Route object: RIR123.49.194.0/24Route object only in RADB. Add it in the RIR database for the space.27 of 673
Route object: RIR103.74.124.0/24Route object only in RADB. Add it in the RIR database for the space.4 of 673
Route object: RIR103.74.127.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.4 of 673
Route object: RIR123.49.196.0/24Route object only in RADB. Add it in the RIR database for the space.4 of 673
Route object: RIR103.74.125.0/24Route object only in RADB. Add it in the RIR database for the space.1 of 673
Route object: RIR103.74.126.0/24Route object only in RADB. Add it in the RIR database for the space.1 of 673

Route objects not announced

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

123.49.193.0/24RADBValid
123.49.195.0/24RADBValid
123.49.224.0/24RADBValid
123.49.225.0/24RADBValid
123.49.226.0/24RADBValid
123.49.227.0/24RADBValid
123.49.241.0/24NTTCOM, RADBValid

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.