Observed topology

AS139750 IDCSERVICESNETINC-AS-AP - IDCServices.net Inc

Unclassified APNIC

Upstreams 7 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 10

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS139750: 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
AS6453	TATA COMMUNICATIONS (AMERICA) INC	Transit	IPv4	564
AS17408	AboveNet Communications Taiwan	Unclassified	IPv4	331
AS2914	NTT America, Inc.	Transit	IPv4	74
AS3491	PCCW Global (HK) Ltd.	Transit	IPv4	47
AS4637	Telstra Global	Unclassified	IPv4	11
AS10133	Chief Telecom Inc.	Unclassified	IPv4	3
AS24482	SG.GS	Hosting	IPv4	3

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS59268	QLINKS	Unclassified	IPv4	1,829

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS59268	QLINKS	Unclassified	IPv4	2,001
AS6453	TATA COMMUNICATIONS (AMERICA) INC	Transit	IPv4	1,336
AS17408	AboveNet Communications Taiwan	Unclassified	IPv4	914
AS3491	PCCW Global (HK) Ltd.	Transit	IPv4	345
AS1299	Arelion Sweden AB	Transit	IPv4	171
AS2914	NTT America, Inc.	Transit	IPv4	161
AS4637	Telstra Global	Unclassified	IPv4	79
AS10133	Chief Telecom Inc.	Unclassified	IPv4	16
AS24482	SG.GS	Hosting	IPv4	11
AS7713	PT Telekomunikasi Indonesia	Residential	IPv4	1

Provenance

Where this comes from

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