bgpreport

Network · data from 2026-11-12

AS16905 LEARN-RESEARCH

Registry name: LEARN-RESEARCH - LEARN, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS16905, 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.
74.200.150.0/24 No ROA None 20 3%low visibility 18
74.200.179.0/24 No ROA Other origin only 16 2%low visibility 16
2607:f928:16::/48 No ROA Other origin only 13 2%low visibility 15
74.200.187.0/24 No ROA Other IRR onlyRADB 20 3%low visibility 18
2607:f928:2::/48 No ROA Other IRR onlyRADB 17 3%low visibility 18
2607:f928:12::/48 No ROA Other IRR onlyRADB 17 3%low visibility 18
74.200.186.0/24 No ROA Other IRR onlyRADB 16 2%low visibility 16

AS-SET

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

  • ROA: none7
  • Route object: none3
  • Route object: RIR4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none74.200.150.0/24No ROA covers it. Add a ROA for AS16905, maxLength 24.20 of 673
Route object: none74.200.150.0/24No route object for it. Add a route object with origin AS16905 in the RIR database for the space.20 of 673
ROA: none74.200.179.0/24No ROA covers it. Add a ROA for AS16905, maxLength 24.16 of 673
Route object: none74.200.179.0/24Route objects for it name AS22645. Add a route object with origin AS16905 in the RIR database for the space.16 of 673
ROA: none2607:f928:16::/48No ROA covers it. Add a ROA for AS16905, maxLength 48.13 of 636
Route object: none2607:f928:16::/48Route objects for it name AS13359. Add a route object with origin AS16905 in the RIR database for the space.13 of 636
ROA: none74.200.187.0/24No ROA covers it. Add a ROA for AS16905, maxLength 24.20 of 673
Route object: RIR74.200.187.0/24Route object only in RADB. Add it in the RIR database for the space.20 of 673
ROA: none2607:f928:2::/48No ROA covers it. Add a ROA for AS16905, maxLength 48.17 of 636
Route object: RIR2607:f928:2::/48Route object only in RADB. Add it in the RIR database for the space.17 of 636
ROA: none2607:f928:12::/48No ROA covers it. Add a ROA for AS16905, maxLength 48.17 of 636
Route object: RIR2607:f928:12::/48Route object only in RADB. Add it in the RIR database for the space.17 of 636
ROA: none74.200.186.0/24No ROA covers it. Add a ROA for AS16905, maxLength 24.16 of 673
Route object: RIR74.200.186.0/24Route object only in RADB. Add it in the RIR database for the space.16 of 673

Route objects not announced

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

206.223.141.0/24RADBNo ROA
208.76.227.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.