bgpreport

Network · data from 2026-11-12

AS17005 NFL3 - National Football League

Registry name: NFL3 - National Football League, US · not in PeeringDB

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

Announced routes

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

72.46.66.0/23 Valid Nonecovered by 72.46.64.0/21 673 100% 67
72.46.68.0/23 Valid Nonecovered by 72.46.64.0/21 673 100% 67
204.141.136.0/21 Valid None 673 100% 67
204.141.132.0/22 Valid Other IRR onlyNTTCOM 673 100% 67

AS-SET

AS17005 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 9 are in fix.csv.

  • Route object: none3
  • Route object: RIR1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: none72.46.66.0/23No route object for it. A route object for 72.46.64.0/21 with origin AS17005 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17005 in the RIR database for the space.673 of 673
Route object: none72.46.68.0/23No route object for it. A route object for 72.46.64.0/21 with origin AS17005 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17005 in the RIR database for the space.673 of 673
Route object: none204.141.136.0/21No route object for it. Add a route object with origin AS17005 in the RIR database for the space.673 of 673
Route object: RIR204.141.132.0/22Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

72.46.64.0/21ARINValid
204.141.104.0/21NTTCOMValid
204.141.128.0/21NTTCOMValid
204.141.128.0/22NTTCOMValid
208.179.187.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.