asn.dev

Observed topology

AS270644 AS270644 - Lagoanet Telecomunicacoes

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS270644: 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
AS266269MV TELECOMUnclassifiedIPv4 IPv692
AS266129LOCALLINK TELECOMUNICACOES LTDA - MEResidentialIPv4 IPv665
AS265335PLANETA NET TELECOMUnclassifiedIPv460
AS266038VN TELECOM PROVEDORES A.R.C EIRELIResidentialIPv459
AS529651TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDAUnclassifiedIPv4 IPv627

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269586ARENNA FIBRA TELECOMUnclassifiedIPv410

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS266269MV TELECOMUnclassifiedIPv4 IPv692
AS266129LOCALLINK TELECOMUNICACOES LTDA - MEResidentialIPv4 IPv665
AS265335PLANETA NET TELECOMUnclassifiedIPv460
AS266038VN TELECOM PROVEDORES A.R.C EIRELIResidentialIPv459
AS529651TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDAUnclassifiedIPv4 IPv627
AS263456MKNETWORK TELECOM LTDA MEResidentialIPv410
AS269586ARENNA FIBRA TELECOMUnclassifiedIPv410

Provenance

Where this comes from

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