bgpreport

Network · data from 2026-11-12

AS13783 RADFORD-UNIV-AS - Radford University

Registry name: RADFORD-UNIV-AS - Radford University, US · not in PeeringDB

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

Announced routes

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

137.45.169.0/24 No ROA Nonecovered by 137.45.160.0/20 670 100% 67
137.45.0.0/16 No ROA Other IRR onlyNTTCOM, RADB 670 100% 68

AS-SET

AS13783 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 32 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced28
ChangePrefix or setDetailFull-table peers
ROA: none137.45.169.0/24No ROA covers it. Add a ROA for AS13783, maxLength 24.670 of 673
Route object: none137.45.169.0/24No route object for it. A route object for 137.45.160.0/20 with origin AS13783 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13783 in the RIR database for the space.670 of 673
ROA: none137.45.0.0/16No ROA covers it. Add a ROA for AS13783, maxLength 16.670 of 673
Route object: RIR137.45.0.0/16Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

137.45.0.0/20RADBNo ROA
137.45.14.0/23RADBNo ROA
137.45.16.0/20RADBNo ROA
137.45.32.0/20RADBNo ROA
137.45.44.0/23RADBNo ROA
137.45.48.0/20RADBNo ROA
137.45.48.0/21RADBNo ROA
137.45.56.0/21RADBNo ROA
137.45.64.0/21RADBNo ROA
137.45.72.0/21RADBNo ROA
137.45.78.0/23RADBNo ROA
137.45.80.0/20RADBNo ROA
137.45.84.0/23RADBNo ROA
137.45.88.0/23RADBNo ROA
137.45.92.0/23RADBNo ROA
137.45.112.0/20RADBNo ROA
137.45.120.0/23RADBNo ROA
137.45.144.0/20RADBNo ROA
137.45.160.0/20RADBNo ROA
137.45.176.0/20RADBNo ROA
137.45.204.0/23RADBNo ROA
137.45.208.0/20RADBNo ROA
137.45.208.0/23RADBNo ROA
137.45.224.0/20RADBNo ROA
137.45.232.0/23RADBNo ROA
137.45.240.0/20RADBNo ROA
137.45.244.0/23RADBNo ROA
2620:10c:d000::/44ARINValid

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.