bgpreport

Network · data from 2026-11-12

AS53559 ANONYMIZER - KST Networks

Registry name: ANONYMIZER - KST Networks, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS53559, 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.238.20.0/24 No ROA Other IRR onlyRADB 673 100% 67
192.238.29.0/24 No ROA Other IRR onlyRADB 673 100% 67
192.238.30.0/24 No ROA Other IRR onlyRADB 673 100% 67
66.163.218.0/24 Valid RIR databaseARIN 673 100% 67
192.238.23.0/24 Valid RIR databaseARIN 673 100% 67
192.238.28.0/24 Valid RIR databaseARIN 673 100% 67
198.35.25.0/24 Valid RIR databaseARIN, RADB 673 100% 67
198.212.219.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.41.141.0/24 Valid RIR databaseARIN, RADB 673 100% 67

AS-SET

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

  • ROA: none3
  • Route object: RIR3
  • Route object: not announced109
ChangePrefix or setDetailFull-table peers
ROA: none192.238.20.0/24No ROA covers it. Add a ROA for AS53559, maxLength 24.673 of 673
Route object: RIR192.238.20.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none192.238.29.0/24No ROA covers it. Add a ROA for AS53559, maxLength 24.673 of 673
Route object: RIR192.238.29.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none192.238.30.0/24No ROA covers it. Add a ROA for AS53559, maxLength 24.673 of 673
Route object: RIR192.238.30.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

24.235.6.0/24RADBNo ROA
64.64.120.0/24RADBNo ROA
66.163.220.0/24RADBNo ROA
98.159.46.0/24RADBNo ROA
104.143.215.0/24RADBNo ROA
104.166.107.0/24RADBNo ROA
104.166.123.0/24RADBNo ROA
104.166.126.0/24RADBNo ROA
104.222.142.0/24RADBNo ROA
104.222.223.0/24RADBNo ROA
104.247.11.0/24RADBNo ROA
104.247.17.0/24RADBNo ROA
104.247.29.0/24RADBNo ROA
104.247.97.0/24RADBNo ROA
104.247.126.0/24RADBNo ROA
140.239.236.0/24RADBNo ROA
140.239.237.0/24RADBNo ROA
147.203.12.0/24RADBNo ROA
147.203.99.0/24RADBNo ROA
147.203.108.0/24RADBNo ROA
147.203.194.0/24RADBNo ROA
173.239.206.0/24RADBNo ROA
173.239.252.0/24RADBNo ROA
173.244.38.0/24RADBNo ROA
173.244.53.0/24RADBNo ROA
192.238.18.0/24RADBNo ROA
192.238.24.0/24RADBNo ROA
192.238.25.0/24RADBNo ROA
192.238.26.0/24RADBNo ROA
198.35.24.0/24RADBNo ROA
198.212.220.0/24RADBNo ROA
204.68.106.0/24RADBNo ROA
204.68.119.0/24RADBNo ROA
204.87.135.0/24RADBNo ROA
206.71.162.0/24RADBNo ROA
206.71.191.0/24RADBNo ROA
206.251.230.0/24RADBNo ROA
207.110.34.0/23RADBNo ROA
207.110.46.0/24RADBNo ROA
207.110.47.0/24RADBNo ROA
207.158.4.0/24RADBNo ROA
207.158.17.0/24RADBNo ROA
207.158.24.0/24RADBNo ROA
207.158.35.0/24RADBNo ROA
207.158.36.0/24RADBNo ROA
207.158.41.0/24RADBNo ROA
207.158.51.0/24RADBNo ROA
207.195.240.0/20RADBNo ROA
207.195.240.0/24RADBNo ROA
207.195.241.0/24RADBNo ROA
207.195.242.0/24RADBNo ROA
207.195.243.0/24RADBNo ROA
207.195.244.0/24RADBNo ROA
207.195.246.0/24RADBNo ROA
207.195.247.0/24RADBNo ROA
207.195.248.0/24RADBNo ROA
207.195.249.0/24RADBNo ROA
207.195.253.0/24RADBNo ROA
207.195.254.0/24RADBNo ROA
209.59.32.0/19RADBNo ROA
209.59.32.0/24RADBNo ROA
209.59.33.0/24RADBNo ROA
209.59.34.0/24RADBNo ROA
209.59.36.0/24RADBNo ROA
209.59.37.0/24RADBNo ROA
209.59.39.0/24RADBNo ROA
209.59.40.0/24RADBNo ROA
209.59.42.0/24RADBNo ROA
209.59.43.0/24RADBNo ROA
209.59.44.0/24RADBNo ROA
209.59.45.0/24RADBNo ROA
209.59.46.0/24RADBNo ROA
209.59.47.0/24RADBNo ROA
209.59.50.0/24RADBNo ROA
209.59.51.0/24RADBNo ROA
209.59.54.0/24RADBNo ROA
209.59.55.0/24RADBNo ROA
209.59.57.0/24RADBNo ROA
209.59.59.0/24RADBNo ROA
209.59.61.0/24RADBNo ROA
209.59.62.0/24RADBNo ROA
209.59.63.0/24RADBNo ROA
209.118.143.0/24RADBNo ROA
209.161.96.0/24RADBNo ROA
209.161.100.0/24RADBNo ROA
209.216.214.0/24RADBNo ROA
209.216.220.0/24RADBNo ROA
209.216.226.0/24RADBNo ROA
209.216.228.0/24RADBNo ROA
209.216.235.0/24RADBNo ROA
216.0.107.0/24RADBNo ROA
216.41.140.0/24RADBNo ROA
2620:111:2000::/44RADBNo ROA
2620:111:2000::/48RADBNo ROA
2620:111:2001::/48RADBNo ROA
2620:111:2002::/48RADBNo ROA
2620:111:2003::/48RADBNo ROA
2620:111:2004::/48RADBNo ROA
2620:111:2005::/48RADBNo ROA
2620:111:2006::/48RADBNo ROA
2620:111:2007::/48RADBNo ROA
2620:111:2008::/48RADBNo ROA
2620:111:2009::/48RADBNo ROA
2620:111:200a::/48RADBNo ROA
2620:111:200b::/48RADBNo ROA
2620:111:200c::/48RADBNo ROA
2620:111:200d::/48RADBNo ROA
2620:111:200e::/48RADBNo ROA
2620:111:200f::/48RADBNo 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.