asn.dev

Observed topology

AS45349 TFL-AS-AP - Telecom Fiji Ltd

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS45349: 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
AS4648Global-Gateway InternetUnclassifiedIPv4 IPv6136
AS174Cogent Communications, LLCTransitIPv4 IPv676
AS4637Telstra GlobalUnclassifiedIPv4 IPv644
AS9241Fiji International Telecomunications LtdUnclassifiedIPv444
AS6939Hurricane Electric LLCTransitIPv438
AS7474SingTel Optus Pty LtdUnclassifiedIPv426
AS24482SG.GSHostingIPv4 IPv66
AS64073Vetta GroupUnclassifiedIPv4 IPv66
AS24115EquinixHostingIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS4638Telecom Fiji LimitedResidentialIPv4 IPv65,735

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS4638Telecom Fiji LimitedResidentialIPv4 IPv66,240
AS174Cogent Communications, LLCTransitIPv4 IPv63,142
AS7474SingTel Optus Pty LtdUnclassifiedIPv4 IPv61,064
AS6939Hurricane Electric LLCTransitIPv4 IPv6883
AS4648Global-Gateway InternetUnclassifiedIPv4 IPv6756
AS4637Telstra GlobalUnclassifiedIPv4 IPv6380
AS24482SG.GSHostingIPv4 IPv6106
AS64073Vetta GroupUnclassifiedIPv4 IPv6106
AS24115EquinixHostingIPv4101
AS9241Fiji International Telecomunications LtdUnclassifiedIPv479

All 13 adjacent →

Provenance

Where this comes from

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