bgpreport

Network · data from 2026-11-12

AS11995 Oregon Health and Sciences University

Registry name: OHSU - Oregon Health & Science University, US · PeeringDB

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

Announced routes

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

129.95.0.0/23 Valid Nonecovered by 129.95.0.0/16 3 0%low visibility 3
129.95.16.0/20 Valid Nonecovered by 129.95.0.0/16 3 0%low visibility 3
129.95.32.0/20 Valid Nonecovered by 129.95.0.0/16 3 0%low visibility 3
129.95.100.0/24 Valid Nonecovered by 129.95.0.0/16 3 0%low visibility 3
129.95.128.0/17 Valid Nonecovered by 129.95.0.0/16 3 0%low visibility 3
129.95.128.0/20 Valid Nonecovered by 129.95.0.0/16 2 0%low visibility 2
204.63.232.0/21 Valid Other IRR onlyRADB 672 100% 68
137.53.0.0/16 Valid RIR databaseARIN, RADB 672 100% 68
129.95.0.0/16 Valid RIR databaseARIN, RADB 671 100% 68

AS-SET

AS11995's PeeringDB record names no 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.

  • Route object: none6
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none129.95.0.0/23No route object for it. A route object for 129.95.0.0/16 with origin AS11995 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11995 in the RIR database for the space.3 of 673
Route object: none129.95.16.0/20No route object for it. A route object for 129.95.0.0/16 with origin AS11995 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11995 in the RIR database for the space.3 of 673
Route object: none129.95.32.0/20No route object for it. A route object for 129.95.0.0/16 with origin AS11995 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11995 in the RIR database for the space.3 of 673
Route object: none129.95.100.0/24No route object for it. A route object for 129.95.0.0/16 with origin AS11995 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11995 in the RIR database for the space.3 of 673
Route object: none129.95.128.0/17No route object for it. A route object for 129.95.0.0/16 with origin AS11995 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11995 in the RIR database for the space.3 of 673
Route object: none129.95.128.0/20No route object for it. A route object for 129.95.0.0/16 with origin AS11995 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11995 in the RIR database for the space.2 of 673
Route object: RIR204.63.232.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

2605:d900::/32ARINValid

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.