Observed topology

AS24475 THAIREN-TRANSIT-AS-AP - ThaiREN.Thailand Research and Education Network Thailand

Unclassified APNIC

Upstreams 2 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 4

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS24475: 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
AS7660	Asia Pacific Advanced Network - Japan	Unclassified	IPv4	16
AS24489	Trans-Eurasia Information Network (TEIN2) - North	Unclassified	IPv4 IPv6	5

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS4621	UNINET-TH	Education	IPv4 IPv6	283
AS3836	Thai Social/Scientific, Academic and Research Network	Education	IPv4 IPv6	6

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS4621	UNINET-TH	Education	IPv4 IPv6	2,068
AS7660	Asia Pacific Advanced Network - Japan	Unclassified	IPv4	2,054
AS24489	Trans-Eurasia Information Network (TEIN2) - North	Unclassified	IPv4 IPv6	71
AS3836	Thai Social/Scientific, Academic and Research Network	Education	IPv4 IPv6	36

Provenance

Where this comes from

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