asn.dev

Observed topology

AS137910 WAVECOMM-AS-AP Wavecomm Private Limited

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS137910: 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
AS139820HG TELECOMMUNICATION PRIVATE LIMITEDUnclassifiedIPv4410
AS58470IX Peering for Mobilink and Link Direct International.UnclassifiedIPv4130
AS138423CMPak LimitedUnclassifiedIPv4114
AS17557Pakistan Telecommunication Company LimitedUnclassifiedIPv459

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS150311LASERTEL PRIVATE LIMITEDUnclassifiedIPv4 IPv6157
AS142063Grand Tel Private LimitedUnclassifiedIPv461
AS141023HG TELECOMMUNICATION PRIVATE LIMITEDUnclassifiedIPv456
AS139820HG TELECOMMUNICATION PRIVATE LIMITEDUnclassifiedIPv43

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS139820HG TELECOMMUNICATION PRIVATE LIMITEDUnclassifiedIPv4413
AS17557Pakistan Telecommunication Company LimitedUnclassifiedIPv4 IPv6277
AS138423CMPak LimitedUnclassifiedIPv4170
AS150311LASERTEL PRIVATE LIMITEDUnclassifiedIPv4 IPv6157
AS58470IX Peering for Mobilink and Link Direct International.UnclassifiedIPv4133
AS142063Grand Tel Private LimitedUnclassifiedIPv461
AS141023HG TELECOMMUNICATION PRIVATE LIMITEDUnclassifiedIPv456

Provenance

Where this comes from

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