bgpreport

Network · data from 2026-11-12

AS59083 KHTech

Registry name: KHTech - Shanghai Kuanhui Tech. Co.,ltd, CN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS59083, 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.254.152.0/24 Valid Other origin onlycovered by 43.254.152.0/23 45 7%low visibility 23
43.254.153.0/24 Valid Other IRR onlyRADB 673 100% 67
43.254.154.0/23 Valid Other IRR onlyRADB 673 100% 67
43.254.154.0/24 Valid Other IRR onlyRADB 673 100% 67
59.153.168.0/24 Valid Other IRR onlyRADB 673 100% 67
103.10.0.0/22 Valid Other IRR onlyRADB 673 100% 67
103.10.0.0/24 Valid Other IRR onlyRADB 673 100% 67
103.10.1.0/24 Valid Other IRR onlyRADB 673 100% 67
103.10.2.0/23 Valid Other IRR onlyRADB 673 100% 67
103.10.2.0/24 Valid Other IRR onlyRADB 673 100% 67
103.24.117.0/24 Valid Other IRR onlyRADB 673 100% 67
2403:1b80::/48 Valid Other IRR onlyRADB 636 100% 68

AS-SET

AS59083'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.

  • Route object: none1
  • Route object: RIR11
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
Route object: none43.254.152.0/24Route objects for it name AS4812. A route object for 43.254.152.0/23 with origin AS59083 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59083 in the RIR database for the space.45 of 673
Route object: RIR43.254.153.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR43.254.154.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR43.254.154.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR59.153.168.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.10.0.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.10.0.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.10.1.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.10.2.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.10.2.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.24.117.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2403:1b80::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

43.254.152.0/22RADBValid
43.254.152.0/23RADBValid
43.254.155.0/24RADBValid
59.153.169.0/24RADBValid
59.153.172.0/24RADBValid
103.10.0.0/23NTTCOM, RADBValid
103.10.3.0/24RADBValid
103.24.116.0/22RADBValid
103.24.116.0/23RADBValid
202.89.96.0/22RADBValid

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.