asn.dev

Observed topology

AS135307 GTMH-AS-AP - Golden TMH Telecom Co. Ltd

Hosting APNIC

Upstreams 3 carry this network
Downstreams 3 this network carries
Adjacent (IPv4) 6
Adjacent (IPv6) 0
Upstream graph Who carries AS135307, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS135307 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS135307: 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.

ASNetworkTypeFamiliesPaths seen
AS45558MYANMA POSTS AND TELECOMMUNICATIONSResidentialIPv4345
AS132167Nine Communications Company LimitedResidentialIPv4133
AS133385Atom Myanmar LimitedResidentialIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS150297Golden Myanmar Business Exchange Co. LtdUnclassifiedIPv4305
AS153998Myanmar Citizens Bank Public Company LimitedUnclassifiedIPv467
AS134137True Internet Data Center Company LimitedHostingIPv458

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS45558MYANMA POSTS AND TELECOMMUNICATIONSResidentialIPv4691
AS150297Golden Myanmar Business Exchange Co. LtdUnclassifiedIPv4305
AS132167Nine Communications Company LimitedResidentialIPv4217
AS153998Myanmar Citizens Bank Public Company LimitedUnclassifiedIPv467
AS134137True Internet Data Center Company LimitedHostingIPv458
AS133385Atom Myanmar LimitedResidentialIPv43

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.