Observed topology

AS264385 AS264385 - Itop Internet e Servicos LTDA

Unclassified LACNIC

Upstreams 5 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264385: 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
AS270724	CLIENT.CO SERVICOS E TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	166
AS268568	IMPLANTAR TELECOM SOCIEDADE LIMITADA	Unclassified	IPv4 IPv6	162
AS21574	Century Telecom Ltda	Unclassified	IPv4 IPv6	119
AS266260	ITOP TELECOM LTDA - ME	Residential	IPv4	58
AS266525	Eurocorp Vialux Internet Eireli	Residential	IPv4	58

Transit

Downstream networks

inferred

Networks for which AS264385 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 AS264385 in a routing path, in either direction.

AS	Network	Type	Families	Paths seen
AS270724	CLIENT.CO SERVICOS E TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	166
AS268568	IMPLANTAR TELECOM SOCIEDADE LIMITADA	Unclassified	IPv4 IPv6	162
AS21574	Century Telecom Ltda	Unclassified	IPv4 IPv6	119
AS266260	ITOP TELECOM LTDA - ME	Residential	IPv4	58
AS266525	Eurocorp Vialux Internet Eireli	Residential	IPv4	58

Provenance

Where this comes from

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