Observed topology

AS134190 IPDC-AS-AP - IPDC SOLUTIONS PTE LTD

Unclassified APNIC

Upstreams 2 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS134190: 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
AS3491	PCCW Global (HK) Ltd.	Transit	IPv4	110
AS17984	PCCW Global (HK) Ltd.	Unclassified	IPv4	8

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS9656	T-SYSTEMS SINGAPORE PTE LTD	Unclassified	IPv4	295
AS136907	HUAWEI CLOUDS	Hosting	IPv4	152
AS137932	IPDC SOLUTIONS PTE LTD	Unclassified	IPv4	60
AS9902	NEOCOMISP LIMITED, IPTX Transit and Network Service Provider in Cambodia.	Unclassified	IPv4	5
AS134672	Aquoz Solutions Inc	Unclassified	IPv4	1

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS3491	PCCW Global (HK) Ltd.	Transit	IPv4	548
AS17984	PCCW Global (HK) Ltd.	Unclassified	IPv4	333
AS151610	HUAWEI INTERNATIONAL PTE. LTD.	Unclassified	IPv4	319
AS9656	T-SYSTEMS SINGAPORE PTE LTD	Unclassified	IPv4	295
AS136907	HUAWEI CLOUDS	Hosting	IPv4	152
AS2914	NTT America, Inc.	Transit	IPv4	125
AS9902	NEOCOMISP LIMITED, IPTX Transit and Network Service Provider in Cambodia.	Unclassified	IPv4	61
AS137932	IPDC SOLUTIONS PTE LTD	Unclassified	IPv4	60
AS134672	Aquoz Solutions Inc	Unclassified	IPv4	1

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.