asn.dev

Observed topology

AS59362 KSNETWORK-AS-AP KS Network Limited

Unclassified APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS59362: 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
AS141731Max Hub LimitedUnclassifiedIPv4 IPv61,254
AS58717Summit Communications LtdUnclassifiedIPv41,157
AS10075Fiber@Home Global LimitedResidentialIPv4230

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS154580Linux Pathshala Limited.UnclassifiedIPv465
AS64065NRB Global Bank Ltd.UnclassifiedIPv458

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS58717Summit Communications LtdUnclassifiedIPv41,280
AS141731Max Hub LimitedUnclassifiedIPv4 IPv61,254
AS10075Fiber@Home Global LimitedResidentialIPv4230
AS154580Linux Pathshala Limited.UnclassifiedIPv465
AS64065NRB Global Bank Ltd.UnclassifiedIPv458

Provenance

Where this comes from

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