bgpreport

Network · data from 2026-11-12

AS45552 METASERV-VN - METASERV COMPANY LIMITED

Registry name: METASERV-VN - METASERV COMPANY LIMITED, VN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45552, 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:9100::/48 No ROA Other IRR onlyNTTCOM 636 100% 69
103.20.144.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
202.43.110.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
202.43.108.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
202.43.111.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 68

AS-SET

AS45552 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 12 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none2400:9100::/48No ROA covers it. Add a ROA for AS45552, maxLength 48.636 of 636
Route object: RIR2400:9100::/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 AS45552 whose prefix no peer sees AS45552 announce. Many are kept on purpose (backup routes, space announced only in some places).

103.20.144.0/23APNIC, NTTCOM, RADBValid
103.20.144.0/24APNIC, NTTCOM, RADBValid
103.20.145.0/24APNIC, NTTCOM, RADBValid
103.20.146.0/23APNIC, NTTCOM, RADBValid
103.20.146.0/24APNIC, NTTCOM, RADBValid
103.20.147.0/24APNIC, NTTCOM, RADBValid
202.43.108.0/23APNIC, NTTCOM, RADBValid
202.43.108.0/24APNIC, NTTCOM, RADBValid
202.43.109.0/24APNIC, NTTCOM, RADBValid
202.43.110.0/23APNIC, NTTCOM, 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.