Observed topology

AS264397 SUPRANET TELECOM INFORMATICA LTDA

Residential LACNIC

Upstreams 6 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 6

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264397: 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 IPv6	238
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	223
AS267613	ELETRONET S.A.	Unclassified	IPv4 IPv6	50
AS24482	SG.GS	Hosting	IPv4 IPv6	15
AS37721	Virtual Technologies & Solutions	Residential	IPv4 IPv6	14
AS35280	F5 Networks SARL	Hosting	IPv4 IPv6	12

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS28590	Directnet Prestacao de Servicos Ltda.	Unclassified	IPv4	60
AS267529	KNS DE PINHO TELECOMUNICACOES	Unclassified	IPv4	27

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS3356	Level 3 Parent, LLC	Transit	IPv4 IPv6	276
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	253
AS267613	ELETRONET S.A.	Unclassified	IPv4 IPv6	65
AS28590	Directnet Prestacao de Servicos Ltda.	Unclassified	IPv4	60
AS267529	KNS DE PINHO TELECOMUNICACOES	Unclassified	IPv4	27
AS24482	SG.GS	Hosting	IPv4 IPv6	17
AS37721	Virtual Technologies & Solutions	Residential	IPv4 IPv6	15
AS35280	F5 Networks SARL	Hosting	IPv4 IPv6	13

Provenance

Where this comes from

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