asn.dev

Observed topology

AS46031 TELKOMSAT-NAP-AS-ID PT Telkom Satelit Indonesia

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS46031: 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
AS10217PT. NTT IndonesiaUnclassifiedIPv4 IPv6220
AS7713PT Telekomunikasi IndonesiaResidentialIPv413
AS138840PT. PARSAORAN GLOBAL DATATRANS - NAPUnclassifiedIPv44
AS24482SG.GSHostingIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS56241PT Telkom Satelit IndonesiaUnclassifiedIPv4808
AS10137PT Telkom Satelit IndonesiaUnclassifiedIPv4595

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS10217PT. NTT IndonesiaUnclassifiedIPv4 IPv61,226
AS56241PT Telkom Satelit IndonesiaUnclassifiedIPv4854
AS10137PT Telkom Satelit IndonesiaUnclassifiedIPv4595
AS138840PT. PARSAORAN GLOBAL DATATRANS - NAPUnclassifiedIPv4245
AS7713PT Telekomunikasi IndonesiaResidentialIPv4206
AS136106PT. Mega Akses PersadaResidentialIPv435
AS24482SG.GSHostingIPv420
AS58495PT Parsaoran Global DatatransUnclassifiedIPv43

Provenance

Where this comes from

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