Observed topology
AS12200 RACKSPACE - Rackspace Hosting
Hosting ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS12200: 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 |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 213 |
| AS32787 | Akamai Technologies, Inc. | Hosting | IPv4 | 180 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 140 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 91 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 | 85 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 72 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 16 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 8 |
| AS293 | ESnet | Unclassified | IPv4 | 5 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 5 |
Transit
Downstream networks
Networks for which AS12200 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS33070 | Rackspace Hosting | Hosting | IPv4 IPv6 | 6,034 |
| AS22205 | DataPipe, Inc. | Unclassified | IPv4 IPv6 | 3,963 |
| AS19994 | Rackspace Hosting | Hosting | IPv4 IPv6 | 3,887 |
| AS27357 | Rackspace Hosting | Hosting | IPv4 IPv6 | 2,196 |
| AS15395 | Rackspace Ltd. | Hosting | IPv4 IPv6 | 2,006 |
| AS14492 | DataPipe, Inc. | Hosting | IPv4 IPv6 | 1,080 |
| AS39921 | Rackspace Ltd. | Hosting | IPv4 IPv6 | 552 |
| AS22576 | DataPipe, Inc. | Unclassified | IPv4 | 472 |
| AS16805 | DataPipe, Inc. | Unclassified | IPv4 IPv6 | 444 |
| AS46202 | Michaels Stores, Inc. | Unclassified | IPv4 | 343 |
Adjacency
Adjacent networks
Every AS seen directly next to AS12200 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 7,808 |
| AS33070 | Rackspace Hosting | Hosting | IPv4 IPv6 | 6,034 |
| AS19994 | Rackspace Hosting | Hosting | IPv4 IPv6 | 5,155 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 4,573 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 4,172 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 4,044 |
| AS22205 | DataPipe, Inc. | Unclassified | IPv4 IPv6 | 3,963 |
| AS27357 | Rackspace Hosting | Hosting | IPv4 IPv6 | 3,180 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 3,164 |
| AS15395 | Rackspace Ltd. | Hosting | IPv4 IPv6 | 2,006 |
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.