bgpreport

Network · data from 2026-11-12

AS40294 CHARTER-40294-DC - Charter Communications LLC

Registry name: CHARTER-40294-DC - Charter Communications LLC, US · not in PeeringDB

47IPv4 routes 42.6% RPKI valid · 19.1% with a route object
2IPv6 routes 100.0% RPKI valid · 0.0% with a route object
20RPKI invalid 17 origin · 3 maxLength
7No ROA 40 with no route object for this origin
32Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS40294, seen from no peer

Announced routes

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

98.8.64.0/20 Invalid: origin None 1 0%low visibility 1
98.8.76.0/22 Invalid: origin None 1 0%low visibility 1
98.8.80.0/20 Invalid: origin None 1 0%low visibility 1
98.8.80.0/22 Invalid: origin None 1 0%low visibility 1
98.8.92.0/23 Invalid: origin None 1 0%low visibility 1
98.8.96.0/22 Invalid: origin None 1 0%low visibility 1
98.9.96.0/20 Invalid: origin None 1 0%low visibility 1
98.9.98.0/24 Invalid: origin None 1 0%low visibility 1
98.9.252.0/22 Invalid: origin None 1 0%low visibility 1
134.13.120.0/22 Invalid: origin None 1 0%low visibility 1
134.13.124.0/22 Invalid: origin None 1 0%low visibility 1
134.13.128.0/19 Invalid: origin None 1 0%low visibility 1
134.13.192.0/19 Invalid: origin None 1 0%low visibility 1
150.181.104.0/23 Invalid: origin None 1 0%low visibility 1
150.181.106.0/23 Invalid: origin None 1 0%low visibility 1
150.181.112.0/21 Invalid: origin None 1 0%low visibility 1
150.181.120.0/21 Invalid: origin None 1 0%low visibility 1
47.43.92.0/23 Invalid: maxLength None 53 8%low visibility 31
47.43.92.0/24 Invalid: maxLength None 53 8%low visibility 31
47.43.93.0/24 Invalid: maxLength None 53 8%low visibility 31
24.169.168.0/23 No ROA None 1 0%low visibility 1
24.169.184.0/24 No ROA None 1 0%low visibility 1
24.169.188.0/24 No ROA None 1 0%low visibility 1
24.169.190.0/24 No ROA None 1 0%low visibility 1
24.169.191.0/24 No ROA None 1 0%low visibility 1
47.43.112.0/21 No ROA None 1 0%low visibility 1
47.43.120.0/21 No ROA None 1 0%low visibility 1
47.43.16.0/21 Valid None 673 100% 67
47.43.32.0/20 Valid None 673 100% 67
47.43.34.0/24 Valid None 673 100% 67
47.43.48.0/20 Valid None 673 100% 67
47.43.80.0/21 Valid None 673 100% 67
47.43.88.0/21 Valid None 673 100% 67
98.7.128.0/19 Valid None 673 100% 67
98.7.160.0/19 Valid None 673 100% 67
98.8.40.0/22 Valid None 673 100% 67
98.8.44.0/22 Valid None 673 100% 67
47.43.24.0/21 Valid None 670 100% 67
2600:6c7f:9330::/44 Valid None 633 100% 69
2600:6c7f:9340::/44 Valid None 633 100% 69
98.8.56.0/22 Valid Other IRR onlyRADB 673 100% 67
98.8.60.0/22 Valid Other IRR onlyRADB 673 100% 67
47.43.68.0/22 Valid RIR databaseARIN 673 100% 67
47.43.72.0/22 Valid RIR databaseARIN 673 100% 67
69.134.192.0/19 Valid RIR databaseARIN 1 0%low visibility 1
98.8.128.0/20 Valid RIR databaseARIN 1 0%low visibility 1
98.8.144.0/20 Valid RIR databaseARIN 1 0%low visibility 1
98.8.160.0/20 Valid RIR databaseARIN 1 0%low visibility 1
98.8.176.0/20 Valid RIR databaseARIN 1 0%low visibility 1

AS-SET

