Observed topology

AS9241 FINTEL-FJ Fiji International Telecomunications Ltd

Unclassified APNIC Cable/DSL/ISP

Upstreams 3 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS9241: 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	133
AS4648	Global-Gateway Internet	Unclassified	IPv4	117
AS6939	Hurricane Electric LLC	Transit	IPv4	52

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS23917	Tuvalu Telecommunications Corporation	Unclassified	IPv4	360
AS38201	Tonga Communications Internet Network	Unclassified	IPv4	146
AS45349	Telecom Fiji Ltd	Residential	IPv4	46
AS17993	Vodafone Samoa Limited	Unclassified	IPv4	42

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS4648	Global-Gateway Internet	Unclassified	IPv4	574
AS23917	Tuvalu Telecommunications Corporation	Unclassified	IPv4	360
AS174	Cogent Communications, LLC	Transit	IPv4	357
AS38201	Tonga Communications Internet Network	Unclassified	IPv4	146
AS6939	Hurricane Electric LLC	Transit	IPv4	107
AS45349	Telecom Fiji Ltd	Residential	IPv4	78
AS17993	Vodafone Samoa Limited	Unclassified	IPv4	42

Provenance

Where this comes from

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