asn.dev

Observed topology

AS24435 SUPERNET-PAKISTAN-AS-AP Supernet Limited Transit Autonomous System Number

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS24435: 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
AS38193Transworld Associates (Pvt.) Ltd.UnclassifiedIPv4 IPv62,774
AS138423CMPak LimitedUnclassifiedIPv4 IPv61,312
AS17557Pakistan Telecommunication Company LimitedUnclassifiedIPv4 IPv6939

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS55340Telecard LimitedUnclassifiedIPv4372
AS38166Standard Chartered Bank (Hong Kong) Limited.Banking andUnclassifiedIPv4242
AS38488Telecard LimitedUnclassifiedIPv496
AS56192KICT Customer Services Building,UnclassifiedIPv441

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS38193Transworld Associates (Pvt.) Ltd.UnclassifiedIPv4 IPv63,166
AS138423CMPak LimitedUnclassifiedIPv4 IPv61,551
AS17557Pakistan Telecommunication Company LimitedUnclassifiedIPv4 IPv61,059
AS55340Telecard LimitedUnclassifiedIPv4372
AS38166Standard Chartered Bank (Hong Kong) Limited.Banking andUnclassifiedIPv4242
AS38488Telecard LimitedUnclassifiedIPv496
AS56192KICT Customer Services Building,UnclassifiedIPv441

Provenance

Where this comes from

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