Observed topology

AS134134 WESTERN2-AS-AP - Western ICT Solutions Services

Unclassified APNIC Cable/DSL/ISP

Upstreams 1 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS134134: 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
AS55330	AFGHANTELECOM GOVERNMENT COMMUNICATION NETWORK	Unclassified	IPv4	554

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS139885	Fushanj Telecom ISP	Unclassified	IPv4	63
AS151062	Matin Net	Unclassified	IPv4	63
AS137040	Network Zone Solution Provider Ltd	Unclassified	IPv4	62
AS149173	Hindukush Bridge ICT Services Company	Unclassified	IPv4	62

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS55330	AFGHANTELECOM GOVERNMENT COMMUNICATION NETWORK	Unclassified	IPv4	804
AS139885	Fushanj Telecom ISP	Unclassified	IPv4	63
AS151062	Matin Net	Unclassified	IPv4	63
AS137040	Network Zone Solution Provider Ltd	Unclassified	IPv4	62
AS149173	Hindukush Bridge ICT Services Company	Unclassified	IPv4	62

Provenance

Where this comes from

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