Observed topology

AS271564 AS271564 - PINHEIRO & SILVA INFORMATICA LTDA

Residential APNIC

Upstreams 3 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 6

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.

AS	Network	Type	Families	Paths seen
AS267587	CLICK SPEED SERVICOS DE TELECOMUNICACOES LTDA - EP	Unclassified	IPv4 IPv6	248
AS6939	Hurricane Electric LLC	Transit	IPv6	102
AS270984	MVM PINTO COMERCIO E SERVICOS ME	Unclassified	IPv4 IPv6	22

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS275655	VIANET TELECOM LTDA	Unclassified	IPv4 IPv6	97
AS262663	METROFLEX TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	92
AS274498	M B LOPES NET-ME	Unclassified	IPv4 IPv6	51

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS267587	CLICK SPEED SERVICOS DE TELECOMUNICACOES LTDA - EP	Unclassified	IPv4 IPv6	470
AS6939	Hurricane Electric LLC	Transit	IPv6	102
AS275655	VIANET TELECOM LTDA	Unclassified	IPv4 IPv6	97
AS262663	METROFLEX TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	92
AS274498	M B LOPES NET-ME	Unclassified	IPv4 IPv6	51
AS270984	MVM PINTO COMERCIO E SERVICOS ME	Unclassified	IPv4 IPv6	22
AS61817	Halley Telecom Comercio & Servico Ltda	Unclassified	IPv4	18

Provenance

Where this comes from

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