bgpreport

Network · data from 2026-11-12

AS7536 CDNEXIS-NET - chiaochiao ltd.

Registry name: CDNEXIS-NET - chiaochiao ltd., TW · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS7536, 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.
49.213.34.0/24 Valid Other IRR onlyRADB 673 100% 70
49.213.35.0/24 Valid Other IRR onlyRADB 673 100% 70
103.159.120.0/24 Valid Other IRR onlyRADB 673 100% 70
103.117.132.0/24 Valid Other IRR onlyRADB 672 100% 67
103.117.133.0/24 Valid Other IRR onlyRADB 672 100% 67
103.198.152.0/24 Valid Other IRR onlyRADB 672 100% 67
103.198.153.0/24 Valid Other IRR onlyRADB 672 100% 67
122.50.15.0/24 Valid Other IRR onlyRADB 670 100% 67
211.79.102.0/24 Valid Other IRR onlyRADB 211 31% 52
122.50.14.0/24 Valid Other IRR onlyRADB 76 11% 34
211.79.103.0/24 Valid Other IRR onlyRADB 48 7%low visibility 30
107.149.172.0/24 Valid RIR databaseARIN, RADB 673 100% 67
107.148.159.0/24 Valid RIR databaseARIN, RADB 672 100% 67
157.254.212.0/24 Valid RIR databaseARIN, RADB 672 100% 67
185.213.248.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
87.82.242.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
87.84.131.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
194.147.4.0/24 Valid RIR databaseRADB, RIPE 670 100% 67

AS-SET

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

  • Route object: RIR11
  • Route object: not announced18
ChangePrefix or setDetailFull-table peers
Route object: RIR49.213.34.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR49.213.35.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.159.120.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.117.132.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.117.133.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.198.152.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.198.153.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR122.50.15.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR211.79.102.0/24Route object only in RADB. Add it in the RIR database for the space.211 of 673
Route object: RIR122.50.14.0/24Route object only in RADB. Add it in the RIR database for the space.76 of 673
Route object: RIR211.79.103.0/24Route object only in RADB. Add it in the RIR database for the space.48 of 673

Route objects not announced

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

49.213.34.0/23RADBValid
103.64.22.0/23RADBValid
103.64.22.0/24RADBValid
103.64.23.0/24RADBValid
103.117.132.0/23RADBValid
103.159.120.0/23RADBValid
103.159.121.0/24RADBValid
103.189.108.0/23RADBValid
103.189.108.0/24RADBValid
103.189.109.0/24RADBValid
103.198.152.0/23RADBValid
103.255.42.0/23RADBNo ROA
103.255.42.0/24RADBNo ROA
103.255.43.0/24RADBNo ROA
122.50.14.0/23RADBValid
211.79.102.0/23RADBValid
2402:28a0::/32RADBNo ROA
2402:3560::/32RADBNo 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.