asn.dev

Observed topology

AS270372 CEUNET TELECOM EIRELI

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS270372: 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
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6151
AS52573Une Telecom LtdaResidentialIPv4 IPv6126
AS28178Networld Provedor e Servicos de Internet LtdaUnclassifiedIPv4 IPv693
AS24482SG.GSHostingIPv4 IPv66
AS35280F5 Networks SARLHostingIPv4 IPv63
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv63
AS266207Onitel TelecomunicacoesUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271218AL TELECOM - TELECOMUNICACOES LTDAUnclassifiedIPv462

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS52573Une Telecom LtdaResidentialIPv4 IPv6188
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6151
AS28178Networld Provedor e Servicos de Internet LtdaUnclassifiedIPv4 IPv693
AS271218AL TELECOM - TELECOMUNICACOES LTDAUnclassifiedIPv462
AS24482SG.GSHostingIPv4 IPv66
AS35280F5 Networks SARLHostingIPv4 IPv63
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv63
AS266207Onitel TelecomunicacoesUnclassifiedIPv41

Provenance

Where this comes from

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