Observed topology

AS17993 VODAFONESAMOA-AS-AP Vodafone Samoa Limited

Unclassified APNIC

Upstreams 7 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS17993: 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
AS174	Cogent Communications, LLC	Transit	IPv4	1,547
AS6939	Hurricane Electric LLC	Transit	IPv4	357
AS9241	Fiji International Telecomunications Ltd	Unclassified	IPv4	42
AS24115	Equinix	Hosting	IPv4	35
AS24482	SG.GS	Hosting	IPv4	35
AS64073	Vetta Group	Unclassified	IPv4	35
AS35280	F5 Networks SARL	Hosting	IPv4	3

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS23657	Blue Sky Communications	Unclassified	IPv4	59
AS150321	Secretariat of the Pacific Regional Environment Programme	Unclassified	IPv4	58

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS174	Cogent Communications, LLC	Transit	IPv4	1,651
AS6939	Hurricane Electric LLC	Transit	IPv4	367
AS23657	Blue Sky Communications	Unclassified	IPv4	59
AS150321	Secretariat of the Pacific Regional Environment Programme	Unclassified	IPv4	58
AS9241	Fiji International Telecomunications Ltd	Unclassified	IPv4	42
AS24115	Equinix	Hosting	IPv4	36
AS24482	SG.GS	Hosting	IPv4	36
AS64073	Vetta Group	Unclassified	IPv4	36
AS35280	F5 Networks SARL	Hosting	IPv4	3

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.