Observed topology

AS271025 FLASHNET PROVEDOR LTDA.ME

Unclassified ARIN

Upstreams 4 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 4

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS271025: 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
AS265066	Conect Provedor de Acesso a Internet Ltda Me	Residential	IPv4 IPv6	217
AS61872	INUV PROVEDOR DE INTERNET LTDA	Residential	IPv4 IPv6	147
AS268076	WEBNET TELECOM	Residential	IPv4 IPv6	128
AS262286	ALAN MARCELO DA SILVA LTDA	Residential	IPv4	44

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS270351	AC Oliveira Comunicacao Ltda	Unclassified	IPv6	37

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS265066	Conect Provedor de Acesso a Internet Ltda Me	Residential	IPv4 IPv6	217
AS61872	INUV PROVEDOR DE INTERNET LTDA	Residential	IPv4 IPv6	184
AS268076	WEBNET TELECOM	Residential	IPv4 IPv6	128
AS262286	ALAN MARCELO DA SILVA LTDA	Residential	IPv4	44
AS270351	AC Oliveira Comunicacao Ltda	Unclassified	IPv6	37

Provenance

Where this comes from

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