bgpreport

Network · data from 2026-11-12

AS55649 METRONET-HK - Flat C, 16/F, Skyline Tower,

Registry name: METRONET-HK - Flat C, 16/F, Skyline Tower,, HK · not in PeeringDB

26IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
55Route objects not announced registered with origin AS55649, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS55649, 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.
43.242.140.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
43.242.140.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
43.242.141.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
43.242.142.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
43.242.143.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.38.28.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.38.28.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.38.29.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.38.30.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.38.31.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.215.40.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.215.41.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.215.42.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.215.43.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
144.48.216.0/22 Valid RIR databaseAPNIC, NTTCOM 673 100% 67
144.48.216.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 67
144.48.217.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
144.48.218.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
144.48.219.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
202.70.162.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
202.70.174.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
223.255.240.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
223.255.240.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
223.255.241.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
223.255.242.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
223.255.243.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
2001:df0:a300::/48 Valid RIR databaseAPNIC 635 100% 68

AS-SET

AS55649 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 55 are in fix.csv.

  • Route object: not announced55

Route objects not announced

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

39.109.120.0/21RADBNo ROA
39.109.120.0/22RADBNo ROA
39.109.122.0/24NTTCOM, RADBNo ROA
39.109.123.0/24NTTCOM, RADBNo ROA
39.109.124.0/24RADBNo ROA
39.109.125.0/24RADBNo ROA
39.109.126.0/24RADBNo ROA
39.109.127.0/24RADBNo ROA
103.92.129.0/24RADBNo ROA
103.215.40.0/23APNIC, NTTCOM, RADBValid
103.215.40.0/24APNIC, NTTCOM, RADBValid
103.215.42.0/23APNIC, NTTCOM, RADBValid
103.251.36.0/22RADBNo ROA
118.103.240.0/21RADBNo ROA
118.103.241.0/24RADBNo ROA
118.103.242.0/24RADBNo ROA
118.103.243.0/24RADBNo ROA
118.103.244.0/24NTTCOM, RADBNo ROA
118.103.245.0/24RADBNo ROA
123.58.92.0/22RADBNo ROA
144.48.216.0/23APNIC, NTTCOM, RADBValid
144.48.218.0/23APNIC, NTTCOM, RADBValid
150.242.228.0/22RADBNo ROA
202.70.160.0/20APNIC, NTTCOM, RADBValid
202.70.160.0/21APNICValid
202.70.160.0/22APNICValid
202.70.160.0/23APNICValid
202.70.160.0/24APNIC, RADBValid
202.70.161.0/24APNIC, RADBValid
202.70.162.0/23APNICValid
202.70.163.0/24APNIC, RADBValid
202.70.164.0/22APNICValid
202.70.164.0/23APNICValid
202.70.164.0/24APNIC, RADBValid
202.70.165.0/24APNIC, RADBValid
202.70.166.0/23APNICValid
202.70.166.0/24APNIC, RADBValid
202.70.167.0/24APNIC, RADBValid
202.70.168.0/21APNICValid
202.70.168.0/22APNICValid
202.70.168.0/23APNICValid
202.70.168.0/24APNIC, RADBValid
202.70.169.0/24APNIC, RADBValid
202.70.170.0/23APNICValid
202.70.170.0/24APNIC, RADBValid
202.70.171.0/24APNIC, RADBValid
202.70.172.0/22APNICValid
202.70.172.0/23APNICValid
202.70.172.0/24APNIC, RADBValid
202.70.173.0/24APNIC, RADBValid
202.70.174.0/23APNICValid
202.70.175.0/24APNIC, RADBValid
202.181.145.0/24RADBNo ROA
223.255.240.0/23APNIC, NTTCOM, RADBValid
223.255.242.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.