Observed topology
AS269530 ACCESSNET TELECOMUNICACOES EIRELI
Residential LACNIC
Transit
Upstream networks
Networks observed carrying traffic for AS269530: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 150 |
| AS262503 | WIKI TELECOMUNICACOES EIRELI | Unclassified | IPv4 IPv6 | 104 |
| AS265269 | MEGA TELE INFORMATICA | Unclassified | IPv4 IPv6 | 87 |
| AS271201 | Vianet Telecomunicacoes Ltda | Residential | IPv4 IPv6 | 68 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 10 |
| AS35280 | F5 Networks SARL | Hosting | IPv4 IPv6 | 8 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 8 |
Transit
Downstream networks
Networks for which AS269530 was observed as the last hop before the origin, meaning it appears to provide them transit.
Adjacency
Adjacent networks
Every AS seen directly next to AS269530 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS265269 | MEGA TELE INFORMATICA | Unclassified | IPv4 IPv6 | 215 |
| AS271201 | Vianet Telecomunicacoes Ltda | Residential | IPv4 IPv6 | 184 |
| AS262503 | WIKI TELECOMUNICACOES EIRELI | Unclassified | IPv4 IPv6 | 164 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 150 |
| AS274389 | F-NET MASTER LTDA | Unclassified | IPv4 IPv6 | 150 |
| AS270885 | VITORIA NET | Unclassified | IPv4 | 53 |
| AS271493 | SPEED NET PEDRA | Unclassified | IPv4 IPv6 | 46 |
| AS270657 | FNET TELECOM | Unclassified | IPv4 IPv6 | 40 |
| AS271608 | plus internet telecom | Unclassified | IPv4 IPv6 | 18 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 13 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-25 12:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.