Observed topology

AS38084 ETHAN-AU-AP Ethan Group

Unclassified APNIC

Upstreams 6 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 4

Upstream graph Who carries AS38084, and who carries them, drawn as a map up to the transit-free core. 6 exchanges Where AS38084 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS38084: 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.

AS	Network	Type	Families	Paths seen
AS4826	Vocus Connect International Backbone	Unclassified	IPv4 IPv6	316
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	259
AS6939	Hurricane Electric LLC	Transit	IPv4	70
AS23655	2degrees Networks Limited	Unclassified	IPv4	66
AS24482	SG.GS	Hosting	IPv4 IPv6	13
AS64073	Vetta Group	Unclassified	IPv4 IPv6	13

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS153162	S Apikian and others t/a Gadens	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS4826	Vocus Connect International Backbone	Unclassified	IPv4 IPv6	332
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	293
AS6939	Hurricane Electric LLC	Transit	IPv4	77
AS23655	2degrees Networks Limited	Unclassified	IPv4	66
AS153162	S Apikian and others t/a Gadens	Unclassified	IPv4	59
AS24482	SG.GS	Hosting	IPv4 IPv6	14
AS64073	Vetta Group	Unclassified	IPv4 IPv6	14

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.