asn.dev

Observed topology

AS55785 ISPLIMITED-AS-AP ISP Limited

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS55785: 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
AS55850Mercury NZ LimitedResidentialIPv4 IPv6222
AS6939Hurricane Electric LLCTransitIPv440
AS24482SG.GSHostingIPv4 IPv65
AS64073Vetta GroupUnclassifiedIPv4 IPv65

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS133043Enhanced Solutions LtdUnclassifiedIPv4 IPv6213
AS138041Telco2 LimitedHostingIPv471
AS137257Localhost LimitedHostingIPv4 IPv668
AS133096MOTHERSHIPUnclassifiedIPv430
AS131583WIZwireless LimitedUnclassifiedIPv417

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS55850Mercury NZ LimitedResidentialIPv4 IPv61,170
AS133043Enhanced Solutions LtdUnclassifiedIPv4 IPv61,039
AS6939Hurricane Electric LLCTransitIPv4255
AS138041Telco2 LimitedHostingIPv471
AS137257Localhost LimitedHostingIPv4 IPv668
AS24482SG.GSHostingIPv4 IPv644
AS133096MOTHERSHIPUnclassifiedIPv430
AS64073Vetta GroupUnclassifiedIPv4 IPv628
AS131583WIZwireless LimitedUnclassifiedIPv417

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.