bgpreport

Network · data from 2026-11-12

AS19606 NLSNMEDIA - THE NIELSEN COMPANY (US), LLC

Registry name: NLSNMEDIA - THE NIELSEN COMPANY (US), LLC, US · not in PeeringDB

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

Announced routes

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

162.33.64.0/24 No ROA None 673 100% 67
208.64.96.0/23 No ROA Nonecovered by 208.64.96.0/22 673 100% 67
209.242.88.0/24 No ROA Nonecovered by 209.242.88.0/22 673 100% 67
209.242.89.0/24 No ROA Nonecovered by 209.242.88.0/22 673 100% 67
209.242.90.0/24 No ROA Nonecovered by 209.242.88.0/22 673 100% 67
209.242.91.0/24 No ROA Nonecovered by 209.242.88.0/22 673 100% 67
206.113.192.0/24 No ROA Other IRR onlyRADB 673 100% 67
206.113.193.0/24 No ROA Other IRR onlyRADB 673 100% 67
208.64.99.0/24 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS19606 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 30 are in fix.csv.

  • ROA: none9
  • Route object: none6
  • Route object: RIR3
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none162.33.64.0/24No ROA covers it. Add a ROA for AS19606, maxLength 24.673 of 673
Route object: none162.33.64.0/24No route object for it. Add a route object with origin AS19606 in the RIR database for the space.673 of 673
ROA: none208.64.96.0/23No ROA covers it. Add a ROA for AS19606, maxLength 23.673 of 673
Route object: none208.64.96.0/23No route object for it. A route object for 208.64.96.0/22 with origin AS19606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19606 in the RIR database for the space.673 of 673
ROA: none209.242.88.0/24No ROA covers it. Add a ROA for AS19606, maxLength 24.673 of 673
Route object: none209.242.88.0/24No route object for it. A route object for 209.242.88.0/22 with origin AS19606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19606 in the RIR database for the space.673 of 673
ROA: none209.242.89.0/24No ROA covers it. Add a ROA for AS19606, maxLength 24.673 of 673
Route object: none209.242.89.0/24No route object for it. A route object for 209.242.88.0/22 with origin AS19606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19606 in the RIR database for the space.673 of 673
ROA: none209.242.90.0/24No ROA covers it. Add a ROA for AS19606, maxLength 24.673 of 673
Route object: none209.242.90.0/24No route object for it. A route object for 209.242.88.0/22 with origin AS19606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19606 in the RIR database for the space.673 of 673
ROA: none209.242.91.0/24No ROA covers it. Add a ROA for AS19606, maxLength 24.673 of 673
Route object: none209.242.91.0/24No route object for it. A route object for 209.242.88.0/22 with origin AS19606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19606 in the RIR database for the space.673 of 673
ROA: none206.113.192.0/24No ROA covers it. Add a ROA for AS19606, maxLength 24.673 of 673
Route object: RIR206.113.192.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none206.113.193.0/24No ROA covers it. Add a ROA for AS19606, maxLength 24.673 of 673
Route object: RIR206.113.193.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none208.64.99.0/24No ROA covers it. Add a ROA for AS19606, maxLength 24.673 of 673
Route object: RIR208.64.99.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

63.114.249.0/24RADBNo ROA
65.196.144.0/24RADBNo ROA
138.108.3.0/24RADBNo ROA
138.108.57.0/24RADBNo ROA
138.108.58.0/24RADBNo ROA
138.108.60.0/24RADBNo ROA
138.108.62.0/24RADBNo ROA
206.113.192.0/23RADBNo ROA
208.64.96.0/22RADBNo ROA
208.64.96.0/24RADBNo ROA
208.64.97.0/24RADBNo ROA
209.242.88.0/22RADBNo 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.