bgpreport

Network · data from 2026-11-12

AS17060 E-NETWORKS - NBCUniversal

Registry name: E-NETWORKS - NBCUniversal, US · not in PeeringDB

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

Announced routes

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

64.129.180.0/24 No ROA None 667 99% 67
70.39.40.0/24 No ROA Nonecovered by 70.39.32.0/19 2 0%low visibility 2
70.39.41.0/24 No ROA Nonecovered by 70.39.32.0/19 2 0%low visibility 2
70.39.37.0/24 No ROA Other IRR onlyRADB 673 100% 67
70.39.34.0/24 No ROA RIR databaseARIN 671 100% 67
50.239.57.0/24 Valid None 672 100% 67
70.39.36.0/24 Valid RIR databaseARIN 669 99% 67

AS-SET

AS17060 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 14 are in fix.csv.

  • ROA: none5
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none64.129.180.0/24No ROA covers it. Add a ROA for AS17060, maxLength 24.667 of 673
Route object: none64.129.180.0/24No route object for it. Add a route object with origin AS17060 in the RIR database for the space.667 of 673
ROA: none70.39.40.0/24No ROA covers it. Add a ROA for AS17060, maxLength 24.2 of 673
Route object: none70.39.40.0/24No route object for it. A route object for 70.39.32.0/19 with origin AS17060 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17060 in the RIR database for the space.2 of 673
ROA: none70.39.41.0/24No ROA covers it. Add a ROA for AS17060, maxLength 24.2 of 673
Route object: none70.39.41.0/24No route object for it. A route object for 70.39.32.0/19 with origin AS17060 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17060 in the RIR database for the space.2 of 673
ROA: none70.39.37.0/24No ROA covers it. Add a ROA for AS17060, maxLength 24.673 of 673
Route object: RIR70.39.37.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none70.39.34.0/24No ROA covers it. Add a ROA for AS17060, maxLength 24.671 of 673
Route object: none50.239.57.0/24No route object for it. Add a route object with origin AS17060 in the RIR database for the space.672 of 673

Route objects not announced

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

70.39.32.0/19RADBNo ROA
208.78.120.0/21RADBNo ROA
208.88.208.0/21RADBNo ROA
208.88.208.0/23RADBNo 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.