asn.dev

Observed topology

AS26464 JOYENT-INC-US - Joyent, Inc.

Hosting ARIN

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

Transit

Upstream networks

All 30

Networks observed carrying traffic for AS26464: 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
AS4766Korea TelecomMobileIPv41,811
AS1299Arelion Sweden ABTransitIPv41,559
AS3356Level 3 Parent, LLCTransitIPv41,325
AS6461Zayo BandwidthTransitIPv4775
AS2914NTT America, Inc.TransitIPv4549
AS7473Singapore Telecommunications LtdUnclassifiedIPv4532
AS6939Hurricane Electric LLCTransitIPv4201
AS3320Deutsche Telekom AGMobileIPv4199
AS702Verizon BusinessUnclassifiedIPv4116
AS9286KINXHostingIPv466

All 30 upstreams →

Transit

Downstream networks

inferred

Networks for which AS26464 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 30

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

ASNetworkTypeFamiliesPaths seen
AS4766Korea TelecomMobileIPv41,811
AS1299Arelion Sweden ABTransitIPv41,559
AS3356Level 3 Parent, LLCTransitIPv41,325
AS6461Zayo BandwidthTransitIPv4775
AS2914NTT America, Inc.TransitIPv4549
AS7473Singapore Telecommunications LtdUnclassifiedIPv4532
AS6939Hurricane Electric LLCTransitIPv4201
AS3320Deutsche Telekom AGMobileIPv4199
AS702Verizon BusinessUnclassifiedIPv4116
AS9286KINXHostingIPv466

All 30 adjacent →

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.