Observed topology
AS270867 AS270867 - Perto Network
Unclassified RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS270867: 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.
Transit
Downstream networks
Networks for which AS270867 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS264498 | Netiz Internet | Residential | IPv4 IPv6 | 818 |
| AS268467 | Voa Internet | Unclassified | IPv4 IPv6 | 444 |
| AS269397 | JUMP NET | Unclassified | IPv4 | 413 |
| AS267315 | GIGABYTE NET PROVEDOR DE INTERNET LTDA | Unclassified | IPv4 IPv6 | 299 |
| AS268268 | LINKNET SERVICOS E COMERCIO LTDA - ME | Residential | IPv4 IPv6 | 213 |
| AS263838 | E&F TECNOLOGIA LTDA | Unclassified | IPv4 IPv6 | 210 |
| AS61598 | SMART DATACENTER LTDA | Unclassified | IPv4 IPv6 | 81 |
| AS268432 | DIGITAL COMUNICACAO VIRTUAL EIRELI | Unclassified | IPv4 | 30 |
| AS263321 | ILOGNET PROVEDOR | Unclassified | IPv4 IPv6 | 29 |
Adjacency
Adjacent networks
Every AS seen directly next to AS270867 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS4230 | CLARO S.A. | Residential | IPv4 IPv6 | 3,502 |
| AS268467 | Voa Internet | Unclassified | IPv4 IPv6 | 992 |
| AS264498 | Netiz Internet | Residential | IPv4 IPv6 | 818 |
| AS268268 | LINKNET SERVICOS E COMERCIO LTDA - ME | Residential | IPv4 IPv6 | 486 |
| AS269397 | JUMP NET | Unclassified | IPv4 | 413 |
| AS263321 | ILOGNET PROVEDOR | Unclassified | IPv4 IPv6 | 346 |
| AS262740 | VELOO NET LTDA | Residential | IPv4 IPv6 | 300 |
| AS267315 | GIGABYTE NET PROVEDOR DE INTERNET LTDA | Unclassified | IPv4 IPv6 | 299 |
| AS263838 | E&F TECNOLOGIA LTDA | Unclassified | IPv4 IPv6 | 210 |
| AS61598 | SMART DATACENTER LTDA | Unclassified | IPv4 IPv6 | 112 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-12 10:00 UTC by route-views2,rrc00, as seen from 75 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.