asn.dev

Observed topology

AS134555 ENCOO-AS-AP - Encoo Pty Ltd

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS134555: 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
AS137409GSL Networks Pty LTDUnclassifiedIPv4869
AS6939Hurricane Electric LLCTransitIPv4135
AS1221Telstra LimitedMobileIPv4 IPv646
AS24482SG.GSHostingIPv4 IPv617
AS64073Vetta GroupUnclassifiedIPv4 IPv614
AS24115EquinixHostingIPv48

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS133120Hosted Network Pty LtdUnclassifiedIPv4 IPv61,676
AS7471City of DarebinUnclassifiedIPv4124
AS137433Seek LimitedUnclassifiedIPv4124
AS45267Lightwire LTDUnclassifiedIPv4 IPv691
AS136228Casey City CouncilUnclassifiedIPv462
AS138488Moonee Valley City CouncilUnclassifiedIPv462
AS149814BLUE CONNECTIONS PTY LTDUnclassifiedIPv455

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS137409GSL Networks Pty LTDUnclassifiedIPv43,024
AS133120Hosted Network Pty LtdUnclassifiedIPv4 IPv61,694
AS6939Hurricane Electric LLCTransitIPv4221
AS45267Lightwire LTDUnclassifiedIPv4 IPv6221
AS7471City of DarebinUnclassifiedIPv4124
AS137433Seek LimitedUnclassifiedIPv4124
AS1221Telstra LimitedMobileIPv4 IPv6104
AS136228Casey City CouncilUnclassifiedIPv462
AS138488Moonee Valley City CouncilUnclassifiedIPv462
AS149814BLUE CONNECTIONS PTY LTDUnclassifiedIPv455

All 13 adjacent →

Provenance

Where this comes from

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