asn.dev

Observed topology

AS63529 Bangkok Neutral Internet Exchange Route Servers

Unclassified APNIC Route Server

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

Transit

Upstream networks

inferred

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

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS58955Bangmod Enterprise Co., Ltd.HostingIPv4119
AS23932Internet Service ProviderUnclassifiedIPv453
AS4621UNINET-THEducationIPv427
AS15352601-00027433ResidentialIPv45
AS32934Facebook, Inc.HostingIPv4 IPv64
AS133880The Thai Red Cross SocietyUnclassifiedIPv4 IPv63
AS7693KSC Commercial Internet Co. Ltd.UnclassifiedIPv42
AS38794UIHResidentialIPv42
AS45758Triple T Broadband Public Company LimitedResidentialIPv62
AS63528Bangkok Neutral Internet ExchangeUnclassifiedIPv42

Adjacency

Adjacent networks

All 19

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

ASNetworkTypeFamiliesPaths seen
AS23764CTGNetUnclassifiedIPv4 IPv6246
AS58955Bangmod Enterprise Co., Ltd.HostingIPv4119
AS23932Internet Service ProviderUnclassifiedIPv453
AS4621UNINET-THEducationIPv435
AS15352601-00027433ResidentialIPv45
AS32934Facebook, Inc.HostingIPv4 IPv64
AS45667TCC Technology Co.,Ltd.ResidentialIPv44
AS45758Triple T Broadband Public Company LimitedResidentialIPv63
AS131447POPIDC powered by CSLoxinfoUnclassifiedIPv4 IPv63
AS133880The Thai Red Cross SocietyUnclassifiedIPv4 IPv63

Provenance

Where this comes from

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