Observed topology

AS150683 FBL-AS-AP FASTTEL BROADBAND PRIVATE LIMITED

Unclassified ARIN

Upstreams 5 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 4

Adjacent (IPv6) 3

Upstream graph Who carries AS150683, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS150683 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS150683: 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.

AS	Network	Type	Families	Paths seen
AS138423	CMPak Limited	Unclassified	IPv4 IPv6	804
AS58470	IX Peering for Mobilink and Link Direct International.	Unclassified	IPv4 IPv6	507
AS38264	National WiMAX/IMS environment	Unclassified	IPv4	58
AS38193	Transworld Associates (Pvt.) Ltd.	Unclassified	IPv6	41
AS24499	Telenor Pakistan	Unclassified	IPv4	27

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS138423	CMPak Limited	Unclassified	IPv4 IPv6	804
AS58470	IX Peering for Mobilink and Link Direct International.	Unclassified	IPv4 IPv6	507
AS38264	National WiMAX/IMS environment	Unclassified	IPv4	58
AS38193	Transworld Associates (Pvt.) Ltd.	Unclassified	IPv6	41
AS24499	Telenor Pakistan	Unclassified	IPv4	27

Provenance

Where this comes from

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