Observed topology

AS52533 TRADITIO COMPANHIA DE SEGUROS

Unclassified LACNIC

Upstreams 7 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52533: 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
AS4230	CLARO S.A.	Residential	IPv4	290
AS7738	V tal	Unclassified	IPv4	252
AS3356	Level 3 Parent, LLC	Transit	IPv4	248
AS26615	TIM S/A	Mobile	IPv4	71
AS10429	TELEFONICA BRASIL S.A	Residential	IPv4	37
AS28669	VERO S.A	Residential	IPv4	22
AS22381	SAMM TECNOLOGIA E TELECOMUNICACOES S.A	Unclassified	IPv4	3

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS4230	CLARO S.A.	Residential	IPv4	290
AS7738	V tal	Unclassified	IPv4	252
AS3356	Level 3 Parent, LLC	Transit	IPv4	248
AS26615	TIM S/A	Mobile	IPv4	71
AS10429	TELEFONICA BRASIL S.A	Residential	IPv4	37
AS28669	VERO S.A	Residential	IPv4	22
AS22381	SAMM TECNOLOGIA E TELECOMUNICACOES S.A	Unclassified	IPv4	3

Provenance

Where this comes from

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