Observed topology
AS10796 TWC-10796-MIDWEST
Residential ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS10796: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.
Transit
Downstream networks
Networks for which AS10796 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS26072 | FirstEnergy Corp. | Unclassified | IPv4 IPv6 | 1,264 |
| AS17054 | Expedient | Hosting | IPv4 | 1,250 |
| AS14089 | CanNet Internet Services, Inc. | Unclassified | IPv4 | 829 |
| AS16410 | The Reynolds and Reynolds Company | Hosting | IPv4 | 748 |
| AS397093 | St. Elizabeth Medical Center, Inc. | Unclassified | IPv4 | 618 |
| AS40264 | Charter Communications LLC | Unclassified | IPv4 IPv6 | 613 |
| AS14283 | blueone.net | Unclassified | IPv4 | 598 |
| AS26862 | FULLNET INC | Unclassified | IPv4 | 550 |
| AS29771 | Express LLC | Unclassified | IPv4 | 472 |
| AS26133 | Frankfort Plant Board | Residential | IPv4 | 450 |
Adjacency
Adjacent networks
Every AS seen directly next to AS10796 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS7843 | Charter Communications Inc | Residential | IPv4 IPv6 | 61,799 |
| AS40264 | Charter Communications LLC | Unclassified | IPv4 IPv6 | 6,779 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 4,306 |
| AS17054 | Expedient | Hosting | IPv4 | 1,995 |
| AS26072 | FirstEnergy Corp. | Unclassified | IPv4 IPv6 | 1,264 |
| AS14089 | CanNet Internet Services, Inc. | Unclassified | IPv4 | 829 |
| AS16410 | The Reynolds and Reynolds Company | Hosting | IPv4 | 748 |
| AS397093 | St. Elizabeth Medical Center, Inc. | Unclassified | IPv4 | 618 |
| AS14283 | blueone.net | Unclassified | IPv4 | 598 |
| AS26862 | FULLNET INC | Unclassified | IPv4 | 550 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.25M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.
Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.
Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.