Observed topology

AS262813 Superimagem Tecnologia em Eletronica Ltda

Residential LACNIC

Upstreams 4 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262813: 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
AS263047	CORP BR TELECOMUNICACOES LTDA - LINK FULL	Unclassified	IPv4 IPv6	2,260
AS4230	CLARO S.A.	Residential	IPv4 IPv6	747
AS264226	ADVANCED CONNECTION TELECOM LTDA-ME	Unclassified	IPv4	50
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	34

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS265917	RJ NET BRASIL TELECOM LTDA	Unclassified	IPv4 IPv6	75

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS263047	CORP BR TELECOMUNICACOES LTDA - LINK FULL	Unclassified	IPv4 IPv6	2,288
AS4230	CLARO S.A.	Residential	IPv4 IPv6	794
AS265917	RJ NET BRASIL TELECOM LTDA	Unclassified	IPv4 IPv6	75
AS264226	ADVANCED CONNECTION TELECOM LTDA-ME	Unclassified	IPv4	50
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	34

Provenance

Where this comes from

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