Network · data from 2026-11-12
AS40264 TWC-40264-WI-MN-UPPERMI-C3 - Charter Communications LLC
Registry name: TWC-40264-WI-MN-UPPERMI-C3 - Charter Communications LLC, US · not in PeeringDB
19IPv4 routes
68.4% RPKI valid · 47.4% with a route object
4IPv6 routes
50.0% RPKI valid · 25.0% with a route object
1RPKI invalid
1 origin · 0 maxLength
7No ROA
13 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
3Route objects not announced
registered with origin AS40264, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS40264, 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.
| 97.75.228.0/24 | Invalid: origin | Other origin only | 68 10% |
| 192.104.31.0/24 | No ROA | Other origin only | 673 100% |
| 204.176.194.0/24 | No ROA | Other origin only | 673 100% |
| 208.103.155.0/24 | No ROA | Other origin only | 673 100% |
| 2602:80c:1004::/48 | No ROA | Other origin only | 633 100% |
| 2602:80c:1008::/48 | No ROA | Other origin only | 633 100% |
| 76.58.44.0/24 | No ROA | None | 1 0%low visibility |
| 138.207.2.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
| 47.45.16.0/24 | Valid | None | 673 100% |
| 47.45.59.0/24 | Valid | Other origin only | 673 100% |
| 76.58.8.0/21 | Valid | None | 672 100% |
| 76.58.45.0/24 | Valid | None | 672 100% |
| 76.58.48.0/22 | Valid | None | 672 100% |
| 2602:107:e100::/40 | Valid | None | 633 100% |
| 47.45.46.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 192.62.232.0/21 | Valid | Other IRR onlyRADB | 672 100% |
| 2602:107:4100::/40 | Valid | Other IRR onlyRADB | 633 100% |
| 82.27.4.0/22 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 82.27.12.0/22 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 82.29.16.0/22 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 82.29.32.0/22 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 144.168.16.0/21 | Valid | RIR databaseARIN, RADB | 673 100% |
| 199.15.240.0/21 | Valid | RIR databaseARIN, RADB | 673 100% |
AS-SET
AS40264 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 28 are in fix.csv.
- ROA: origin1
- ROA: none7
- Route object: none13
- Route object: RIR4
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 97.75.228.0/24 | ROAs covering it name AS394365, not AS40264. If AS40264 should announce it, add a ROA for AS40264. |
| Route object: none | 97.75.228.0/24 | Route objects for it name AS394365. Add a route object with origin AS40264 in the RIR database for the space. |
| ROA: none | 192.104.31.0/24 | No ROA covers it. Add a ROA for AS40264, maxLength 24. |
| Route object: none | 192.104.31.0/24 | Route objects for it name AS10796. Add a route object with origin AS40264 in the RIR database for the space. |
| ROA: none | 204.176.194.0/24 | No ROA covers it. Add a ROA for AS40264, maxLength 24. |
| Route object: none | 204.176.194.0/24 | Route objects for it name AS7029, AS10796. Add a route object with origin AS40264 in the RIR database for the space. |
| ROA: none | 208.103.155.0/24 | No ROA covers it. Add a ROA for AS40264, maxLength 24. |
| Route object: none | 208.103.155.0/24 | Route objects for it name AS10796. Add a route object with origin AS40264 in the RIR database for the space. |
| ROA: none | 2602:80c:1004::/48 | No ROA covers it. Add a ROA for AS40264, maxLength 48. |
| Route object: none | 2602:80c:1004::/48 | Route objects for it name AS400013. Add a route object with origin AS40264 in the RIR database for the space. |
| ROA: none | 2602:80c:1008::/48 | No ROA covers it. Add a ROA for AS40264, maxLength 48. |
| Route object: none | 2602:80c:1008::/48 | Route objects for it name AS400013. Add a route object with origin AS40264 in the RIR database for the space. |
| ROA: none | 76.58.44.0/24 | No ROA covers it. Add a ROA for AS40264, maxLength 24. |
| Route object: none | 76.58.44.0/24 | No route object for it. Add a route object with origin AS40264 in the RIR database for the space. |
| ROA: none | 138.207.2.0/23 | No ROA covers it. Add a ROA for AS40264, maxLength 23. |
| Route object: RIR | 138.207.2.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 47.45.16.0/24 | No route object for it. Add a route object with origin AS40264 in the RIR database for the space. |
| Route object: none | 47.45.59.0/24 | Route objects for it name AS10796, AS20115. Add a route object with origin AS40264 in the RIR database for the space. |
| Route object: none | 76.58.8.0/21 | No route object for it. Add a route object with origin AS40264 in the RIR database for the space. |
| Route object: none | 76.58.45.0/24 | No route object for it. Add a route object with origin AS40264 in the RIR database for the space. |
| Route object: none | 76.58.48.0/22 | No route object for it. Add a route object with origin AS40264 in the RIR database for the space. |
| Route object: none | 2602:107:e100::/40 | No route object for it. Add a route object with origin AS40264 in the RIR database for the space. |
| Route object: RIR | 47.45.46.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.62.232.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2602:107:4100::/40 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS40264 whose prefix no peer sees AS40264 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.26.160.0/20 | RADB | No ROA |
| 71.13.163.0/24 | RADB | Valid |
| 2603:60c4::/32 | ARIN | Valid |
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.