asn.dev

Observed topology

AS52795 ONE TELECOM TELECOMUNICACOES LTDA

Unclassified LACNIC NSP

Upstreams 7 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 8
Adjacent (IPv6) 6
Upstream graph Who carries AS52795, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS52795 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52795: 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
AS28283Adylnet TelecomResidentialIPv4 IPv6402
AS6939Hurricane Electric LLCTransitIPv4 IPv6119
AS28343UNIFIQUE TELECOMUNICACOES S/AUnclassifiedIPv442
AS24482SG.GSHostingIPv4 IPv616
AS35280F5 Networks SARLHostingIPv48
AS37721Virtual Technologies & SolutionsResidentialIPv48
AS264409Huge Solucoes Corporativas LtdaUnclassifiedIPv68

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS266647I360 Solucoes para Interacao e Com. Corp. LtdaUnclassifiedIPv4 IPv6287
AS268927HR processamentos de dados ltdaUnclassifiedIPv4 IPv6229

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS28283Adylnet TelecomResidentialIPv4 IPv6666
AS266647I360 Solucoes para Interacao e Com. Corp. LtdaUnclassifiedIPv4 IPv6287
AS6939Hurricane Electric LLCTransitIPv4 IPv6279
AS268927HR processamentos de dados ltdaUnclassifiedIPv4 IPv6229
AS28343UNIFIQUE TELECOMUNICACOES S/AUnclassifiedIPv466
AS264409Huge Solucoes Corporativas LtdaUnclassifiedIPv644
AS24482SG.GSHostingIPv4 IPv632
AS35280F5 Networks SARLHostingIPv416
AS37721Virtual Technologies & SolutionsResidentialIPv416

Provenance

Where this comes from

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