bgpreport

Network · data from 2026-11-12

AS56282 VClouD - Beijing Internet Harbor Technology Co., Ltd

Registry name: VClouD - Beijing Internet Harbor Technology Co., Ltd, CN · not in PeeringDB

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

Announced routes

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

103.235.232.0/21 No ROA None 5 1%low visibility 6
114.66.72.0/21 Valid None 672 100% 67
163.53.128.0/22 Valid None 672 100% 67
103.54.48.0/22 Valid None 44 7%low visibility 30
103.54.48.0/23 Valid None 44 7%low visibility 30
103.54.50.0/23 Valid None 44 7%low visibility 30
103.227.76.0/23 Valid None 44 7%low visibility 30
103.227.82.0/23 Valid None 44 7%low visibility 30
103.231.64.0/22 Valid None 44 7%low visibility 30
103.235.224.0/23 Valid Nonecovered by 103.235.224.0/22 44 7%low visibility 30
103.235.240.0/22 Valid None 44 7%low visibility 30
103.235.240.0/23 Valid None 44 7%low visibility 30
103.235.242.0/23 Valid None 44 7%low visibility 30
103.235.244.0/23 Valid None 44 7%low visibility 30
103.235.246.0/23 Valid None 44 7%low visibility 30
103.249.252.0/23 Valid None 44 7%low visibility 30
103.227.78.0/23 Valid None 5 1%low visibility 6
103.227.80.0/23 Valid None 5 1%low visibility 6
103.227.82.0/24 Valid None 5 1%low visibility 6
103.231.65.0/24 Valid None 5 1%low visibility 6
103.231.66.0/24 Valid None 5 1%low visibility 6
103.231.70.0/24 Valid None 5 1%low visibility 6
103.235.220.0/23 Valid None 5 1%low visibility 6
103.235.222.0/23 Valid None 5 1%low visibility 6
103.235.225.0/24 Valid Nonecovered by 103.235.224.0/22 5 1%low visibility 6
103.235.226.0/23 Valid Nonecovered by 103.235.224.0/22 5 1%low visibility 6
103.235.228.0/23 Valid None 5 1%low visibility 6
103.235.230.0/23 Valid None 5 1%low visibility 6
103.235.244.0/24 Valid None 5 1%low visibility 6
103.235.247.0/24 Valid None 5 1%low visibility 6
103.235.248.0/23 Valid None 5 1%low visibility 6
103.235.250.0/24 Valid None 5 1%low visibility 6
103.237.8.0/23 Valid None 5 1%low visibility 6
103.237.10.0/23 Valid None 5 1%low visibility 6
103.237.11.0/24 Valid None 5 1%low visibility 6
103.243.252.0/23 Valid None 5 1%low visibility 6
103.243.254.0/23 Valid None 5 1%low visibility 6
103.249.254.0/23 Valid None 5 1%low visibility 6
150.129.192.0/23 Valid None 5 1%low visibility 6
150.129.194.0/23 Valid None 5 1%low visibility 6
163.47.4.0/23 Valid None 5 1%low visibility 6
163.47.6.0/23 Valid None 5 1%low visibility 6
163.53.88.0/22 Valid None 5 1%low visibility 6
163.53.92.0/22 Valid None 5 1%low visibility 6
211.155.80.0/20 Valid None 5 1%low visibility 6
211.155.80.0/22 Valid None 5 1%low visibility 6
211.155.84.0/22 Valid None 5 1%low visibility 6
211.155.88.0/22 Valid Nonecovered by 211.155.88.0/21 5 1%low visibility 6
114.66.64.0/24 Valid Other IRR onlyNTTCOM, RADB 5 1%low visibility 6
211.155.92.0/22 Valid Other IRR onlyRADB 5 1%low visibility 6

AS-SET

AS56282 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 53 are in fix.csv.

  • ROA: none1
  • Route object: none48
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none103.235.232.0/21No ROA covers it. Add a ROA for AS56282, maxLength 21.5 of 673
Route object: none103.235.232.0/21No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none114.66.72.0/21No route object for it. Add a route object with origin AS56282 in the RIR database for the space.672 of 673
Route object: none163.53.128.0/22No route object for it. Add a route object with origin AS56282 in the RIR database for the space.672 of 673
Route object: none103.54.48.0/22No route object for it. Add a route object with origin AS56282 in the RIR database for the space.44 of 673
Route object: none103.54.48.0/23No route object for it. Add a route object with origin AS56282 in the RIR database for the space.44 of 673
Route object: none103.54.50.0/23No route object for it. Add a route object with origin AS56282 in the RIR database for the space.44 of 673
Route object: none103.227.76.0/23No route object for it. Add a route object with origin AS56282 in the RIR database for the space.44 of 673
Route object: none103.227.82.0/23No route object for it. Add a route object with origin AS56282 in the RIR database for the space.44 of 673
Route object: none103.231.64.0/22No route object for it. Add a route object with origin AS56282 in the RIR database for the space.44 of 673
Route object: none103.235.224.0/23No route object for it. A route object for 103.235.224.0/22 with origin AS56282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56282 in the RIR database for the space.44 of 673
Route object: none103.235.240.0/22No route object for it. Add a route object with origin AS56282 in the RIR database for the space.44 of 673
Route object: none103.235.240.0/23No route object for it. Add a route object with origin AS56282 in the RIR database for the space.44 of 673
Route object: none103.235.242.0/23No route object for it. Add a route object with origin AS56282 in the RIR database for the space.44 of 673
Route object: none103.235.244.0/23No route object for it. Add a route object with origin AS56282 in the RIR database for the space.44 of 673
Route object: none103.235.246.0/23No route object for it. Add a route object with origin AS56282 in the RIR database for the space.44 of 673
Route object: none103.249.252.0/23No route object for it. Add a route object with origin AS56282 in the RIR database for the space.44 of 673
Route object: none103.227.78.0/23No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none103.227.80.0/23No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none103.227.82.0/24No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none103.231.65.0/24No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none103.231.66.0/24No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none103.231.70.0/24No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none103.235.220.0/23No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none103.235.222.0/23No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none103.235.225.0/24No route object for it. A route object for 103.235.224.0/22 with origin AS56282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none103.235.226.0/23No route object for it. A route object for 103.235.224.0/22 with origin AS56282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none103.235.228.0/23No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none103.235.230.0/23No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none103.235.244.0/24No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none103.235.247.0/24No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none103.235.248.0/23No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none103.235.250.0/24No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none103.237.8.0/23No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none103.237.10.0/23No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none103.237.11.0/24No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none103.243.252.0/23No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none103.243.254.0/23No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none103.249.254.0/23No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none150.129.192.0/23No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none150.129.194.0/23No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none163.47.4.0/23No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none163.47.6.0/23No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none163.53.88.0/22No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none163.53.92.0/22No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none211.155.80.0/20No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none211.155.80.0/22No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none211.155.84.0/22No route object for it. Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: none211.155.88.0/22No route object for it. A route object for 211.155.88.0/21 with origin AS56282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56282 in the RIR database for the space.5 of 673
Route object: RIR114.66.64.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR211.155.92.0/22Route object only in RADB. Add it in the RIR database for the space.5 of 673

Route objects not announced

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

103.235.224.0/22RADBValid
211.155.88.0/21RADBValid

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.