bgpreport

Network · data from 2026-11-12

AS2 UDEL-DCN - University of Delaware

Registry name: UDEL-DCN - University of Delaware, US · not in PeeringDB

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

Announced routes

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

177.85.170.0/24 Invalid: origin Other origin only 5 1%low visibility 4
177.85.171.0/24 Invalid: origin Other origin only 5 1%low visibility 4
201.159.75.0/24 Invalid: origin Other origin only 5 1%low visibility 4
171.79.128.0/20 No ROA None 673 100% 67
171.79.144.0/20 No ROA None 673 100% 67
91.143.144.0/20 No ROA Other origin only 671 100% 67
194.190.53.0/24 No ROA Other origin only 177 26% 56
194.190.54.0/24 No ROA Other origin only 177 26% 56
189.39.185.0/24 No ROA Other origin only 164 24% 56
189.76.77.0/24 No ROA Other origin only 88 13% 33
196.13.136.0/24 No ROA Other origin only 47 7%low visibility 17
129.205.64.0/20 No ROA Other origin only 18 3%low visibility 12
154.65.12.0/22 No ROA Other origin only 18 3%low visibility 12
128.4.0.0/16 Valid Other IRR onlyRADB 671 100% 68

AS-SET

AS2 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 28 are in fix.csv.

  • ROA: origin3
  • ROA: none10
  • Route object: none13
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin177.85.170.0/24ROAs covering it name AS61763, not AS2. If AS2 should announce it, add a ROA for AS2.5 of 673
Route object: none177.85.170.0/24Route objects for it name AS61763. Add a route object with origin AS2 in the RIR database for the space.5 of 673
ROA: origin177.85.171.0/24ROAs covering it name AS61763, not AS2. If AS2 should announce it, add a ROA for AS2.5 of 673
Route object: none177.85.171.0/24Route objects for it name AS61763. Add a route object with origin AS2 in the RIR database for the space.5 of 673
ROA: origin201.159.75.0/24ROAs covering it name AS61763, not AS2. If AS2 should announce it, add a ROA for AS2.5 of 673
Route object: none201.159.75.0/24Route objects for it name AS61763. Add a route object with origin AS2 in the RIR database for the space.5 of 673
ROA: none171.79.128.0/20No ROA covers it. Add a ROA for AS2, maxLength 20.673 of 673
Route object: none171.79.128.0/20No route object for it. Add a route object with origin AS2 in the RIR database for the space.673 of 673
ROA: none171.79.144.0/20No ROA covers it. Add a ROA for AS2, maxLength 20.673 of 673
Route object: none171.79.144.0/20No route object for it. Add a route object with origin AS2 in the RIR database for the space.673 of 673
ROA: none91.143.144.0/20No ROA covers it. Add a ROA for AS2, maxLength 20.671 of 673
Route object: none91.143.144.0/20Route objects for it name AS41837. Add a route object with origin AS2 in the RIR database for the space.671 of 673
ROA: none194.190.53.0/24No ROA covers it. Add a ROA for AS2, maxLength 24.177 of 673
Route object: none194.190.53.0/24Route objects for it name AS203794. Add a route object with origin AS2 in the RIR database for the space.177 of 673
ROA: none194.190.54.0/24No ROA covers it. Add a ROA for AS2, maxLength 24.177 of 673
Route object: none194.190.54.0/24Route objects for it name AS203794. Add a route object with origin AS2 in the RIR database for the space.177 of 673
ROA: none189.39.185.0/24No ROA covers it. Add a ROA for AS2, maxLength 24.164 of 673
Route object: none189.39.185.0/24Route objects for it name AS270792. Add a route object with origin AS2 in the RIR database for the space.164 of 673
ROA: none189.76.77.0/24No ROA covers it. Add a ROA for AS2, maxLength 24.88 of 673
Route object: none189.76.77.0/24Route objects for it name AS52752. Add a route object with origin AS2 in the RIR database for the space.88 of 673
ROA: none196.13.136.0/24No ROA covers it. Add a ROA for AS2, maxLength 24.47 of 673
Route object: none196.13.136.0/24Route objects for it name AS15808, AS37027, AS327753. Add a route object with origin AS2 in the RIR database for the space.47 of 673
ROA: none129.205.64.0/20No ROA covers it. Add a ROA for AS2, maxLength 20.18 of 673
Route object: none129.205.64.0/20Route objects for it name AS37628. Add a route object with origin AS2 in the RIR database for the space.18 of 673
ROA: none154.65.12.0/22No ROA covers it. Add a ROA for AS2, maxLength 22.18 of 673
Route object: none154.65.12.0/22Route objects for it name AS37628. Add a route object with origin AS2 in the RIR database for the space.18 of 673
Route object: RIR128.4.0.0/16Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

1.1.2.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.