Observed topology

AS3836 THAISARN-TH-AS-AP Thai SocialScientific, Academic and Research Network

Education ARIN

Upstreams 2 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 4

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS3836: 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
AS4621	UNINET-TH	Education	IPv4 IPv6	164
AS24475	ThaiREN.Thailand Research and Education Network Thailand	Unclassified	IPv4 IPv6	6

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS38296	National Science and Technology Development Agency	Unclassified	IPv4	20
AS7588	Thailand Public backbone Network	Unclassified	IPv4	10

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS4621	UNINET-TH	Education	IPv4 IPv6	164
AS24475	ThaiREN.Thailand Research and Education Network Thailand	Unclassified	IPv4 IPv6	36
AS38296	National Science and Technology Development Agency	Unclassified	IPv4	20
AS7588	Thailand Public backbone Network	Unclassified	IPv4	10

Provenance

Where this comes from

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