asn.dev

Observed topology

AS38154 PSN-NAP-AS PT. Pasifik Satelit Nusantara

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS38154: 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 IPv6285
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv48
AS24482SG.GSHostingIPv4 IPv66

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS9875PT. Pasifik Satelit NusantaraResidentialIPv4 IPv64,081
AS58478PT. Pasifik Satelit NusantaraUnclassifiedIPv4325
AS150953PT Satelit Nusantara LimaUnclassifiedIPv427

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS45147PT. NAP Info Lintas NusaUnclassifiedIPv4 IPv64,556
AS9875PT. Pasifik Satelit NusantaraResidentialIPv4 IPv64,081
AS58478PT. Pasifik Satelit NusantaraUnclassifiedIPv4325
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4154
AS150953PT Satelit Nusantara LimaUnclassifiedIPv427
AS24482SG.GSHostingIPv4 IPv611

Provenance

Where this comes from

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