bgpreport

Network · data from 2026-11-12

AS26522 SU-ASN-1 - Stevenson University

Registry name: SU-ASN-1 - Stevenson University, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS26522, 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.
2602:faba::/36 No ROA Other IRR onlyRADB 636 100% 68
64.89.166.0/24 Valid Nonecovered by 64.89.164.0/22 673 100% 67
64.89.164.0/24 Valid Nonecovered by 64.89.164.0/22 671 100% 67
64.89.165.0/24 Valid Nonecovered by 64.89.164.0/22 671 100% 67
64.89.167.0/24 Valid Nonecovered by 64.89.164.0/22 671 100% 67

AS-SET

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

  • ROA: none1
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none2602:faba::/36No ROA covers it. Add a ROA for AS26522, maxLength 36.636 of 636
Route object: RIR2602:faba::/36Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: none64.89.166.0/24No route object for it. A route object for 64.89.164.0/22 with origin AS26522 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26522 in the RIR database for the space.673 of 673
Route object: none64.89.164.0/24No route object for it. A route object for 64.89.164.0/22 with origin AS26522 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26522 in the RIR database for the space.671 of 673
Route object: none64.89.165.0/24No route object for it. A route object for 64.89.164.0/22 with origin AS26522 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26522 in the RIR database for the space.671 of 673
Route object: none64.89.167.0/24No route object for it. A route object for 64.89.164.0/22 with origin AS26522 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26522 in the RIR database for the space.671 of 673

Route objects not announced

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

64.21.15.0/24RADBNo ROA
64.89.164.0/22ARIN, RADBValid
64.247.15.0/24RADBNo ROA
66.246.45.0/24RADBNo ROA
66.246.46.0/24RADBNo ROA
66.246.70.0/24RADBNo ROA
209.123.244.0/24RADBNo 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.