Observed topology

AS271591 TOP NET SERVICOS DE PROVEDOR LTDA - ME

Unclassified LACNIC

Upstreams 5 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 4

Upstream graph Who carries AS271591, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS271591 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS271591: 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
AS271547	RANDSON DE JESUS PASSOS	Unclassified	IPv4	304
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	123
AS28300	Speed Servicos de Internet Ltda	Residential	IPv4 IPv6	84
AS273621	Fonseca Reis Provedor de Internet LTDA	Unclassified	IPv6	64
AS24482	SG.GS	Hosting	IPv4 IPv6	9

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS270749	VTI PROVEDOR DE INTERNET E SUP DE INFORMATICA ME	Unclassified	IPv4	164

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS271547	RANDSON DE JESUS PASSOS	Unclassified	IPv4	445
AS270749	VTI PROVEDOR DE INTERNET E SUP DE INFORMATICA ME	Unclassified	IPv4	164
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	143
AS28300	Speed Servicos de Internet Ltda	Residential	IPv4 IPv6	84
AS273621	Fonseca Reis Provedor de Internet LTDA	Unclassified	IPv6	64
AS24482	SG.GS	Hosting	IPv4 IPv6	12

Provenance

Where this comes from

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