bgpreport

Network · data from 2026-11-12

AS20130 DePaul University

Registry name: DEPAUL - Depaul University, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS20130, 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.
2001:468:1202::/48 Valid None 634 100% 69
75.102.192.0/18 Valid RIR databaseARIN 671 100% 69
140.192.0.0/16 Valid RIR databaseARIN 671 100% 69
216.220.176.0/20 Valid RIR databaseARIN 671 100% 69
2604:95c0::/32 Valid RIR databaseARIN 634 100% 70
2620:0:2250::/48 Valid RIR databaseARIN 634 100% 70

AS-SET

AS20130'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 1 are in fix.csv.

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none2001:468:1202::/48No route object for it. Add a route object with origin AS20130 in the RIR database for the space.634 of 636

Route objects not announced

Every route object with origin AS20130 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.