asn.dev

Observed topology

AS265336 ELneT Telecom

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS265336: 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
AS52554A. da Silva JuniorUnclassifiedIPv689
AS3356Level 3 Parent, LLCTransitIPv4 IPv676
AS263151TELECOMResidentialIPv4 IPv623
AS52720TELECOMUNICACOES LTDAUnclassifiedIPv46
AS24482SG.GSHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271589MEUnclassifiedIPv4 IPv6395
AS270414TELECOM SERVICOS E COMERCIOS LTDAResidentialIPv4 IPv6299
AS270264INTERNETUnclassifiedIPv4 IPv676
AS262663TELECOMUNICACOES LTDAUnclassifiedIPv452
AS272601GOMES VASCONECELOS BARRETO SANTANUnclassifiedIPv635
AS263556INDUSTRIA NAVAL S.A.UnclassifiedIPv428
AS269139TELECOMUnclassifiedIPv4 IPv67

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6677
AS271589MEUnclassifiedIPv4 IPv6395
AS269139TELECOMUnclassifiedIPv4 IPv6315
AS270414TELECOM SERVICOS E COMERCIOS LTDAResidentialIPv4 IPv6299
AS272601GOMES VASCONECELOS BARRETO SANTANUnclassifiedIPv4 IPv6156
AS52554A. da Silva JuniorUnclassifiedIPv4 IPv6144
AS263151TELECOMResidentialIPv4 IPv6111
AS52720TELECOMUNICACOES LTDAUnclassifiedIPv494
AS270264INTERNETUnclassifiedIPv4 IPv676
AS262663TELECOMUNICACOES LTDAUnclassifiedIPv452

All 13 adjacent →

Provenance

Where this comes from

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