asn.dev

Observed topology

AS63270 AERUX-BROADBAND - Aerux LLP

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS63270: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6392
AS1299Arelion Sweden ABTransitIPv4 IPv6377
AS174Cogent Communications, LLCTransitIPv4 IPv6184
AS6939Hurricane Electric LLCTransitIPv4 IPv6173
AS62887WhiteSky Communications, LLC.ResidentialIPv415

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS400229ELEKTRAFI INC.UnclassifiedIPv4394
AS397301Thrive Broadband, LLCUnclassifiedIPv47
AS36207ELEKTRAFI INC.UnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6531
AS1299Arelion Sweden ABTransitIPv4 IPv6513
AS400229ELEKTRAFI INC.UnclassifiedIPv4394
AS174Cogent Communications, LLCTransitIPv4 IPv6246
AS6939Hurricane Electric LLCTransitIPv4 IPv6231
AS62887WhiteSky Communications, LLC.ResidentialIPv423
AS397301Thrive Broadband, LLCUnclassifiedIPv47
AS36207ELEKTRAFI INC.UnclassifiedIPv42

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-10 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 71.97M 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.