bgpreport

Network · data from 2026-11-12

AS55350 Virtual Switching Consultancy Limited

Registry name: VSCGT-HK - Virtual Switching Consultancy Limited (C/O VXRoutes Ltd), HK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55350, 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.
2401:8500::/32 No ROA None 631 99% 68
175.100.165.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.4.244.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
175.100.167.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
103.4.244.0/22 No ROA RIR databaseAPNIC, NTTCOM, RADB 669 99% 67
175.100.164.0/22 No ROA RIR databaseAPNIC, NTTCOM, RADB 669 99% 67
175.100.164.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 92 14% 41
175.100.166.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 25 4%low visibility 18

AS-SET

AS55350's PeeringDB record names no 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 22 are in fix.csv.

  • ROA: none8
  • Route object: none1
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: none2401:8500::/32No ROA covers it. Add a ROA for AS55350, maxLength 32.631 of 636
Route object: none2401:8500::/32No route object for it. Add a route object with origin AS55350 in the RIR database for the space.631 of 636
ROA: none175.100.165.0/24No ROA covers it. Add a ROA for AS55350, maxLength 24.673 of 673
ROA: none103.4.244.0/24No ROA covers it. Add a ROA for AS55350, maxLength 24.671 of 673
ROA: none175.100.167.0/24No ROA covers it. Add a ROA for AS55350, maxLength 24.671 of 673
ROA: none103.4.244.0/22No ROA covers it. Add a ROA for AS55350, maxLength 22.669 of 673
ROA: none175.100.164.0/22No ROA covers it. Add a ROA for AS55350, maxLength 22.669 of 673
ROA: none175.100.164.0/24No ROA covers it. Add a ROA for AS55350, maxLength 24.92 of 673
ROA: none175.100.166.0/24No ROA covers it. Add a ROA for AS55350, maxLength 24.25 of 673

Route objects not announced

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

103.4.244.0/23NTTCOM, RADBNo ROA
103.4.245.0/24APNIC, NTTCOM, RADBNo ROA
103.4.246.0/23NTTCOM, RADBNo ROA
103.4.246.0/24APNIC, NTTCOM, RADBNo ROA
103.4.247.0/24APNIC, NTTCOM, RADBNo ROA
103.18.182.0/23NTTCOM, RADBNo ROA
103.18.182.0/24NTTCOM, RADBNo ROA
103.18.183.0/24NTTCOM, RADBNo ROA
103.65.98.0/23NTTCOM, RADBNo ROA
103.65.98.0/24NTTCOM, RADBNo ROA
103.65.99.0/24NTTCOM, RADBNo ROA
175.100.164.0/23NTTCOM, RADBNo ROA
175.100.166.0/23NTTCOM, RADBNo 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.