asn.dev

Observed topology

AS55501 CONNECTEL-PK 141-143 Maulana Shaukat Ali Road

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS55501: 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,095
AS24499Telenor PakistanUnclassifiedIPv4 IPv61,016

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS147031Million Web Services Private LimitedUnclassifiedIPv4116
AS142421SKIF Enterprises Private LimitedUnclassifiedIPv452

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS38193Transworld Associates (Pvt.) Ltd.UnclassifiedIPv4 IPv62,211
AS24499Telenor PakistanUnclassifiedIPv4 IPv61,068
AS147031Million Web Services Private LimitedUnclassifiedIPv4116
AS142421SKIF Enterprises Private LimitedUnclassifiedIPv452

Provenance

Where this comes from

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