asn.dev

Observed topology

AS142647 NAN-AS-AP Nasstec Airnet Networks Private Limited

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS142647: 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
AS138423CMPak LimitedUnclassifiedIPv4 IPv6612
AS58470IX Peering for Mobilink and Link Direct International.UnclassifiedIPv4174
AS132165Connect CommunicationsUnclassifiedIPv461

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS139087Fast Web & Wireless Communications (Pvt.) LimitedUnclassifiedIPv462
AS147018MIAN INTERNET SERVICES (Pvt.) LtdUnclassifiedIPv457
AS55714Fiberlink Pvt.LtdUnclassifiedIPv456

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS138423CMPak LimitedUnclassifiedIPv4 IPv6612
AS58470IX Peering for Mobilink and Link Direct International.UnclassifiedIPv4287
AS132165Connect CommunicationsUnclassifiedIPv4123
AS139087Fast Web & Wireless Communications (Pvt.) LimitedUnclassifiedIPv462
AS147018MIAN INTERNET SERVICES (Pvt.) LtdUnclassifiedIPv457
AS55714Fiberlink Pvt.LtdUnclassifiedIPv456

Provenance

Where this comes from

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