Observed topology

AS24532 INET-AS-ID - PT. Inet Global Indo

Residential ARIN

Upstreams 6 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS24532: 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
AS23947	PT.Mora Telematika Indonesia	Unclassified	IPv4	2,839
AS137344	PT. TRANS NASIONAL TEKNOLOGI	Unclassified	IPv4	132
AS55685	PT Jala Lintas Media	Unclassified	IPv4	130
AS24482	SG.GS	Hosting	IPv4	37
AS131111	PT Mora Telematika Indonesia	Unclassified	IPv4	2
AS7713	PT Telekomunikasi Indonesia	Residential	IPv4	1

Transit

Downstream networks

inferred

Networks for which AS24532 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 AS24532 in a routing path, in either direction.

AS	Network	Type	Families	Paths seen
AS23947	PT.Mora Telematika Indonesia	Unclassified	IPv4	2,858
AS137344	PT. TRANS NASIONAL TEKNOLOGI	Unclassified	IPv4	132
AS55685	PT Jala Lintas Media	Unclassified	IPv4	130
AS24482	SG.GS	Hosting	IPv4	37
AS141985	PT Argon Internet Amariqindo	Residential	IPv4	19
AS131111	PT Mora Telematika Indonesia	Unclassified	IPv4	2
AS7713	PT Telekomunikasi Indonesia	Residential	IPv4	1

Provenance

Where this comes from

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