bgpreport

Network · data from 2026-11-12

AS39986 GEORGE-FOX-UNIVERSITY - George Fox University

Registry name: GEORGE-FOX-UNIVERSITY - George Fox University, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS39986, 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.
209.170.248.0/24 No ROA Other IRR onlyRADB 667 99% 68
209.170.249.0/24 No ROA Other IRR onlyRADB 667 99% 68
209.170.250.0/24 No ROA Other IRR onlyRADB 667 99% 68
209.170.251.0/24 No ROA Other IRR onlyRADB 667 99% 68
209.170.252.0/24 No ROA Other IRR onlyRADB 667 99% 68
209.170.254.0/24 No ROA Other IRR onlyRADB 667 99% 68
209.170.255.0/24 No ROA Other IRR onlyRADB 667 99% 68

AS-SET

AS39986 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 16 are in fix.csv.

  • ROA: none7
  • Route object: RIR7
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none209.170.248.0/24No ROA covers it. Add a ROA for AS39986, maxLength 24.667 of 673
Route object: RIR209.170.248.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none209.170.249.0/24No ROA covers it. Add a ROA for AS39986, maxLength 24.667 of 673
Route object: RIR209.170.249.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none209.170.250.0/24No ROA covers it. Add a ROA for AS39986, maxLength 24.667 of 673
Route object: RIR209.170.250.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none209.170.251.0/24No ROA covers it. Add a ROA for AS39986, maxLength 24.667 of 673
Route object: RIR209.170.251.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none209.170.252.0/24No ROA covers it. Add a ROA for AS39986, maxLength 24.667 of 673
Route object: RIR209.170.252.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none209.170.254.0/24No ROA covers it. Add a ROA for AS39986, maxLength 24.667 of 673
Route object: RIR209.170.254.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none209.170.255.0/24No ROA covers it. Add a ROA for AS39986, maxLength 24.667 of 673
Route object: RIR209.170.255.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673

Route objects not announced

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

209.170.248.0/21ARINNo ROA
2620:5d:c000::/48ARINNo 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.