asn.dev

Observed topology

AS4382 INDONUSA-ID - PT. Indonusa System Integrator Prima

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS4382: 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
AS45147PT. NAP Info Lintas NusaUnclassifiedIPv4 IPv6337
AS55818MC-IX Matrix Internet Exchange RS-1ResidentialIPv4 IPv6175
AS7713PT Telekomunikasi IndonesiaResidentialIPv490
AS18103Neuviz NetResidentialIPv418
AS24482SG.GSHostingIPv4 IPv612
AS136106PT. Mega Akses PersadaResidentialIPv68
AS35280F5 Networks SARLHostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS152069PT Nusantara Star ConnectUnclassifiedIPv4117

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS45147PT. NAP Info Lintas NusaUnclassifiedIPv4 IPv6451
AS55818MC-IX Matrix Internet Exchange RS-1ResidentialIPv4 IPv6175
AS152069PT Nusantara Star ConnectUnclassifiedIPv4117
AS7713PT Telekomunikasi IndonesiaResidentialIPv495
AS18103Neuviz NetResidentialIPv426
AS24482SG.GSHostingIPv4 IPv612
AS136106PT. Mega Akses PersadaResidentialIPv68
AS35280F5 Networks SARLHostingIPv61

Provenance

Where this comes from

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