AS40294 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 74 are in fix.csv.

  • ROA: origin17
  • ROA: maxLength3
  • ROA: none7
  • Route object: none40
  • Route object: RIR2
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: origin98.8.64.0/20ROAs covering it name AS7843, not AS40294. If AS40294 should announce it, add a ROA for AS40294.1 of 673
Route object: none98.8.64.0/20No route object for it. Add a route object with origin AS40294 in the RIR database for the space.1 of 673
ROA: origin98.8.76.0/22ROAs covering it name AS7843, not AS40294. If AS40294 should announce it, add a ROA for AS40294.1 of 673
Route object: none98.8.76.0/22No route object for it. Add a route object with origin AS40294 in the RIR database for the space.1 of 673
ROA: origin98.8.80.0/20ROAs covering it name AS7843, not AS40294. If AS40294 should announce it, add a ROA for AS40294.1 of 673
Route object: none98.8.80.0/20No route object for it. Add a route object with origin AS40294 in the RIR database for the space.1 of 673
ROA: origin98.8.80.0/22ROAs covering it name AS7843, not AS40294. If AS40294 should announce it, add a ROA for AS40294.1 of 673
Route object: none98.8.80.0/22No route object for it. Add a route object with origin AS40294 in the RIR database for the space.1 of 673
ROA: origin98.8.92.0/23ROAs covering it name AS7843, not AS40294. If AS40294 should announce it, add a ROA for AS40294.1 of 673
Route object: none98.8.92.0/23No route object for it. Add a route object with origin AS40294 in the RIR database for the space.1 of 673
ROA: origin98.8.96.0/22ROAs covering it name AS7843, not AS40294. If AS40294 should announce it, add a ROA for AS40294.1 of 673
Route object: none98.8.96.0/22No route object for it. Add a route object with origin AS40294 in the RIR database for the space.1 of 673
ROA: origin98.9.96.0/20ROAs covering it name AS7843, not AS40294. If AS40294 should announce it, add a ROA for AS40294.1 of 673
Route object: none98.9.96.0/20No route object for it. Add a route object with origin AS40294 in the RIR database for the space.1 of 673
ROA: origin98.9.98.0/24ROAs covering it name AS7843, not AS40294. If AS40294 should announce it, add a ROA for AS40294.1 of 673
Route object: none98.9.98.0/24No route object for it. Add a route object with origin AS40294 in the RIR database for the space.1 of 673
ROA: origin98.9.252.0/22ROAs covering it name AS7843, not AS40294. If AS40294 should announce it, add a ROA for AS40294.1 of 673
Route object: none98.9.252.0/22No route object for it. Add a route object with origin AS40294 in the RIR database for the space.1 of 673
ROA: origin134.13.120.0/22An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS40294 should announce it, add a ROA for AS40294.1 of 673
Route object: none134.13.120.0/22No route object for it. Add a route object with origin AS40294 in the RIR database for the space.1 of 673
ROA: origin134.13.124.0/22An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS40294 should announce it, add a ROA for AS40294.1 of 673
Route object: none134.13.124.0/22No route object for it. Add a route object with origin AS40294 in the RIR database for the space.1 of 673
ROA: origin134.13.128.0/19An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS40294 should announce it, add a ROA for AS40294.1 of 673
Route object: none134.13.128.0/19No route object for it. Add a route object with origin AS40294 in the RIR database for the space.1 of 673
ROA: origin134.13.192.0/19An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS40294 should announce it, add a ROA for AS40294.1 of 673
Route object: none134.13.192.0/19No route object for it. Add a route object with origin AS40294 in the RIR database for the space.1 of 673
ROA: origin150.181.104.0/23An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS40294 should announce it, add a ROA for AS40294.1 of 673
Route object: none150.181.104.0/23No route object for it. Add a route object with origin AS40294 in the RIR database for the space.1 of 673
ROA: origin150.181.106.0/23An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS40294 should announce it, add a ROA for AS40294.1 of 673
Route object: none150.181.106.0/23No route object for it. Add a route object with origin AS40294 in the RIR database for the space.1 of 673
ROA: origin150.181.112.0/21An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS40294 should announce it, add a ROA for AS40294.1 of 673
Route object: none150.181.112.0/21No route object for it. Add a route object with origin AS40294 in the RIR database for the space.1 of 673
ROA: origin150.181.120.0/21An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS40294 should announce it, add a ROA for AS40294.1 of 673
Route object: none150.181.120.0/21No route object for it. Add a route object with origin AS40294 in the RIR database for the space.1 of 673
ROA: maxLength47.43.92.0/23ROA 47.43.88.0/21 AS40294 has maxLength 21; the route is a /23. Raise the maxLength, or add a ROA for 47.43.92.0/23.53 of 673
Route object: none47.43.92.0/23No route object for it. Add a route object with origin AS40294 in the RIR database for the space.53 of 673
ROA: maxLength47.43.92.0/24ROA 47.43.88.0/21 AS40294 has maxLength 21; the route is a /24. Raise the maxLength, or add a ROA for 47.43.92.0/24.53 of 673
Route object: none47.43.92.0/24No route object for it. Add a route object with origin AS40294 in the RIR database for the space.53 of 673
ROA: maxLength47.43.93.0/24ROA 47.43.88.0/21 AS40294 has maxLength 21; the route is a /24. Raise the maxLength, or add a ROA for 47.43.93.0/24.53 of 673
Route object: none47.43.93.0/24No route object for it. Add a route object with origin AS40294 in the RIR database for the space.53 of 673
ROA: none24.169.168.0/23No ROA covers it. Add a ROA for AS40294, maxLength 23.1 of 673
Route object: none24.169.168.0/23No route object for it. Add a route object with origin AS40294 in the RIR database for the space.1 of 673
ROA: none24.169.184.0/24No ROA covers it. Add a ROA for AS40294, maxLength 24.1 of 673
Route object: none24.169.184.0/24No route object for it. Add a route object with origin AS40294 in the RIR database for the space.1 of 673
ROA: none24.169.188.0/24No ROA covers it. Add a ROA for AS40294, maxLength 24.1 of 673
Route object: none24.169.188.0/24No route object for it. Add a route object with origin AS40294 in the RIR database for the space.1 of 673
ROA: none24.169.190.0/24No ROA covers it. Add a ROA for AS40294, maxLength 24.1 of 673
Route object: none24.169.190.0/24No route object for it. Add a route object with origin AS40294 in the RIR database for the space.1 of 673
ROA: none24.169.191.0/24No ROA covers it. Add a ROA for AS40294, maxLength 24.1 of 673
Route object: none24.169.191.0/24No route object for it. Add a route object with origin AS40294 in the RIR database for the space.1 of 673
ROA: none47.43.112.0/21No ROA covers it. Add a ROA for AS40294, maxLength 21.1 of 673
Route object: none47.43.112.0/21No route object for it. Add a route object with origin AS40294 in the RIR database for the space.1 of 673
ROA: none47.43.120.0/21No ROA covers it. Add a ROA for AS40294, maxLength 21.1 of 673
Route object: none47.43.120.0/21No route object for it. Add a route object with origin AS40294 in the RIR database for the space.1 of 673
Route object: none47.43.16.0/21No route object for it. Add a route object with origin AS40294 in the RIR database for the space.673 of 673
Route object: none47.43.32.0/20No route object for it. Add a route object with origin AS40294 in the RIR database for the space.673 of 673
Route object: none47.43.34.0/24No route object for it. Add a route object with origin AS40294 in the RIR database for the space.673 of 673
Route object: none47.43.48.0/20No route object for it. Add a route object with origin AS40294 in the RIR database for the space.673 of 673
Route object: none47.43.80.0/21No route object for it. Add a route object with origin AS40294 in the RIR database for the space.673 of 673
Route object: none47.43.88.0/21No route object for it. Add a route object with origin AS40294 in the RIR database for the space.673 of 673
Route object: none98.7.128.0/19No route object for it. Add a route object with origin AS40294 in the RIR database for the space.673 of 673
Route object: none98.7.160.0/19No route object for it. Add a route object with origin AS40294 in the RIR database for the space.673 of 673
Route object: none98.8.40.0/22No route object for it. Add a route object with origin AS40294 in the RIR database for the space.673 of 673
Route object: none98.8.44.0/22No route object for it. Add a route object with origin AS40294 in the RIR database for the space.673 of 673
Route object: none47.43.24.0/21No route object for it. Add a route object with origin AS40294 in the RIR database for the space.670 of 673
Route object: none2600:6c7f:9330::/44No route object for it. Add a route object with origin AS40294 in the RIR database for the space.633 of 636
Route object: none2600:6c7f:9340::/44No route object for it. Add a route object with origin AS40294 in the RIR database for the space.633 of 636
Route object: RIR98.8.56.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR98.8.60.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

24.30.215.0/24ARINValid
69.134.128.0/17ARINValid
69.134.128.0/18ARINValid
69.134.160.0/19ARINValid
69.134.234.0/24ARINValid

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.