bgpreport

Network · data from 2026-11-12

AS25668 AEBC Internet Corp.

Registry name: CIPHERKEY - Cipherkey Exchange Corp., CA · PeeringDB

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

Announced routes

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

192.197.96.0/20 No ROA Other origin only 673 100% 67
38.13.64.0/19 No ROA Other IRR onlyRADB 671 100% 67
38.23.128.0/19 No ROA Other IRR onlyRADB 671 100% 67
38.34.64.0/19 No ROA Other IRR onlyRADB 671 100% 67
38.35.0.0/19 No ROA Other IRR onlyRADB 671 100% 67
38.131.96.0/19 No ROA Other IRR onlyRADB 671 100% 67
38.172.224.0/19 No ROA Other IRR onlyRADB 671 100% 67
38.51.50.0/24 No ROA Other IRR onlyRADB 670 100% 67
199.175.157.0/24 No ROA Other IRR onlyRADB 669 99% 67
204.239.157.0/24 No ROA Other IRR onlyRADB 669 99% 67
2605:7c00::/32 No ROA RIR databaseARIN, RADB 635 100% 69
209.53.194.0/24 Valid Nonecovered by 209.53.194.0/23 669 99% 67
209.53.195.0/24 Valid Nonecovered by 209.53.194.0/23 669 99% 67
209.53.196.0/24 Valid Nonecovered by 209.53.196.0/22 669 99% 67
209.53.197.0/24 Valid Nonecovered by 209.53.196.0/22 669 99% 67
209.53.199.0/24 Valid Nonecovered by 209.53.196.0/22 669 99% 67
209.53.210.0/24 Valid Nonecovered by 209.53.208.0/22 669 99% 67
209.53.211.0/24 Valid Nonecovered by 209.53.208.0/22 669 99% 67
209.53.213.0/24 Valid Nonecovered by 209.53.212.0/23 669 99% 67
208.181.120.0/21 Valid Other IRR onlyRADB 671 100% 67
64.114.80.0/22 Valid Other IRR onlyRADB 669 99% 67
64.114.84.0/23 Valid Other IRR onlyRADB 669 99% 67
64.114.148.0/22 Valid Other IRR onlyRADB 669 99% 67
64.114.200.0/23 Valid Other IRR onlyRADB 669 99% 67
64.114.250.0/23 Valid Other IRR onlyRADB 669 99% 67
205.250.172.0/22 Valid Other IRR onlyRADB 669 99% 67
205.250.196.0/22 Valid Other IRR onlyRADB 669 99% 67
207.34.148.0/22 Valid Other IRR onlyRADB 669 99% 67
207.34.168.0/23 Valid Other IRR onlyRADB 669 99% 67
207.81.148.0/22 Valid Other IRR onlyRADB 669 99% 67
207.194.128.0/22 Valid Other IRR onlyRADB 669 99% 67
207.194.212.0/22 Valid Other IRR onlyRADB 669 99% 67
207.194.216.0/22 Valid Other IRR onlyRADB 669 99% 67
209.52.228.0/24 Valid Other IRR onlyRADB 669 99% 67
65.110.0.0/19 Valid RIR databaseARIN, RADB 671 100% 67
66.51.128.0/20 Valid RIR databaseARIN, RADB 671 100% 67
172.103.128.0/17 Valid RIR databaseARIN, RADB 671 100% 67
208.110.96.0/19 Valid RIR databaseARIN, RADB 671 100% 67
209.53.200.0/21 Valid RIR databaseARIN, RADB 671 100% 67
209.53.212.0/24 Valid RIR databaseARIN, RADB 671 100% 67
209.205.64.0/19 Valid RIR databaseARIN, RADB 671 100% 67
209.205.64.0/21 Valid RIR databaseARIN, RADB 671 100% 67
209.205.80.0/20 Valid RIR databaseARIN, RADB 671 100% 67
209.205.96.0/20 Valid RIR databaseARIN, RADB 671 100% 67
38.75.36.0/22 Valid RIR databaseARIN 669 99% 67
38.123.248.0/22 Valid RIR databaseARIN 669 99% 67
38.187.240.0/23 Valid RIR databaseARIN 669 99% 67
209.53.193.0/24 Valid RIR databaseARIN, RADB 669 99% 67
209.53.194.0/23 Valid RIR databaseARIN, RADB 669 99% 67
209.53.196.0/22 Valid RIR databaseARIN, RADB 669 99% 67
209.53.198.0/24 Valid RIR databaseARIN, RADB 669 99% 67
209.53.208.0/22 Valid RIR databaseARIN, RADB 669 99% 67
209.53.208.0/24 Valid RIR databaseARIN, RADB 669 99% 67
209.53.209.0/24 Valid RIR databaseARIN, RADB 669 99% 67
209.53.212.0/23 Valid RIR databaseARIN, RADB 669 99% 67
209.53.214.0/24 Valid RIR databaseARIN, RADB 669 99% 67
209.205.78.0/24 Valid RIR databaseARIN, RADB 669 99% 67
209.205.79.0/24 Valid RIR databaseARIN, RADB 669 99% 67
209.205.94.0/23 Valid RIR databaseARIN, RADB 669 99% 67
38.135.83.0/24 Valid RIR databaseARIN 668 99% 67
38.187.250.0/24 Valid RIR databaseARIN 668 99% 67

