asn.dev

Observed topology

AS151066 INI-AS-AP Imperial network inc

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS151066: 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
AS135423Total Information Management CorporationResidentialIPv4650
AS24482SG.GSHostingIPv4 IPv677
AS63927RISEResidentialIPv434
AS6939Hurricane Electric LLCTransitIPv616
AS21859Zenlayer IncHostingIPv411
AS37989DCS1 Pte. Ltd.HostingIPv411
AS38001NewMedia Express Pte LtdHostingIPv411
AS17639Converge ICT Solutions Inc.UnclassifiedIPv61
AS135607Infinivan IncorporatedResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS141455Halum Properties (HALPROP) Inc.UnclassifiedIPv4130

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS135423Total Information Management CorporationResidentialIPv4778
AS141455Halum Properties (HALPROP) Inc.UnclassifiedIPv4130
AS24482SG.GSHostingIPv4 IPv679
AS63927RISEResidentialIPv434
AS6939Hurricane Electric LLCTransitIPv616
AS21859Zenlayer IncHostingIPv411
AS37989DCS1 Pte. Ltd.HostingIPv411
AS38001NewMedia Express Pte LtdHostingIPv411
AS17639Converge ICT Solutions Inc.UnclassifiedIPv61
AS135607Infinivan IncorporatedResidentialIPv61

Provenance

Where this comes from

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