asn.dev

Observed topology

AS271418 AS271418 - freynet telecom

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS271418: 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
AS28260ALTA REDE CORPORATE NETWORK TELECOM LTDA - EPPUnclassifiedIPv461
AS264014Led Internet EireliResidentialIPv461
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv659
AS264144ASAP GLOBAL TELECOMUnclassifiedIPv4 IPv647
AS273421MAZA TelecomUnclassifiedIPv435
AS269665LEKST TELECOMResidentialIPv433
AS6939Hurricane Electric LLCTransitIPv411
AS24482SG.GSHostingIPv4 IPv64
AS35280F5 Networks SARLHostingIPv62
AS37721Virtual Technologies & SolutionsResidentialIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS274735MAIKE DOUGLAS MACEDO SEBASTIAO MEUnclassifiedIPv666

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS274735MAIKE DOUGLAS MACEDO SEBASTIAO MEUnclassifiedIPv6132
AS28260ALTA REDE CORPORATE NETWORK TELECOM LTDA - EPPUnclassifiedIPv461
AS264014Led Internet EireliResidentialIPv461
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv659
AS264144ASAP GLOBAL TELECOMUnclassifiedIPv4 IPv647
AS273421MAZA TelecomUnclassifiedIPv435
AS269665LEKST TELECOMResidentialIPv433
AS6939Hurricane Electric LLCTransitIPv411
AS24482SG.GSHostingIPv4 IPv64
AS35280F5 Networks SARLHostingIPv62

All 11 adjacent →

Provenance

Where this comes from

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