asn.dev

Observed topology

AS271255 AS271255 - PEER TELECOM LTDA

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS271255: 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
AS267613ELETRONET S.A.UnclassifiedIPv465
AS13786Seabras 1 USA, LLCUnclassifiedIPv4 IPv659
AS28283Adylnet TelecomResidentialIPv628

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS262316Ateky Internet Eireli MeUnclassifiedIPv4 IPv63,030
AS263527SERRA GERAL SOLUCOES PARA INTERNET LTDAUnclassifiedIPv4 IPv6277
AS262320BANDATURBO TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6238
AS263582PONTO SAT CONECT EIRELI MEResidentialIPv4 IPv670

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS262316Ateky Internet Eireli MeUnclassifiedIPv4 IPv63,030
AS28283Adylnet TelecomResidentialIPv4 IPv62,503
AS13786Seabras 1 USA, LLCUnclassifiedIPv4 IPv61,672
AS263527SERRA GERAL SOLUCOES PARA INTERNET LTDAUnclassifiedIPv4 IPv61,162
AS267613ELETRONET S.A.UnclassifiedIPv4 IPv6686
AS262320BANDATURBO TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6438
AS263582PONTO SAT CONECT EIRELI MEResidentialIPv4 IPv6109
AS6939Hurricane Electric LLCTransitIPv4 IPv627
AS24482SG.GSHostingIPv4 IPv63

Provenance

Where this comes from

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