Observed topology

AS270585 Rodrigo de Mello Goncalves Lopes ME

Unclassified APNIC Cable/DSL/ISP

Upstreams 5 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS270585: 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
AS3356	Level 3 Parent, LLC	Transit	IPv4	303
AS268624	Gamers Club Ltda	Unclassified	IPv4 IPv6	139
AS53062	GGNET TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	57
AS271253	LINK BRASIL TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	17
AS22356	Durand do Brasil Ltda	Unclassified	IPv4	10

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS3356	Level 3 Parent, LLC	Transit	IPv4	304
AS268624	Gamers Club Ltda	Unclassified	IPv4 IPv6	139
AS271253	LINK BRASIL TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	63
AS53062	GGNET TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	60
AS274384	VELIZ INTERNET E SERVICOS LTDA	Unclassified	IPv4 IPv6	50
AS22356	Durand do Brasil Ltda	Unclassified	IPv4	10

Provenance

Where this comes from

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