bgpreport

Network · data from 2026-11-12

AS3456 TWC-3456-IT - Charter Communications Inc

Registry name: TWC-3456-IT - Charter Communications Inc, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS3456, 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.
2600:5c00:21cf::/48 Valid None 633 100% 69
2600:5c00:21d1::/48 Valid None 633 100% 69
2600:5c00:2304::/48 Valid None 633 100% 69
2600:5c00:2541::/48 Valid None 633 100% 69
2001:1998:3100::/48 Valid Nonecovered by 2001:1998:3000::/36 28 4%low visibility 16
67.48.224.0/19 Valid Other IRR onlyRADB 673 100% 67
142.136.0.0/16 Valid Other IRR onlyRADB 673 100% 67
165.237.0.0/16 Valid Other IRR onlyRADB 673 100% 67
165.237.14.0/24 Valid Other IRR onlyRADB 673 100% 67
165.237.15.0/24 Valid Other IRR onlyRADB 673 100% 67
192.219.231.0/24 Valid Other IRR onlyRADB 673 100% 67
204.29.131.0/24 Valid Other IRR onlyRADB 673 100% 67
204.235.112.0/21 Valid Other IRR onlyRADB 673 100% 67
204.235.120.0/23 Valid Other IRR onlyRADB 673 100% 67
2001:1998:2000::/36 Valid Other IRR onlyRADB 633 100% 69
2001:1998:3000::/36 Valid Other IRR onlyRADB 633 100% 69

AS-SET

AS3456 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 16 are in fix.csv.

  • Route object: none5
  • Route object: RIR11
ChangePrefix or setDetailFull-table peers
Route object: none2600:5c00:21cf::/48No route object for it. Add a route object with origin AS3456 in the RIR database for the space.633 of 636
Route object: none2600:5c00:21d1::/48No route object for it. Add a route object with origin AS3456 in the RIR database for the space.633 of 636
Route object: none2600:5c00:2304::/48No route object for it. Add a route object with origin AS3456 in the RIR database for the space.633 of 636
Route object: none2600:5c00:2541::/48No route object for it. Add a route object with origin AS3456 in the RIR database for the space.633 of 636
Route object: none2001:1998:3100::/48No route object for it. A route object for 2001:1998:3000::/36 with origin AS3456 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3456 in the RIR database for the space.28 of 636
Route object: RIR67.48.224.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR142.136.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR165.237.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR165.237.14.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR165.237.15.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR192.219.231.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR204.29.131.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR204.235.112.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR204.235.120.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2001:1998:2000::/36Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2001:1998:3000::/36Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

Every route object with origin AS3456 is announced.

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.