Observed topology
AS11232 MIDCO-NET
Residential ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS11232: 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 | 2,921 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 993 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 537 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 439 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 349 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 234 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 98 |
| AS34927 | iFog GmbH | Hosting | IPv4 IPv6 | 72 |
| AS852 | TELUS Communications Inc. | Residential | IPv4 IPv6 | 29 |
| AS11164 | Internet2 | Education | IPv4 | 21 |
Transit
Downstream networks
Networks for which AS11232 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS11055 | Midcontinent Communications | Residential | IPv4 IPv6 | 645 |
| AS23260 | Midcontinent Communications | Unclassified | IPv4 IPv6 | 620 |
| AS14263 | South Dakota State Government | Unclassified | IPv4 IPv6 | 491 |
| AS16739 | Midcontinent Communications | Unclassified | IPv4 | 455 |
| AS46206 | Sanford Health | Unclassified | IPv4 | 328 |
| AS12092 | Sonifi Solutions, Inc. | Unclassified | IPv4 | 260 |
| AS25754 | Blueprint America, Inc. | Unclassified | IPv4 | 259 |
| AS32442 | Marco Technologies LLC | Unclassified | IPv4 | 244 |
| AS33178 | Cable Services, Inc. | Unclassified | IPv4 | 195 |
| AS47071 | CHR SOLUTIONS INC | Unclassified | IPv4 | 188 |
Adjacency
Adjacent networks
Every AS seen directly next to AS11232 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 8,535 |
| AS14263 | South Dakota State Government | Unclassified | IPv4 IPv6 | 2,756 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,493 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 1,155 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 1,075 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,057 |
| AS11055 | Midcontinent Communications | Residential | IPv4 IPv6 | 645 |
| AS23260 | Midcontinent Communications | Unclassified | IPv4 IPv6 | 620 |
| AS16739 | Midcontinent Communications | Unclassified | IPv4 | 455 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 436 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-11 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.47M 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.