bgpreport

Network · data from 2026-11-12

AS8052 TWC-8052-PEAKVIEW - Charter Communications Inc

Registry name: TWC-8052-PEAKVIEW - Charter Communications Inc, US · not in PeeringDB

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

Announced routes

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

69.76.82.0/24 Valid None 673 100% 67
69.76.105.0/24 Valid None 673 100% 67
69.76.107.0/24 Valid None 673 100% 67
69.76.108.0/22 Valid None 673 100% 67
69.76.112.0/21 Valid None 673 100% 67
69.76.120.0/22 Valid None 673 100% 67
69.134.132.0/22 Valid None 673 100% 67
69.134.222.0/24 Valid None 673 100% 67
72.129.192.0/24 Valid None 673 100% 67
72.129.208.0/21 Valid None 673 100% 67
72.129.222.0/24 Valid None 673 100% 67
72.129.223.0/24 Valid None 673 100% 67
107.14.76.0/24 Valid None 673 100% 67
107.14.77.0/24 Valid None 673 100% 67
107.14.88.0/24 Valid None 673 100% 67
107.14.89.0/24 Valid None 673 100% 67
107.14.94.0/24 Valid None 673 100% 67
107.14.95.0/24 Valid None 673 100% 67
159.111.48.0/20 Valid None 673 100% 67
2001:1998:890::/44 Valid None 634 100% 69
107.14.90.0/23 Valid None 2 0%low visibility 2
107.14.92.0/23 Valid None 2 0%low visibility 2

AS-SET

AS8052 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 34 are in fix.csv.

  • Route object: none22
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
Route object: none69.76.82.0/24No route object for it. Add a route object with origin AS8052 in the RIR database for the space.673 of 673
Route object: none69.76.105.0/24No route object for it. Add a route object with origin AS8052 in the RIR database for the space.673 of 673
Route object: none69.76.107.0/24No route object for it. Add a route object with origin AS8052 in the RIR database for the space.673 of 673
Route object: none69.76.108.0/22No route object for it. Add a route object with origin AS8052 in the RIR database for the space.673 of 673
Route object: none69.76.112.0/21No route object for it. Add a route object with origin AS8052 in the RIR database for the space.673 of 673
Route object: none69.76.120.0/22No route object for it. Add a route object with origin AS8052 in the RIR database for the space.673 of 673
Route object: none69.134.132.0/22No route object for it. Add a route object with origin AS8052 in the RIR database for the space.673 of 673
Route object: none69.134.222.0/24No route object for it. Add a route object with origin AS8052 in the RIR database for the space.673 of 673
Route object: none72.129.192.0/24No route object for it. Add a route object with origin AS8052 in the RIR database for the space.673 of 673
Route object: none72.129.208.0/21No route object for it. Add a route object with origin AS8052 in the RIR database for the space.673 of 673
Route object: none72.129.222.0/24No route object for it. Add a route object with origin AS8052 in the RIR database for the space.673 of 673
Route object: none72.129.223.0/24No route object for it. Add a route object with origin AS8052 in the RIR database for the space.673 of 673
Route object: none107.14.76.0/24No route object for it. Add a route object with origin AS8052 in the RIR database for the space.673 of 673
Route object: none107.14.77.0/24No route object for it. Add a route object with origin AS8052 in the RIR database for the space.673 of 673
Route object: none107.14.88.0/24No route object for it. Add a route object with origin AS8052 in the RIR database for the space.673 of 673
Route object: none107.14.89.0/24No route object for it. Add a route object with origin AS8052 in the RIR database for the space.673 of 673
Route object: none107.14.94.0/24No route object for it. Add a route object with origin AS8052 in the RIR database for the space.673 of 673
Route object: none107.14.95.0/24No route object for it. Add a route object with origin AS8052 in the RIR database for the space.673 of 673
Route object: none159.111.48.0/20No route object for it. Add a route object with origin AS8052 in the RIR database for the space.673 of 673
Route object: none2001:1998:890::/44No route object for it. Add a route object with origin AS8052 in the RIR database for the space.634 of 636
Route object: none107.14.90.0/23No route object for it. Add a route object with origin AS8052 in the RIR database for the space.2 of 673
Route object: none107.14.92.0/23No route object for it. Add a route object with origin AS8052 in the RIR database for the space.2 of 673

Route objects not announced

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

63.88.132.0/24RADBNo ROA
63.88.133.0/24RADBNo ROA
63.167.208.0/20RADBNo ROA
64.212.103.0/24RADBNo ROA
64.212.167.0/24RADBNo ROA
204.61.192.0/21RADBNo ROA
204.61.200.0/22RADBNo ROA
204.61.204.0/23RADBNo ROA
204.61.206.0/24RADBNo ROA
208.3.248.0/22RADBNo ROA
208.5.176.0/20RADBNo ROA
208.5.186.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.