asn.dev

Observed topology

AS147027 RTARF-MI - Royal Thai Armed Force Headquarters

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS147027: 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
AS131293TOT Public Company LimitedHostingIPv4 IPv6160
AS23969TOT Public Company LimitedResidentialIPv4 IPv6103
AS45758Triple T Broadband Public Company LimitedResidentialIPv436
AS55808Triple T Broadband Public Company LimitedUnclassifiedIPv436

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS131293TOT Public Company LimitedHostingIPv4 IPv6160
AS23969TOT Public Company LimitedResidentialIPv4 IPv6103
AS45758Triple T Broadband Public Company LimitedResidentialIPv436
AS55808Triple T Broadband Public Company LimitedUnclassifiedIPv436

Provenance

Where this comes from

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