Observed topology
AS12243 WADDELL
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS12243: 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 |
|---|---|---|---|---|
| AS394968 | Quality Technology Services, LLC | Unclassified | IPv4 | 234 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 147 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 80 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 60 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 28 |
| AS20205 | Amplex Electric, Inc. | Residential | IPv4 IPv6 | 8 |
| AS25091 | IP-Max SA | Unclassified | IPv6 | 2 |
Transit
Downstream networks
Networks for which AS12243 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS22781 | Strong Technology, LLC. | Hosting | IPv4 IPv6 | 328 |
Adjacency
Adjacent networks
Every AS seen directly next to AS12243 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 348 |
| AS22781 | Strong Technology, LLC. | Hosting | IPv4 IPv6 | 328 |
| AS394968 | Quality Technology Services, LLC | Unclassified | IPv4 | 234 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 116 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 91 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 80 |
| AS20205 | Amplex Electric, Inc. | Residential | IPv4 IPv6 | 13 |
| AS25091 | IP-Max SA | Unclassified | IPv6 | 5 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-27 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.06M 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.