asn.dev

Observed topology

AS55567 AZZURRI-AU Suite 2, Level 9

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS55567: 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
AS4826Vocus Connect International BackboneUnclassifiedIPv4192
AS6939Hurricane Electric LLCTransitIPv432
AS24115EquinixHostingIPv44
AS24482SG.GSHostingIPv44
AS64073Vetta GroupUnclassifiedIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS24110IVE GROUP AUSTRALIA PTY LTDUnclassifiedIPv4354
AS55521IVE GROUP AUSTRALIA PTY LTDHostingIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4826Vocus Connect International BackboneUnclassifiedIPv4534
AS24110IVE GROUP AUSTRALIA PTY LTDUnclassifiedIPv4354
AS6939Hurricane Electric LLCTransitIPv488
AS55521IVE GROUP AUSTRALIA PTY LTDHostingIPv459
AS24482SG.GSHostingIPv411
AS64073Vetta GroupUnclassifiedIPv411
AS24115EquinixHostingIPv45

Provenance

Where this comes from

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