Network · data from 2026-11-12

AS45542 VNU-AS-VN - VietNam National University Ha Noi

Registry name: VNU-AS-VN - VietNam National University Ha Noi, VN · not in PeeringDB

14IPv4 routes 100.0% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

17Route objects not announced registered with origin AS45542, seen from no peer

Announced routes

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


112.137.128.0/20	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	66
112.137.128.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	66
112.137.129.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	66
112.137.130.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	66
112.137.132.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	66
112.137.133.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	66
112.137.134.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	66
112.137.135.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	66
112.137.136.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	66
112.137.137.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	66
112.137.138.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	66
112.137.139.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	66
112.137.140.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	66
112.137.142.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	66

AS-SET

AS45542 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 17 are in fix.csv.

Route object: not announced17

Route objects not announced

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


112.137.128.0/21	APNIC, NTTCOM, RADB	Valid
112.137.128.0/22	APNIC, NTTCOM, RADB	Valid
112.137.128.0/23	APNIC, NTTCOM, RADB	Valid
112.137.130.0/23	APNIC, NTTCOM, RADB	Valid
112.137.131.0/24	APNIC, RADB	Valid
112.137.132.0/22	APNIC, NTTCOM, RADB	Valid
112.137.132.0/23	APNIC, NTTCOM, RADB	Valid
112.137.134.0/23	APNIC, NTTCOM, RADB	Valid
112.137.136.0/21	APNIC, NTTCOM, RADB	Valid
112.137.136.0/22	APNIC, NTTCOM, RADB	Valid
112.137.136.0/23	APNIC, NTTCOM, RADB	Valid
112.137.138.0/23	APNIC, NTTCOM, RADB	Valid
112.137.140.0/22	APNIC, NTTCOM, RADB	Valid
112.137.140.0/23	APNIC, NTTCOM, RADB	Valid
112.137.141.0/24	APNIC, RADB	Valid
112.137.142.0/23	APNIC, NTTCOM, RADB	Valid
112.137.143.0/24	APNIC, RADB	Valid

112.137.128.0/21

APNIC, NTTCOM, RADB

Valid

112.137.128.0/22

APNIC, NTTCOM, RADB

Valid

112.137.128.0/23

APNIC, NTTCOM, RADB

Valid

112.137.130.0/23

APNIC, NTTCOM, RADB

Valid

112.137.131.0/24

APNIC, RADB

Valid

112.137.132.0/22

APNIC, NTTCOM, RADB

Valid

112.137.132.0/23

APNIC, NTTCOM, RADB

Valid

112.137.134.0/23

APNIC, NTTCOM, RADB

Valid

112.137.136.0/21

APNIC, NTTCOM, RADB

Valid

112.137.136.0/22

APNIC, NTTCOM, RADB

Valid

112.137.136.0/23

APNIC, NTTCOM, RADB

Valid

112.137.138.0/23

APNIC, NTTCOM, RADB

Valid

112.137.140.0/22

APNIC, NTTCOM, RADB

Valid

112.137.140.0/23

APNIC, NTTCOM, RADB

Valid

112.137.141.0/24

APNIC, RADB

Valid

112.137.142.0/23

APNIC, NTTCOM, RADB

Valid

112.137.143.0/24

APNIC, RADB

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.