asn.dev

Observed topology

AS270581 JET NETWORK TELECOMUNICACAO LTDA

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS270581: 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
AS270735COMPUTIZE NETWORK TELECOMUNICACOES LTDAHostingIPv4 IPv6200
AS270340NETCOM TELECOMUNICACOES LTDAResidentialIPv4 IPv618
AS24482SG.GSHostingIPv64
AS37721Virtual Technologies & SolutionsResidentialIPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271363P.S.H. DO COUTO TELECOMUNICACAO-MEUnclassifiedIPv4 IPv6166
AS271381WORD INTERNET SERVICOS DE FIBRA OTICA MEUnclassifiedIPv4 IPv681
AS268295PEDRO ANTONIO TAVARES MEUnclassifiedIPv4 IPv674
AS272626N9 TELECOM by LigpronetUnclassifiedIPv422

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS270735COMPUTIZE NETWORK TELECOMUNICACOES LTDAHostingIPv4 IPv6492
AS271363P.S.H. DO COUTO TELECOMUNICACAO-MEUnclassifiedIPv4 IPv6166
AS271381WORD INTERNET SERVICOS DE FIBRA OTICA MEUnclassifiedIPv4 IPv681
AS268295PEDRO ANTONIO TAVARES MEUnclassifiedIPv4 IPv674
AS270340NETCOM TELECOMUNICACOES LTDAResidentialIPv4 IPv663
AS272626N9 TELECOM by LigpronetUnclassifiedIPv422
AS24482SG.GSHostingIPv4 IPv610
AS37721Virtual Technologies & SolutionsResidentialIPv64

Provenance

Where this comes from

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