bgpreport

Network · data from 2026-11-12

AS25631 Gallaudet University

Registry name: GALLAUDET - Gallaudet University, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS25631, 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.
134.231.0.0/21 No ROA Other origin onlycovered by 134.231.0.0/20 673 100% 68
134.231.0.0/24 No ROA Other origin onlycovered by 134.231.0.0/20 672 100% 68
134.231.4.0/23 No ROA Nonecovered by 134.231.0.0/20 672 100% 68
134.231.10.0/24 No ROA Nonecovered by 134.231.0.0/20 672 100% 68
192.26.10.0/24 No ROA Other IRR onlyRADB 673 100% 68
2620:d2::/48 No ROA Other IRR onlyRADB 634 100% 68

AS-SET

AS25631'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 14 are in fix.csv.

  • ROA: none6
  • Route object: none4
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none134.231.0.0/21No ROA covers it. Add a ROA for AS25631, maxLength 21.673 of 673
Route object: none134.231.0.0/21Route objects for it name AS46887. A route object for 134.231.0.0/20 with origin AS25631 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25631 in the RIR database for the space.673 of 673
ROA: none134.231.0.0/24No ROA covers it. Add a ROA for AS25631, maxLength 24.672 of 673
Route object: none134.231.0.0/24Route objects for it name AS46887. A route object for 134.231.0.0/20 with origin AS25631 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25631 in the RIR database for the space.672 of 673
ROA: none134.231.4.0/23No ROA covers it. Add a ROA for AS25631, maxLength 23.672 of 673
Route object: none134.231.4.0/23No route object for it. A route object for 134.231.0.0/20 with origin AS25631 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25631 in the RIR database for the space.672 of 673
ROA: none134.231.10.0/24No ROA covers it. Add a ROA for AS25631, maxLength 24.672 of 673
Route object: none134.231.10.0/24No route object for it. A route object for 134.231.0.0/20 with origin AS25631 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25631 in the RIR database for the space.672 of 673
ROA: none192.26.10.0/24No ROA covers it. Add a ROA for AS25631, maxLength 24.673 of 673
Route object: RIR192.26.10.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none2620:d2::/48No ROA covers it. Add a ROA for AS25631, maxLength 48.634 of 636
Route object: RIR2620:d2::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

134.231.0.0/16RADBNo ROA
134.231.0.0/20RADBNo 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.