Observed topology
AS266201 AS266201 - VERO S.A
Residential ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS266201: 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 AS266201 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS263297 | VERO S.A | Residential | IPv4 IPv6 | 1,686 |
| AS264555 | TECCLOUD SERVICOS DE TECNOLOGIA AHU LTDA. | Unclassified | IPv4 | 474 |
| AS267243 | NET 10 LTDA ME | Unclassified | IPv4 IPv6 | 333 |
| AS269068 | Plus Networks | Unclassified | IPv4 IPv6 | 159 |
| AS271665 | FBT NET LTDA | Unclassified | IPv4 IPv6 | 125 |
| AS265141 | RBT Internet | Residential | IPv4 | 118 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 IPv6 | 92 |
| AS273401 | UOLNET PROVEDORES DE INTERNET | Unclassified | IPv4 IPv6 | 92 |
| AS53061 | G2NET SUL PROVEDOR LTDA | Residential | IPv4 | 82 |
| AS269300 | NETMITT IMP & MULTIMIDIA EIRELI | Unclassified | IPv4 | 55 |
Adjacency
Adjacent networks
Every AS seen directly next to AS266201 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS267613 | ELETRONET S.A. | Unclassified | IPv4 IPv6 | 2,823 |
| AS263297 | VERO S.A | Residential | IPv4 IPv6 | 1,686 |
| AS13786 | Seabras 1 USA, LLC | Unclassified | IPv4 IPv6 | 702 |
| AS264555 | TECCLOUD SERVICOS DE TECNOLOGIA AHU LTDA. | Unclassified | IPv4 | 474 |
| AS267243 | NET 10 LTDA ME | Unclassified | IPv4 IPv6 | 333 |
| AS269068 | Plus Networks | Unclassified | IPv4 IPv6 | 159 |
| AS53061 | G2NET SUL PROVEDOR LTDA | Residential | IPv4 IPv6 | 127 |
| AS271665 | FBT NET LTDA | Unclassified | IPv4 IPv6 | 125 |
| AS265141 | RBT Internet | Residential | IPv4 | 118 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 IPv6 | 92 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.