asn.dev

Observed topology

AS53020 IDT Brasil Telecomunicacoes Ltda.

Unclassified LACNIC Enterprise

Upstreams 9 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 9
Adjacent (IPv6) 0
Upstream graph Who carries AS53020, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS53020 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS53020: 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.

ASNetworkTypeFamiliesPaths seen
AS198949Radware LtdUnclassifiedIPv4257
AS3356Level 3 Parent, LLCTransitIPv465
AS4230CLARO S.A.ResidentialIPv435
AS6939Hurricane Electric LLCTransitIPv429
AS263452Ativas Data Center S.A.UnclassifiedIPv415
AS16735ALGAR TELECOM S/AUnclassifiedIPv412
AS52925Ascenty Data Centers e Telecomunicacoes S/AUnclassifiedIPv44
AS24482SG.GSHostingIPv43
AS37721Virtual Technologies & SolutionsResidentialIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS198949Radware LtdUnclassifiedIPv4257
AS3356Level 3 Parent, LLCTransitIPv465
AS4230CLARO S.A.ResidentialIPv435
AS6939Hurricane Electric LLCTransitIPv429
AS263452Ativas Data Center S.A.UnclassifiedIPv415
AS16735ALGAR TELECOM S/AUnclassifiedIPv412
AS52925Ascenty Data Centers e Telecomunicacoes S/AUnclassifiedIPv44
AS24482SG.GSHostingIPv43
AS37721Virtual Technologies & SolutionsResidentialIPv42

Provenance

Where this comes from

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