Observed topology
AS6181 FUSE-NET - Cincinnati Bell Telephone Company LLC
Residential ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS6181: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 5,556 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 598 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 560 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 557 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 324 |
| AS20205 | Amplex Electric, Inc. | Residential | IPv4 IPv6 | 118 |
Transit
Downstream networks
Networks for which AS6181 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS27365 | Cengage Learning, Inc. | Unclassified | IPv4 | 1,717 |
| AS30035 | Mobilcomm, Inc | Unclassified | IPv4 | 1,040 |
| AS30059 | Zimcom Network Solutions Inc. | Unclassified | IPv4 | 825 |
| AS17089 | Cincinnati Children's Hospital Medical Center | Unclassified | IPv4 | 434 |
| AS46812 | London Computer Systems, Inc | Unclassified | IPv4 | 378 |
| AS26804 | CBTS Technology Solutions LLC | Unclassified | IPv4 | 333 |
| AS18527 | UC Health, LLC | Unclassified | IPv4 | 325 |
| AS62533 | Ascendum-IMS, LLC | Unclassified | IPv4 | 321 |
| AS19558 | Kettering Medical Center | Unclassified | IPv4 | 320 |
| AS400436 | Kentucky Communications Network Authority (KCNA) | Unclassified | IPv4 | 260 |
Adjacency
Adjacent networks
Every AS seen directly next to AS6181 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 12,774 |
| AS27365 | Cengage Learning, Inc. | Unclassified | IPv4 | 1,717 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,422 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 1,288 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 1,165 |
| AS30035 | Mobilcomm, Inc | Unclassified | IPv4 | 1,040 |
| AS30059 | Zimcom Network Solutions Inc. | Unclassified | IPv4 | 825 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 642 |
| AS17089 | Cincinnati Children's Hospital Medical Center | Unclassified | IPv4 | 434 |
| AS46812 | London Computer Systems, Inc | Unclassified | IPv4 | 378 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.