bgpreport

Network · data from 2026-11-12

AS91 Rensselaer Polytechnic Institute

Registry name: RPI-AS - Rensselaer Polytechnic Institute, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS91, 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.
2620:0:bf0::/48 No ROA None 605 95% 67
128.113.0.0/16 No ROA Other IRR onlyRADB 672 100% 68
128.213.0.0/16 No ROA Other IRR onlyRADB 672 100% 68
2620:0:2820::/48 No ROA Other IRR onlyRADB 635 100% 68
146.8.0.0/16 Valid None 672 100% 67
192.12.91.0/24 Valid Other IRR onlyRADB 672 100% 67
192.12.92.0/24 Valid Other IRR onlyRADB 672 100% 67
129.5.0.0/16 Valid RIR databaseARIN 672 100% 67
129.161.0.0/16 Valid RIR databaseARIN, RADB 672 100% 68
204.76.223.0/24 Valid RIR databaseARIN 672 100% 67
204.76.224.0/22 Valid RIR databaseARIN, RADB 672 100% 67
204.76.228.0/23 Valid RIR databaseARIN, RADB 672 100% 67
204.145.205.0/24 Valid RIR databaseARIN, RADB 672 100% 67
204.76.222.0/24 Valid RIR databaseARIN 670 100% 67

AS-SET

AS91'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 12 are in fix.csv.

  • ROA: none4
  • Route object: none2
  • Route object: RIR5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2620:0:bf0::/48No ROA covers it. Add a ROA for AS91, maxLength 48.605 of 636
Route object: none2620:0:bf0::/48No route object for it. Add a route object with origin AS91 in the RIR database for the space.605 of 636
ROA: none128.113.0.0/16No ROA covers it. Add a ROA for AS91, maxLength 16.672 of 673
Route object: RIR128.113.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none128.213.0.0/16No ROA covers it. Add a ROA for AS91, maxLength 16.672 of 673
Route object: RIR128.213.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2620:0:2820::/48No ROA covers it. Add a ROA for AS91, maxLength 48.635 of 636
Route object: RIR2620:0:2820::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: none146.8.0.0/16No route object for it. Add a route object with origin AS91 in the RIR database for the space.672 of 673
Route object: RIR192.12.91.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR192.12.92.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

204.76.222.0/23RADBNo 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.