asn.dev

Observed topology

AS26459 TTD-ASN-01

Unclassified APNIC

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS26459: 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
AS6461Zayo BandwidthTransitIPv4 IPv6655
AS3356Level 3 Parent, LLCTransitIPv4 IPv6415
AS6939Hurricane Electric LLCTransitIPv487
AS9293NTT Com Asia LimitedUnclassifiedIPv445
AS24482SG.GSHostingIPv411
AS49915Megaport (UK) LimitedUnclassifiedIPv411
AS293ESnetUnclassifiedIPv49
AS37721Virtual Technologies & SolutionsResidentialIPv47
AS9002RETN LimitedUnclassifiedIPv46
AS3130RGnet OUUnclassifiedIPv42

All 15 upstreams →

Transit

Downstream networks

inferred

Networks for which AS26459 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 15

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv6655
AS3356Level 3 Parent, LLCTransitIPv4 IPv6415
AS6939Hurricane Electric LLCTransitIPv487
AS9293NTT Com Asia LimitedUnclassifiedIPv445
AS24482SG.GSHostingIPv411
AS49915Megaport (UK) LimitedUnclassifiedIPv411
AS293ESnetUnclassifiedIPv49
AS37721Virtual Technologies & SolutionsResidentialIPv47
AS9002RETN LimitedUnclassifiedIPv46
AS3130RGnet OUUnclassifiedIPv42

All 15 adjacent →

Provenance

Where this comes from

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