Observed topology
AS12179 INTERNAP-2BLK
Hosting ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS12179: 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 |
|---|---|---|---|---|
| AS1828 | Unitas Global | Unclassified | IPv4 IPv6 | 1,804 |
Transit
Downstream networks
Networks for which AS12179 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS19133 | Bird Hosting Inc. | Hosting | IPv4 IPv6 | 506 |
| AS32475 | Internap Holding LLC | Hosting | IPv4 IPv6 | 396 |
| AS13791 | Unitas Global | Hosting | IPv4 | 354 |
| AS22717 | Halliburton Company | Unclassified | IPv4 | 230 |
| AS46282 | Boeing Distribution, Inc. | Unclassified | IPv4 | 141 |
| AS13443 | LinkedIn Corporation | Unclassified | IPv4 IPv6 | 136 |
| AS32312 | Telecommunication Systems, Inc. | Unclassified | IPv4 | 118 |
| AS63018 | Dedicated.com | Hosting | IPv4 IPv6 | 96 |
| AS395110 | AeroData, Inc. | Unclassified | IPv4 | 68 |
| AS12235 | SmartEdgeNet LLC | Unclassified | IPv4 | 59 |
Adjacency
Adjacent networks
Every AS seen directly next to AS12179 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1828 | Unitas Global | Unclassified | IPv4 IPv6 | 4,274 |
| AS19133 | Bird Hosting Inc. | Hosting | IPv4 IPv6 | 506 |
| AS32475 | Internap Holding LLC | Hosting | IPv4 IPv6 | 396 |
| AS13791 | Unitas Global | Hosting | IPv4 | 354 |
| AS22717 | Halliburton Company | Unclassified | IPv4 | 230 |
| AS46282 | Boeing Distribution, Inc. | Unclassified | IPv4 | 141 |
| AS13443 | LinkedIn Corporation | Unclassified | IPv4 IPv6 | 136 |
| AS32312 | Telecommunication Systems, Inc. | Unclassified | IPv4 | 118 |
| AS63018 | Dedicated.com | Hosting | IPv4 IPv6 | 96 |
| AS395110 | AeroData, Inc. | Unclassified | IPv4 | 68 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-24 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 72.94M 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.