bgpreport

Network · data from 2026-11-12

AS41419 KAZRENA-AS KazRENA

Registry name: KAZRENA-AS KazRENA, KZ · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS41419, 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.
89.250.80.48/29 Invalid: maxLength Nonecovered by 89.250.80.0/20 1 0%low visibility 1
89.250.89.0/25 Invalid: maxLength Nonecovered by 89.250.80.0/20 1 0%low visibility 1
89.250.90.0/27 Invalid: maxLength Nonecovered by 89.250.80.0/20 1 0%low visibility 1
2a02:7300::/32 No ROA RIR databaseRIPE 636 100% 68
89.250.88.0/24 Valid Nonecovered by 89.250.80.0/20 673 100% 66
89.250.80.0/20 Valid RIR databaseRIPE 673 100% 66

AS-SET

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

  • ROA: maxLength3
  • ROA: none1
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: maxLength89.250.80.48/29ROA 89.250.80.0/20 AS41419 has maxLength 24; the route is a /29. Raise the maxLength, or add a ROA for 89.250.80.48/29.1 of 673
Route object: none89.250.80.48/29No route object for it. A route object for 89.250.80.0/20 with origin AS41419 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS41419 in the RIR database for the space.1 of 673
ROA: maxLength89.250.89.0/25ROA 89.250.80.0/20 AS41419 has maxLength 24; ROA 89.250.89.0/24 AS41419 has maxLength 24; the route is a /25. Raise the maxLength, or add a ROA for 89.250.89.0/25.1 of 673
Route object: none89.250.89.0/25No route object for it. A route object for 89.250.80.0/20 with origin AS41419 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS41419 in the RIR database for the space.1 of 673
ROA: maxLength89.250.90.0/27ROA 89.250.80.0/20 AS41419 has maxLength 24; ROA 89.250.90.0/24 AS41419 has maxLength 24; the route is a /27. Raise the maxLength, or add a ROA for 89.250.90.0/27.1 of 673
Route object: none89.250.90.0/27No route object for it. A route object for 89.250.80.0/20 with origin AS41419 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS41419 in the RIR database for the space.1 of 673
ROA: none2a02:7300::/32No ROA covers it. Add a ROA for AS41419, maxLength 32.636 of 636
Route object: none89.250.88.0/24No route object for it. A route object for 89.250.80.0/20 with origin AS41419 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41419 in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS41419 is announced.

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.