Observed topology
AS19331 TWIN-LAKES
Unclassified ARIN NSP
Transit
Upstream networks
Networks observed carrying traffic for AS19331: 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 AS19331 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS395437 | Highland Communications LLC | Unclassified | IPv4 | 542 |
| AS12261 | DTC Communications, Inc. | Unclassified | IPv4 | 256 |
| AS13543 | City of Cookeville | Unclassified | IPv4 IPv6 | 101 |
| AS36367 | Alchemy Global Networks, LLC | Unclassified | IPv4 | 66 |
| AS395879 | Identity Group Holdings LLC | Unclassified | IPv4 | 66 |
| AS398543 | Carson-Newman University | Unclassified | IPv4 | 66 |
| AS14389 | Cash Express, LLC | Unclassified | IPv4 | 13 |
Adjacency
Adjacent networks
Every AS seen directly next to AS19331 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS11758 | IRIS Networks | Unclassified | IPv4 IPv6 | 1,134 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 886 |
| AS395437 | Highland Communications LLC | Unclassified | IPv4 | 604 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 580 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 274 |
| AS12261 | DTC Communications, Inc. | Unclassified | IPv4 | 256 |
| AS11979 | Bluegrass Network LLC | Unclassified | IPv4 | 201 |
| AS13543 | City of Cookeville | Unclassified | IPv4 IPv6 | 101 |
| AS36367 | Alchemy Global Networks, LLC | Unclassified | IPv4 | 66 |
| AS395879 | Identity Group Holdings LLC | Unclassified | IPv4 | 66 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-29 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.36M 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.