asn.dev

Observed topology

AS12243 WADDELL - Waddell Solutions Group LLC

Unclassified ARIN

Upstreams 7 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 7
Adjacent (IPv6) 7
Upstream graph Who carries AS12243, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS12243 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

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.

ASNetworkTypeFamiliesPaths seen
AS394968Quality Technology Services, LLCUnclassifiedIPv4240
AS6939Hurricane Electric LLCTransitIPv4 IPv6145
AS1299Arelion Sweden ABTransitIPv4 IPv680
AS174Cogent Communications, LLCTransitIPv4 IPv667
AS3356Level 3 Parent, LLCTransitIPv428
AS20205Amplex Electric, Inc.ResidentialIPv4 IPv68
AS25091IP-Max SAUnclassifiedIPv62

Transit

Downstream networks

inferred

Networks for which AS12243 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS22781Strong Technology, LLC.HostingIPv4 IPv6326

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS12243 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6343
AS22781Strong Technology, LLC.HostingIPv4 IPv6326
AS394968Quality Technology Services, LLCUnclassifiedIPv4240
AS174Cogent Communications, LLCTransitIPv4 IPv6124
AS3356Level 3 Parent, LLCTransitIPv4 IPv691
AS1299Arelion Sweden ABTransitIPv4 IPv680
AS20205Amplex Electric, Inc.ResidentialIPv4 IPv613
AS25091IP-Max SAUnclassifiedIPv65

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.