asn.dev

Observed topology

AS38826 INFINITENETWORKS-AS-AP Infinite Networks Pty Ltd

Unclassified APNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS38826: 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 LTDUnclassifiedIPv4 IPv6872
AS4826Vocus Connect International BackboneUnclassifiedIPv4 IPv6249
AS6939Hurricane Electric LLCTransitIPv4152
AS24482SG.GSHostingIPv4 IPv622
AS64073Vetta GroupUnclassifiedIPv4 IPv622
AS24115EquinixHostingIPv418

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS132221Intelite Pty. Ltd.UnclassifiedIPv4 IPv6159
AS141746Disaster ScienceHostingIPv4112
AS137060The Club Group Canberra AustraliaUnclassifiedIPv4 IPv642

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS137409GSL Networks Pty LTDUnclassifiedIPv4 IPv61,104
AS4826Vocus Connect International BackboneUnclassifiedIPv4 IPv6301
AS6939Hurricane Electric LLCTransitIPv4173
AS132221Intelite Pty. Ltd.UnclassifiedIPv4 IPv6159
AS141746Disaster ScienceHostingIPv4112
AS137060The Club Group Canberra AustraliaUnclassifiedIPv4 IPv642
AS24482SG.GSHostingIPv4 IPv626
AS64073Vetta GroupUnclassifiedIPv4 IPv626
AS24115EquinixHostingIPv418

Provenance

Where this comes from

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