Observed topology

AS150692 GD2CL-AS-AP - Golden Dragon 2000

Unclassified APNIC

Upstreams 2 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS150692: 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
AS136255	Telecom International Myanmar Co., Ltd	Unclassified	IPv4 IPv6	379
AS138166	MaxxB Fiber Internet	Residential	IPv4	111

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS152447	My Mandalay Company Limited	Residential	IPv4	105
AS150309	E R S TECHNOLOGY	Unclassified	IPv4	65
AS153549	MUI Technology Company Limited	Unclassified	IPv4	62
AS150153	A W S (MYANMAR) COMPANY LIMITED	Unclassified	IPv4	58

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS136255	Telecom International Myanmar Co., Ltd	Unclassified	IPv4 IPv6	768
AS153549	MUI Technology Company Limited	Unclassified	IPv4	251
AS138166	MaxxB Fiber Internet	Residential	IPv4	244
AS152447	My Mandalay Company Limited	Residential	IPv4	148
AS150309	E R S TECHNOLOGY	Unclassified	IPv4	65
AS150153	A W S (MYANMAR) COMPANY LIMITED	Unclassified	IPv4	58

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.