asn.dev

Observed topology

AS58485 WIFIAN-AS-ID - WIFIAN ID

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS58485: 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
AS4800PT Aplikanusa LintasartaHostingIPv4 IPv65,658
AS24482SG.GSHostingIPv4 IPv6168
AS37989DCS1 Pte. Ltd.HostingIPv6159
AS61292Blix Group ASUnclassifiedIPv6159
AS138840PT. PARSAORAN GLOBAL DATATRANS - NAPUnclassifiedIPv6157
AS136106PT. Mega Akses PersadaResidentialIPv4138

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS153717PT Diaza Lintas DataResidentialIPv48
AS150487PT Nusantara Akses TelekomunikasiResidentialIPv43

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4800PT Aplikanusa LintasartaHostingIPv4 IPv65,658
AS24482SG.GSHostingIPv4 IPv6172
AS37989DCS1 Pte. Ltd.HostingIPv6159
AS61292Blix Group ASUnclassifiedIPv6159
AS138840PT. PARSAORAN GLOBAL DATATRANS - NAPUnclassifiedIPv6157
AS136106PT. Mega Akses PersadaResidentialIPv4138
AS153717PT Diaza Lintas DataResidentialIPv49
AS150487PT Nusantara Akses TelekomunikasiResidentialIPv43

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.