bgpreport

Network · data from 2026-11-12

AS45079 GDS Services

Registry name: GDSNET - GDS CHANGAN SERVICES Ltd., CN · PeeringDB

21IPv4 routes 90.5% RPKI valid · 71.4% with a route object
3IPv6 routes 100.0% RPKI valid · 100.0% with a route object
2RPKI invalid 0 origin · 2 maxLength
0No ROA 6 with no route object for this origin
7Low visibility seen by under 10% of full-table peers
17Route objects not announced registered with origin AS45079, seen from no peer

Announced routes

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

101.52.68.0/24 Invalid: maxLength Nonecovered by 101.52.68.0/23 10 1%low visibility 5
101.52.69.0/24 Invalid: maxLength Nonecovered by 101.52.68.0/23 10 1%low visibility 5
101.52.70.0/23 Valid Nonecovered by 101.52.0.0/16 5 1%low visibility 6
101.52.200.0/22 Valid Nonecovered by 101.52.0.0/16 5 1%low visibility 6
101.52.232.0/23 Valid Nonecovered by 101.52.0.0/16 1 0%low visibility 3
101.52.238.0/23 Valid Nonecovered by 101.52.0.0/16 1 0%low visibility 3
101.52.124.0/22 Valid Other IRR onlyRADB 673 100% 67
101.52.128.0/20 Valid Other IRR onlyRADB 673 100% 67
101.52.128.0/21 Valid Other IRR onlyRADB 673 100% 67
101.52.135.0/24 Valid Other IRR onlyRADB 673 100% 67
101.52.136.0/22 Valid Other IRR onlyRADB 673 100% 67
101.52.140.0/22 Valid Other IRR onlyRADB 673 100% 67
101.52.140.0/24 Valid Other IRR onlyRADB 673 100% 67
101.52.141.0/24 Valid Other IRR onlyRADB 673 100% 67
101.52.142.0/24 Valid Other IRR onlyRADB 673 100% 67
101.52.4.0/24 Valid Other IRR onlyRADB 672 100% 67
101.52.6.0/24 Valid Other IRR onlyRADB 672 100% 67
101.52.116.0/22 Valid Other IRR onlyRADB 672 100% 67
101.52.137.0/24 Valid Other IRR onlyRADB 672 100% 67
101.52.68.0/23 Valid Other IRR onlyRADB 671 100% 67
2402:6f40::/48 Valid Other IRR onlyRADB 636 100% 68
2402:6f40:2::/48 Valid Other IRR onlyRADB 636 100% 68
2402:6f40:3::/48 Valid Other IRR onlyRADB 636 100% 68
101.52.112.0/22 Valid Other IRR onlyRADB 9 1%low visibility 8

AS-SET

PeeringDB's irr_as_set for AS45079: AS-GDS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS45079 isn't in the set, or no route object for AS45079 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS45079 in itNot covered
AS-GDS RADB 1135 Yes 0

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

  • ROA: maxLength2
  • Route object: none6
  • Route object: RIR18
  • Route object: not announced17
ChangePrefix or setDetailFull-table peers
ROA: maxLength101.52.68.0/24ROA 101.52.68.0/23 AS45079 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 101.52.68.0/24.10 of 673
Route object: none101.52.68.0/24No route object for it. A route object for 101.52.68.0/23 with origin AS45079 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45079 in the RIR database for the space.10 of 673
ROA: maxLength101.52.69.0/24ROA 101.52.68.0/23 AS45079 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 101.52.69.0/24.10 of 673
Route object: none101.52.69.0/24No route object for it. A route object for 101.52.68.0/23 with origin AS45079 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45079 in the RIR database for the space.10 of 673
Route object: none101.52.70.0/23No route object for it. A route object for 101.52.0.0/16 with origin AS45079 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45079 in the RIR database for the space.5 of 673
Route object: none101.52.200.0/22No route object for it. A route object for 101.52.0.0/16 with origin AS45079 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45079 in the RIR database for the space.5 of 673
Route object: none101.52.232.0/23No route object for it. A route object for 101.52.0.0/16 with origin AS45079 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45079 in the RIR database for the space.1 of 673
Route object: none101.52.238.0/23No route object for it. A route object for 101.52.0.0/16 with origin AS45079 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45079 in the RIR database for the space.1 of 673
Route object: RIR101.52.124.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR101.52.128.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR101.52.128.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR101.52.135.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR101.52.136.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR101.52.140.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR101.52.140.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR101.52.141.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR101.52.142.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR101.52.4.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR101.52.6.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR101.52.116.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR101.52.137.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR101.52.68.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2402:6f40::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2402:6f40:2::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2402:6f40:3::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR101.52.112.0/22Route object only in RADB. Add it in the RIR database for the space.9 of 673

Route objects not announced

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

101.52.0.0/16APNICNo ROA
101.52.0.0/24RADBNo ROA
101.52.1.0/24RADBNo ROA
101.52.2.0/24RADBNo ROA
101.52.3.0/24RADBNo ROA
101.52.5.0/24RADBNo ROA
101.52.7.0/24RADBNo ROA
101.52.8.0/24RADBNo ROA
101.52.9.0/24RADBNo ROA
101.52.10.0/24RADBNo ROA
101.52.11.0/24RADBNo ROA
101.52.12.0/24RADBNo ROA
101.52.13.0/24RADBNo ROA
101.52.14.0/24RADBNo ROA
101.52.15.0/24RADBNo ROA
101.52.52.0/24RADBNo ROA
101.52.112.0/24RADBValid

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.