AS-SET

PeeringDB's irr_as_set for AS25668: AS-CIPHERKEY-TRANSIT. 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 (AS25668 isn't in the set, or no route object for AS25668 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 objectsAS25668 in itNot covered
AS-CIPHERKEY-TRANSIT RADB 4183 Yes 1
ARIN (also) 4183 Yes 1

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

  • ROA: none11
  • Route object: none9
  • Route object: RIR24
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none192.197.96.0/20No ROA covers it. Add a ROA for AS25668, maxLength 20.673 of 673
Route object: none192.197.96.0/20Route objects for it name AS19062. Add a route object with origin AS25668 in the RIR database for the space.673 of 673
ROA: none38.13.64.0/19No ROA covers it. Add a ROA for AS25668, maxLength 19.671 of 673
Route object: RIR38.13.64.0/19Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.23.128.0/19No ROA covers it. Add a ROA for AS25668, maxLength 19.671 of 673
Route object: RIR38.23.128.0/19Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.34.64.0/19No ROA covers it. Add a ROA for AS25668, maxLength 19.671 of 673
Route object: RIR38.34.64.0/19Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.35.0.0/19No ROA covers it. Add a ROA for AS25668, maxLength 19.671 of 673
Route object: RIR38.35.0.0/19Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.131.96.0/19No ROA covers it. Add a ROA for AS25668, maxLength 19.671 of 673
Route object: RIR38.131.96.0/19Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.172.224.0/19No ROA covers it. Add a ROA for AS25668, maxLength 19.671 of 673
Route object: RIR38.172.224.0/19Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.51.50.0/24No ROA covers it. Add a ROA for AS25668, maxLength 24.670 of 673
Route object: RIR38.51.50.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none199.175.157.0/24No ROA covers it. Add a ROA for AS25668, maxLength 24.669 of 673
Route object: RIR199.175.157.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none204.239.157.0/24No ROA covers it. Add a ROA for AS25668, maxLength 24.669 of 673
Route object: RIR204.239.157.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2605:7c00::/32No ROA covers it. Add a ROA for AS25668, maxLength 32.635 of 636
Route object: none209.53.194.0/24No route object for it. A route object for 209.53.194.0/23 with origin AS25668 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25668 in the RIR database for the space.669 of 673
Route object: none209.53.195.0/24No route object for it. A route object for 209.53.194.0/23 with origin AS25668 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25668 in the RIR database for the space.669 of 673
Route object: none209.53.196.0/24No route object for it. A route object for 209.53.196.0/22 with origin AS25668 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25668 in the RIR database for the space.669 of 673
Route object: none209.53.197.0/24No route object for it. A route object for 209.53.196.0/22 with origin AS25668 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25668 in the RIR database for the space.669 of 673
Route object: none209.53.199.0/24No route object for it. A route object for 209.53.196.0/22 with origin AS25668 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25668 in the RIR database for the space.669 of 673
Route object: none209.53.210.0/24No route object for it. A route object for 209.53.208.0/22 with origin AS25668 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25668 in the RIR database for the space.669 of 673
Route object: none209.53.211.0/24No route object for it. A route object for 209.53.208.0/22 with origin AS25668 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25668 in the RIR database for the space.669 of 673
Route object: none209.53.213.0/24No route object for it. A route object for 209.53.212.0/23 with origin AS25668 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25668 in the RIR database for the space.669 of 673
Route object: RIR208.181.120.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR64.114.80.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR64.114.84.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR64.114.148.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR64.114.200.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR64.114.250.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR205.250.172.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR205.250.196.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR207.34.148.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR207.34.168.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR207.81.148.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR207.194.128.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR207.194.212.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR207.194.216.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR209.52.228.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

172.103.128.0/19RADBValid
172.103.160.0/19ARIN, RADBValid
172.103.192.0/19ARIN, RADBValid
172.103.224.0/19ARIN, RADBValid
208.110.96.0/20RADBValid
208.110.112.0/20RADBValid
209.205.64.0/20RADBValid
209.205.77.0/24ARIN, RADBValid
2001:470:1bf::/48ARINInvalid: origin
2001:470:1ce::/48ARINInvalid: origin
2001:470:1d1::/48ARINInvalid: 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.