asn.dev

Observed topology

AS36459 GITHUB

Hosting ARIN

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS36459: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6502
AS6461Zayo BandwidthTransitIPv4 IPv6385
AS6939Hurricane Electric LLCTransitIPv4 IPv6205
AS3257GTT Communications Inc.TransitIPv4 IPv6186
AS5405Inter.link GmbHUnclassifiedIPv4 IPv687
AS2914NTT America, Inc.TransitIPv4 IPv674
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv623
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv614
AS42708Glesys ABUnclassifiedIPv4 IPv68
AS3216PJSC "Vimpelcom"MobileIPv47

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6502
AS6461Zayo BandwidthTransitIPv4 IPv6385
AS6939Hurricane Electric LLCTransitIPv4 IPv6205
AS3257GTT Communications Inc.TransitIPv4 IPv6186
AS5405Inter.link GmbHUnclassifiedIPv4 IPv687
AS2914NTT America, Inc.TransitIPv4 IPv674
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv623
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv614
AS42708Glesys ABUnclassifiedIPv4 IPv68
AS3216PJSC "Vimpelcom"MobileIPv47

Provenance

Where this comes from

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