bgpreport

Network · data from 2026-11-12

AS6210 NFL1 - National Football League

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS6210, 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.64.0/23 Valid Nonecovered by 72.46.64.0/21 673 100% 67
204.141.104.0/21 Valid Other IRR onlyNTTCOM 673 100% 67
204.141.144.0/21 Valid Other IRR onlyNTTCOM 673 100% 67
204.141.152.0/22 Valid Other IRR onlyNTTCOM 673 100% 67

AS-SET

AS6210 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 13 are in fix.csv.

  • Route object: none1
  • Route object: RIR3
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
Route object: none72.46.64.0/23No route object for it. A route object for 72.46.64.0/21 with origin AS6210 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6210 in the RIR database for the space.673 of 673
Route object: RIR204.141.104.0/21Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR204.141.144.0/21Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR204.141.152.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 AS6210 whose prefix no peer sees AS6210 announce. Many are kept on purpose (backup routes, space announced only in some places).

72.46.64.0/21ARINValid
204.141.107.0/24NTTCOMValid
204.141.110.0/24NTTCOMValid
204.141.128.0/19NTTCOMValid
204.141.128.0/20NTTCOMValid
204.141.128.0/21NTTCOMValid
204.141.128.0/22NTTCOMValid
204.141.132.0/22NTTCOMValid
204.141.156.0/22NTTCOMValid

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.