bgpreport

Network · data from 2026-11-12

AS139099 GEELY - Zhejiang Geely Holding Group

Registry name: GEELY - Zhejiang Geely Holding Group, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS139099, 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.
120.131.16.0/24 Valid Nonecovered by 120.131.16.0/20 673 100% 67
120.131.17.0/24 Valid Nonecovered by 120.131.16.0/20 673 100% 67
120.131.18.0/23 Valid Nonecovered by 120.131.16.0/20 673 100% 67
120.131.19.0/24 Valid Nonecovered by 120.131.16.0/20 673 100% 67
120.131.25.0/24 Valid Nonecovered by 120.131.16.0/20 673 100% 67
120.131.26.0/23 Valid Nonecovered by 120.131.16.0/20 673 100% 67
120.131.26.0/24 Valid Nonecovered by 120.131.16.0/20 673 100% 67
120.131.27.0/24 Valid Nonecovered by 120.131.16.0/20 673 100% 67
120.131.28.0/22 Valid Nonecovered by 120.131.16.0/20 673 100% 67
120.131.28.0/24 Valid Nonecovered by 120.131.16.0/20 673 100% 67
120.131.29.0/24 Valid Nonecovered by 120.131.16.0/20 673 100% 67
120.131.30.0/24 Valid Nonecovered by 120.131.16.0/20 673 100% 67
120.131.31.0/24 Valid Nonecovered by 120.131.16.0/20 673 100% 67
120.131.18.0/24 Valid Nonecovered by 120.131.16.0/20 82 12% 40
2409:6100::/44 Valid None 22 3%low visibility 14
120.131.16.0/20 Valid RIR databaseAPNIC 673 100% 67

AS-SET

AS139099 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 18 are in fix.csv.

  • Route object: none15
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none120.131.16.0/24No route object for it. A route object for 120.131.16.0/20 with origin AS139099 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139099 in the RIR database for the space.673 of 673
Route object: none120.131.17.0/24No route object for it. A route object for 120.131.16.0/20 with origin AS139099 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139099 in the RIR database for the space.673 of 673
Route object: none120.131.18.0/23No route object for it. A route object for 120.131.16.0/20 with origin AS139099 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139099 in the RIR database for the space.673 of 673
Route object: none120.131.19.0/24No route object for it. A route object for 120.131.16.0/20 with origin AS139099 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139099 in the RIR database for the space.673 of 673
Route object: none120.131.25.0/24No route object for it. A route object for 120.131.16.0/20 with origin AS139099 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139099 in the RIR database for the space.673 of 673
Route object: none120.131.26.0/23No route object for it. A route object for 120.131.16.0/20 with origin AS139099 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139099 in the RIR database for the space.673 of 673
Route object: none120.131.26.0/24No route object for it. A route object for 120.131.16.0/20 with origin AS139099 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139099 in the RIR database for the space.673 of 673
Route object: none120.131.27.0/24No route object for it. A route object for 120.131.16.0/20 with origin AS139099 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139099 in the RIR database for the space.673 of 673
Route object: none120.131.28.0/22No route object for it. A route object for 120.131.16.0/20 with origin AS139099 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139099 in the RIR database for the space.673 of 673
Route object: none120.131.28.0/24No route object for it. A route object for 120.131.16.0/20 with origin AS139099 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139099 in the RIR database for the space.673 of 673
Route object: none120.131.29.0/24No route object for it. A route object for 120.131.16.0/20 with origin AS139099 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139099 in the RIR database for the space.673 of 673
Route object: none120.131.30.0/24No route object for it. A route object for 120.131.16.0/20 with origin AS139099 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139099 in the RIR database for the space.673 of 673
Route object: none120.131.31.0/24No route object for it. A route object for 120.131.16.0/20 with origin AS139099 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139099 in the RIR database for the space.673 of 673
Route object: none120.131.18.0/24No route object for it. A route object for 120.131.16.0/20 with origin AS139099 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139099 in the RIR database for the space.82 of 673
Route object: none2409:6100::/44No route object for it. Add a route object with origin AS139099 in the RIR database for the space.22 of 636

Route objects not announced

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

103.157.174.0/23APNICNo ROA
120.131.32.0/19APNICNo ROA
2409:6000::/32APNICNo 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.