asn.dev

Observed topology

AS136975 GNET-AS-AP Global Technology

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS136975: 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
AS132876Symphony Communication (Thailand) PCL.HostingIPv4 IPv6298
AS45558MYANMA POSTS AND TELECOMMUNICATIONSResidentialIPv4118
AS137557International gateway co., LtdUnclassifiedIPv459
AS24482SG.GSHostingIPv4 IPv67
AS136255Telecom International Myanmar Co., LtdUnclassifiedIPv45
AS136168Campana MYTHIC Co. Ltd.UnclassifiedIPv43
AS140867International gateway co., LtdUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS133524Global Technology Co., Ltd.UnclassifiedIPv4 IPv61,589

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS133524Global Technology Co., Ltd.UnclassifiedIPv4 IPv64,704
AS137557International gateway co., LtdUnclassifiedIPv4 IPv61,993
AS132876Symphony Communication (Thailand) PCL.HostingIPv4 IPv61,855
AS45558MYANMA POSTS AND TELECOMMUNICATIONSResidentialIPv4581
AS136168Campana MYTHIC Co. Ltd.UnclassifiedIPv4288
AS136255Telecom International Myanmar Co., LtdUnclassifiedIPv4 IPv6250
AS132167Nine Communications Company LimitedResidentialIPv489
AS174Cogent Communications, LLCTransitIPv477
AS24482SG.GSHostingIPv4 IPv660
AS140867International gateway co., LtdUnclassifiedIPv42

Provenance

Where this comes from

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