bgpreport

Network · data from 2026-11-12

AS20231 TWC-20231-NE-KS-C3 - Charter Communications Inc

Registry name: TWC-20231-NE-KS-C3 - Charter Communications Inc, US · not in PeeringDB

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

Announced routes

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

76.58.46.0/23 Valid Other IRR onlyRADB 673 100% 67
192.62.240.0/21 Valid Other IRR onlyRADB 673 100% 67
2602:107:4000::/40 Valid Other IRR onlyRADB 633 100% 69
2602:107:e7c0::/43 Valid Other IRR onlyRADB 633 100% 69
24.166.164.0/22 Valid RIR databaseARIN 672 100% 67
24.166.168.0/21 Valid RIR databaseARIN 672 100% 67
24.166.176.0/20 Valid RIR databaseARIN 672 100% 67
72.129.224.0/19 Valid RIR databaseARIN 672 100% 67
72.133.224.0/20 Valid RIR databaseARIN 672 100% 67

AS-SET

AS20231 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 81 are in fix.csv.

  • Route object: RIR4
  • Route object: not announced77
ChangePrefix or setDetailFull-table peers
Route object: RIR76.58.46.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR192.62.240.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2602:107:4000::/40Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2602:107:e7c0::/43Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

24.27.128.0/19RADBNo ROA
24.159.88.0/21ARINValid
24.159.168.0/22ARINValid
24.159.172.0/23ARINValid
24.241.80.0/20ARINValid
35.130.0.0/19ARINValid
35.132.37.0/24ARINValid
35.133.64.0/18ARINValid
35.151.192.0/20ARINValid
47.4.128.0/18ARINValid
47.27.128.0/18ARINValid
47.28.128.0/18ARINValid
47.44.96.0/21ARINValid
47.48.0.0/18ARINValid
47.231.224.0/22ARINValid
47.233.128.0/17ARINValid
65.26.48.0/21ARINValid
65.26.80.0/20ARINValid
65.31.192.0/19ARINValid
66.168.128.0/20ARINValid
66.232.224.0/23RADBNo ROA
66.232.226.0/23RADBNo ROA
66.244.132.0/23RADBNo ROA
67.48.16.0/20ARINValid
67.53.224.0/21RADBNo ROA
68.113.176.0/20ARINValid
68.116.224.0/20ARINValid
68.117.224.0/20ARINValid
68.189.224.0/20ARINValid
69.23.112.0/20ARINValid
69.23.192.0/19RADBNo ROA
70.92.192.0/18RADBNo ROA
70.94.0.0/17ARINValid
70.118.192.0/18ARINValid
71.8.192.0/20ARINValid
71.8.208.0/20ARINValid
71.8.224.0/20ARINValid
71.8.240.0/21ARINValid
71.8.248.0/21ARINValid
71.85.160.0/19ARINValid
72.135.0.0/19ARINValid
72.135.96.0/20ARINValid
75.81.0.0/18ARINValid
75.81.128.0/19ARINValid
75.87.128.0/18ARINValid
75.135.0.0/18ARINValid
75.135.192.0/18ARINValid
75.141.42.0/24ARINValid
76.84.0.0/16ARINValid
76.92.112.0/20ARINValid
76.92.128.0/17ARINValid
96.36.192.0/19ARINValid
96.40.0.0/19ARINValid
97.92.128.0/19ARINValid
97.92.160.0/20ARINValid
97.92.176.0/20ARINValid
108.167.64.0/20ARINValid
150.181.18.0/23ARINValid
150.224.235.0/24ARINValid
159.111.226.0/23ARINValid
173.40.248.0/22ARINValid
173.41.64.0/21ARINValid
192.25.139.0/24RADBNo ROA
192.61.244.0/23ARINValid
192.61.253.0/24ARINValid
192.62.148.0/23ARINValid
192.62.158.0/24ARINValid
198.190.199.0/24RADBNo ROA
204.194.250.0/24RADBNo ROA
204.194.251.0/24RADBNo ROA
2600:6c4c::/32ARINValid
2600:6c4d::/32ARINValid
2600:6c7f:9030::/48ARINValid
2600:6c81::/32ARINValid
2602:104:3::/48ARINValid
2602:107:5300::/40ARINValid
2602:10e:5::/48ARINValid

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.