asn.dev

Observed topology

AS24535 ISATNET-AS-ID PT.Insan Sarana Telematika

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS24535: 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
AS58389PT Sumber Data IndonesiaUnclassifiedIPv41,998
AS45147PT. NAP Info Lintas NusaUnclassifiedIPv4 IPv6292
AS24482SG.GSHostingIPv435
AS7713PT Telekomunikasi IndonesiaResidentialIPv416

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS45102Alibaba (US) Technology Co., Ltd.HostingIPv41
AS54994Meteverse Limited.UnclassifiedIPv41
AS154205PT Susu Teknologi IndonesiaUnclassifiedIPv41
AS199524G-Core Labs S.A.HostingIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS58389PT Sumber Data IndonesiaUnclassifiedIPv41,998
AS45147PT. NAP Info Lintas NusaUnclassifiedIPv4 IPv6292
AS24482SG.GSHostingIPv435
AS7713PT Telekomunikasi IndonesiaResidentialIPv432
AS17497Liasail Global Hongkong LimitedUnclassifiedIPv412
AS45102Alibaba (US) Technology Co., Ltd.HostingIPv41
AS54994Meteverse Limited.UnclassifiedIPv41
AS154205PT Susu Teknologi IndonesiaUnclassifiedIPv41
AS199524G-Core Labs S.A.HostingIPv41

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.