asn.dev

Observed topology

AS23459 APPLEBEE-NETWORKS

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS23459: 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
AS40676Psychz NetworksHostingIPv4 IPv6131
AS21738RozintResidentialIPv450
AS6939Hurricane Electric LLCTransitIPv416
AS9002RETN LimitedUnclassifiedIPv46
AS3130RGnet OUUnclassifiedIPv43
AS7575Australian Academic and Research Network (AARNet)EducationIPv42
AS24482SG.GSHostingIPv42
AS34927iFog GmbHHostingIPv42
AS394256Tech Futures Interactive Inc.UnclassifiedIPv42
AS293ESnetUnclassifiedIPv41

Transit

Downstream networks

inferred

Networks for which AS23459 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

observed

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

ASNetworkTypeFamiliesPaths seen
AS40676Psychz NetworksHostingIPv4 IPv6131
AS21738RozintResidentialIPv450
AS6939Hurricane Electric LLCTransitIPv416
AS9002RETN LimitedUnclassifiedIPv46
AS3130RGnet OUUnclassifiedIPv43
AS7575Australian Academic and Research Network (AARNet)EducationIPv42
AS24482SG.GSHostingIPv42
AS34927iFog GmbHHostingIPv42
AS394256Tech Futures Interactive Inc.UnclassifiedIPv42
AS293ESnetUnclassifiedIPv41

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-21 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.