Observed topology

AS140635 ThreeC-linktecnologysolecoltd-AS-AP - 3C Link Technology Sole Co., Ltd.

Unclassified APNIC

Upstreams 2 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS140635: 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
AS45796	UIH / BB Connect	Unclassified	IPv4 IPv6	206
AS135059	Lao Asia Pacific Satellite Co., Ltd.	Unclassified	IPv4	24

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS17804	Lao Data Center (LaoDC)	Unclassified	IPv4 IPv6	337
AS135059	Lao Asia Pacific Satellite Co., Ltd.	Unclassified	IPv4	62
AS140631	Global Digital Management Solutions Co Ltd	Unclassified	IPv4	48
AS153966	Joint Development Bank	Unclassified	IPv4	45
AS139011	Banque pour le Commerce Exterieur Lao Public	Unclassified	IPv4	9

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS45796	UIH / BB Connect	Unclassified	IPv4 IPv6	756
AS17804	Lao Data Center (LaoDC)	Unclassified	IPv4 IPv6	337
AS140631	Global Digital Management Solutions Co Ltd	Unclassified	IPv4	97
AS135059	Lao Asia Pacific Satellite Co., Ltd.	Unclassified	IPv4	86
AS153966	Joint Development Bank	Unclassified	IPv4	45
AS139011	Banque pour le Commerce Exterieur Lao Public	Unclassified	IPv4	9

Provenance

Where this comes from

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