Observed topology

AS265139 AS265139 - OXENTE NET EMPREENDIMENTOS LTDA - EPP

Unclassified APNIC Cable/DSL/ISP

Upstreams 1 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 5

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS265139: 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
AS262494	Virtex Telecom	Residential	IPv4 IPv6	443

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS272711	Provedor Netlink de Campo Alegre de Lourdes LTDA	Unclassified	IPv4 IPv6	153
AS268314	EWERTON DA SILVA LOPES TELECOMUNICACOES	Unclassified	IPv4 IPv6	90
AS267567	Radiun Servicos de Provedor de Internet LTDA	Residential	IPv4 IPv6	57
AS273530	Joao Gomes de Sousa Neto-ME	Unclassified	IPv6	32

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS262494	Virtex Telecom	Residential	IPv4 IPv6	946
AS272711	Provedor Netlink de Campo Alegre de Lourdes LTDA	Unclassified	IPv4 IPv6	267
AS268314	EWERTON DA SILVA LOPES TELECOMUNICACOES	Unclassified	IPv4 IPv6	90
AS273530	Joao Gomes de Sousa Neto-ME	Unclassified	IPv4 IPv6	89
AS267567	Radiun Servicos de Provedor de Internet LTDA	Residential	IPv4 IPv6	57

Provenance

Where this comes from

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