asn.dev

Observed topology

AS270007 AS270007 - MORENO YANOC NEMIAS BERNARDO

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS270007: 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
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv6603
AS64130M & B Soluciones Peru S.A.C. (FASTNET)UnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS274113CINTELSUR PERU S.A.C.UnclassifiedIPv4 IPv6500
AS270076EXA NETWORKS S.A.C.UnclassifiedIPv4399
AS273209CABLE STAR TV SACUnclassifiedIPv4 IPv6115
AS274156TELDRA S.A.C.UnclassifiedIPv476

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv61,693
AS274113CINTELSUR PERU S.A.C.UnclassifiedIPv4 IPv6500
AS270076EXA NETWORKS S.A.C.UnclassifiedIPv4399
AS273209CABLE STAR TV SACUnclassifiedIPv4 IPv6115
AS274156TELDRA S.A.C.UnclassifiedIPv476
AS64130M & B Soluciones Peru S.A.C. (FASTNET)UnclassifiedIPv42

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.