asn.dev

Observed topology

AS265798 LEVEL SEVEN SRL

Unclassified LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS265798: 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
AS3356Level 3 Parent, LLCTransitIPv4582
AS22927Telefonica de ArgentinaMobileIPv4 IPv6323
AS7303Telecom Argentina S.A.MobileIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271985MEDINA VARGAS JOSE ALEJANDRO (LIRYC)UnclassifiedIPv4 IPv6272
AS273865AREVALO CARLOS ALBERTOUnclassifiedIPv4 IPv6181
AS273965NETIC COMUNICACIONES S.A.S.UnclassifiedIPv4 IPv6156
AS265765Daniel Alejandro Tomsic( RF COMUNICACIONES)UnclassifiedIPv460
AS271887FIBERCOM S.R.L.UnclassifiedIPv458

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv41,024
AS22927Telefonica de ArgentinaMobileIPv4 IPv6608
AS271985MEDINA VARGAS JOSE ALEJANDRO (LIRYC)UnclassifiedIPv4 IPv6272
AS273865AREVALO CARLOS ALBERTOUnclassifiedIPv4 IPv6181
AS273965NETIC COMUNICACIONES S.A.S.UnclassifiedIPv4 IPv6156
AS265765Daniel Alejandro Tomsic( RF COMUNICACIONES)UnclassifiedIPv460
AS271887FIBERCOM S.R.L.UnclassifiedIPv458
AS7303Telecom Argentina S.A.MobileIPv42

Provenance

Where this comes from

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