asn.dev

Observed topology

AS271564 PINHEIRO & SILVA INFORMATICA LTDA

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS271564: 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
AS267587CLICK SPEED SERVICOS DE TELECOMUNICACOES LTDA - EPUnclassifiedIPv4 IPv6387
AS6939Hurricane Electric LLCTransitIPv6115

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS275655VIANET TELECOM LTDAUnclassifiedIPv4 IPv698
AS262663METROFLEX TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv679
AS274498M B LOPES NET-MEUnclassifiedIPv4 IPv652

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS267587CLICK SPEED SERVICOS DE TELECOMUNICACOES LTDA - EPUnclassifiedIPv4 IPv6594
AS6939Hurricane Electric LLCTransitIPv6115
AS275655VIANET TELECOM LTDAUnclassifiedIPv4 IPv698
AS262663METROFLEX TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv679
AS274498M B LOPES NET-MEUnclassifiedIPv4 IPv652
AS61817Halley Telecom Comercio & Servico LtdaUnclassifiedIPv422

Provenance

Where this comes from

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