bgpreport

Network · data from 2026-11-12

AS29752 Zenlayer Edge Cloud Network - AS29752

Registry name: ZEN-SDN - Zenlayer Inc, US · PeeringDB

27IPv4 routes 96.3% RPKI valid · 81.5% with a route object
11IPv6 routes 72.7% RPKI valid · 72.7% with a route object
1RPKI invalid 1 origin · 0 maxLength
3No ROA 8 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
7Route objects not announced registered with origin AS29752, seen from no peer

Announced routes

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

2a0b:21c1:6032::/48 Invalid: origin Other origin only 52 8%low visibility 31
216.225.162.0/24 No ROA Other origin only 673 100% 67
2602:ffe4:ca4::/48 No ROA None 634 100% 68
2607:81c0::/48 No ROA Other origin only 634 100% 68
23.251.35.0/24 Valid Other origin only 673 100% 67
198.44.172.0/24 Valid Other origin onlycovered by 198.44.172.0/22 673 100% 67
198.44.173.0/24 Valid Other origin onlycovered by 198.44.172.0/22 673 100% 67
198.44.174.0/24 Valid Other origin onlycovered by 198.44.172.0/22 673 100% 67
23.251.127.0/24 Valid RIR databaseARIN 673 100% 67
69.28.55.0/24 Valid RIR databaseARIN 673 100% 66
104.166.158.0/24 Valid RIR databaseRIPE 673 100% 67
107.151.157.0/24 Valid RIR databaseARIN 673 100% 67
107.151.194.0/24 Valid RIR databaseARIN 673 100% 67
128.1.206.0/24 Valid RIR databaseARIN 673 100% 67
128.1.216.0/24 Valid RIR databaseARIN 673 100% 66
128.14.13.0/24 Valid RIR databaseARIN 673 100% 67
128.14.90.0/24 Valid RIR databaseARIN 673 100% 66
128.14.91.0/24 Valid RIR databaseARIN 673 100% 66
128.14.161.0/24 Valid RIR databaseARIN 673 100% 67
162.128.9.0/24 Valid RIR databaseAPNIC 673 100% 67
162.128.15.0/24 Valid RIR databaseAPNIC 673 100% 67
162.128.104.0/24 Valid RIR databaseAPNIC 673 100% 66
162.128.106.0/24 Valid RIR databaseAPNIC 673 100% 67
172.96.123.0/24 Valid RIR databaseARIN 673 100% 67
193.118.96.0/24 Valid RIR databaseRIPE 673 100% 67
199.190.47.0/24 Valid RIR databaseARIN 673 100% 66
36.255.92.0/23 Valid RIR databaseRADB, RIPE 672 100% 66
129.227.123.0/24 Valid RIR databaseAPNIC 672 100% 67
162.128.11.0/24 Valid RIR databaseAPNIC 664 99% 67
162.128.12.0/24 Valid RIR databaseAPNIC 663 99% 67
2602:ffe4:ca1::/48 Valid RIR databaseARIN 636 100% 67
2602:ffe4:ca2::/48 Valid RIR databaseARIN 635 100% 67
2604:980:e101::/48 Valid RIR databaseARIN 635 100% 67
2a0b:21c1:601c::/48 Valid RIR databaseRIPE 635 100% 67
2604:980:e100::/48 Valid RIR databaseARIN 634 100% 67
2604:980:e102::/48 Valid RIR databaseARIN 634 100% 67
2a0b:21c1:602a::/48 Valid RIR databaseRIPE 634 100% 67
2a0b:21c1:6030::/48 Valid RIR databaseRIPE 632 99% 68

AS-SET

PeeringDB's irr_as_set for AS29752: AS-ZENLAYER. 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 (AS29752 isn't in the set, or no route object for AS29752 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 objectsAS29752 in itNot covered
AS-ZENLAYER RADBlists itself further down7 member sets in no database: AS-ARESFLARE-TRANSIT, AS-IQ-TW, AS-SET-IID, AS132825:AS-GIGADEFENCE, AS24088:AS-DS … 3,75786842,437 Yes 5
ARIN (also) 112,380 No 38

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

  • ROA: origin1
  • ROA: none3
  • Route object: none8
  • AS-SET: missing member7
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: origin2a0b:21c1:6032::/48ROAs covering it name AS21859, AS62610, not AS29752. If AS29752 should announce it, add a ROA for AS29752.52 of 636
Route object: none2a0b:21c1:6032::/48Route objects for it name AS62610. Add a route object with origin AS29752 in the RIR database for the space.52 of 636
ROA: none216.225.162.0/24No ROA covers it. Add a ROA for AS29752, maxLength 24.673 of 673
Route object: none216.225.162.0/24Route objects for it name AS400866. Add a route object with origin AS29752 in the RIR database for the space.673 of 673
ROA: none2602:ffe4:ca4::/48No ROA covers it. Add a ROA for AS29752, maxLength 48.634 of 636
Route object: none2602:ffe4:ca4::/48No route object for it. Add a route object with origin AS29752 in the RIR database for the space.634 of 636
ROA: none2607:81c0::/48No ROA covers it. Add a ROA for AS29752, maxLength 48.634 of 636
Route object: none2607:81c0::/48Route objects for it name AS400866. Add a route object with origin AS29752 in the RIR database for the space.634 of 636
Route object: none23.251.35.0/24Route objects for it name AS62610. Add a route object with origin AS29752 in the RIR database for the space.673 of 673
Route object: none198.44.172.0/24Route objects for it name AS9269, AS62610, AS137443. A route object for 198.44.172.0/22 with origin AS29752 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29752 in the RIR database for the space.673 of 673
Route object: none198.44.173.0/24Route objects for it name AS9269, AS62610, AS137443. A route object for 198.44.172.0/22 with origin AS29752 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29752 in the RIR database for the space.673 of 673
Route object: none198.44.174.0/24Route objects for it name AS9269, AS62610, AS137443. A route object for 198.44.172.0/22 with origin AS29752 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29752 in the RIR database for the space.673 of 673
AS-SET: missing memberAS-ZENLAYERAS-ZENLAYER (RADB) lists AS-ARESFLARE-TRANSIT; no IRR database read has it.
AS-SET: missing memberAS-ZENLAYERAS-ZENLAYER (RADB) lists AS-IQ-TW; no IRR database read has it.
AS-SET: missing memberAS-ZENLAYERAS-ZENLAYER (RADB) lists AS-SET-IID; no IRR database read has it.
AS-SET: missing memberAS-ZENLAYERAS-ZENLAYER (RADB) lists AS132825:AS-GIGADEFENCE; no IRR database read has it.
AS-SET: missing memberAS-ZENLAYERAS-ZENLAYER (RADB) lists AS24088:AS-DS; no IRR database read has it.
AS-SET: missing memberAS-ZENLAYERAS-ZENLAYER (RADB) lists AS24088:AS-PPS; no IRR database read has it.
AS-SET: missing memberAS-ZENLAYERAS-ZENLAYER (RADB) lists AS55720:AS-GIGADEFENCE; no IRR database read has it.

Route objects not announced

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

128.14.138.0/24ARINValid
198.44.172.0/22ARINValid
207.7.147.0/24BBOINo ROA
209.237.232.0/24BBOINo ROA
209.237.245.0/24BBOINo ROA
209.237.250.0/24BBOINo ROA
2a0b:21c1:6023::/48RIPEInvalid: origin

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.