asn.dev

Observed topology

AS271150 FOX LINK TELECOM LTDA

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS271150: 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
AS269572SPEED JET TELECOM LTDAUnclassifiedIPv4 IPv6131
AS11432Telium Telecomunicacoes LtdaHostingIPv4 IPv694
AS273522WPM TELECOM LTDAUnclassifiedIPv458
AS269250EVOLUCAO TELECOM LTDAUnclassifiedIPv443
AS6939Hurricane Electric LLCTransitIPv635
AS24482SG.GSHostingIPv4 IPv64
AS35280F5 Networks SARLHostingIPv61
AS37721Virtual Technologies & SolutionsResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS272738JC FRANKLIN TELECOM LTDAUnclassifiedIPv675

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS269572SPEED JET TELECOM LTDAUnclassifiedIPv4 IPv6131
AS11432Telium Telecomunicacoes LtdaHostingIPv4 IPv6108
AS6939Hurricane Electric LLCTransitIPv688
AS272738JC FRANKLIN TELECOM LTDAUnclassifiedIPv675
AS273522WPM TELECOM LTDAUnclassifiedIPv458
AS269250EVOLUCAO TELECOM LTDAUnclassifiedIPv443
AS24482SG.GSHostingIPv4 IPv67
AS37721Virtual Technologies & SolutionsResidentialIPv64
AS35280F5 Networks SARLHostingIPv63

Provenance

Where this comes from

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