asn.dev

Observed topology

AS45735 UNINET-NAP-AS-ID PT. UNINET MEDIA SAKTI

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS45735: 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
AS138840PT. PARSAORAN GLOBAL DATATRANS - NAPUnclassifiedIPv4 IPv691

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS17884PT. Uninet Media Sakti (ISP)ResidentialIPv4 IPv6773
AS150945PT Harrisma Data CittaUnclassifiedIPv4171
AS140444Universitas BinawanEducationIPv4 IPv6111
AS141905PT Korea Investment And Sekuritas IndonesiaUnclassifiedIPv421

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS138840PT. PARSAORAN GLOBAL DATATRANS - NAPUnclassifiedIPv4 IPv61,170
AS17884PT. Uninet Media Sakti (ISP)ResidentialIPv4 IPv6773
AS150945PT Harrisma Data CittaUnclassifiedIPv4171
AS140444Universitas BinawanEducationIPv4 IPv6114
AS141905PT Korea Investment And Sekuritas IndonesiaUnclassifiedIPv421

Provenance

Where this comes from

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