asn.dev

Observed topology

AS52850 Oxente.net Solucoes Tecnologicas Eireli

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52850: 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
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv61,585
AS6939Hurricane Electric LLCTransitIPv4 IPv6455

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS266278CABO X PROVEDOR DE INTERNET LTDAUnclassifiedIPv4305
AS274740S.M. DE MATOSUnclassifiedIPv4 IPv6279
AS271305TRX NET SERVICOS DE COMUNICACAO MULTIMIDIA EIRELIUnclassifiedIPv4 IPv6156
AS265913TELEINFOR COMERCIO E SERVICO LTDA-MEUnclassifiedIPv4 IPv6130
AS264935CENTRALNET TELECOMUNICACOES LTDA - MEResidentialIPv416

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv61,899
AS6939Hurricane Electric LLCTransitIPv4 IPv6659
AS16735ALGAR TELECOM S/AUnclassifiedIPv4368
AS266278CABO X PROVEDOR DE INTERNET LTDAUnclassifiedIPv4305
AS274740S.M. DE MATOSUnclassifiedIPv4 IPv6279
AS271305TRX NET SERVICOS DE COMUNICACAO MULTIMIDIA EIRELIUnclassifiedIPv4 IPv6156
AS265913TELEINFOR COMERCIO E SERVICO LTDA-MEUnclassifiedIPv4 IPv6130
AS264935CENTRALNET TELECOMUNICACOES LTDA - MEResidentialIPv416

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.