Observed topology
AS266460 AS266460 - NetGo Telecomunicacoes do Brasil
Residential LACNIC
Transit
Upstream networks
Networks observed carrying traffic for AS266460: 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 |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 244 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 50 |
| AS61832 | DB3 SERVICOS DE TELECOMUNICACOES S.A | Unclassified | IPv4 IPv6 | 36 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 5 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 4 |
| AS28368 | unnamed | Residential | IPv6 | 1 |
Transit
Downstream networks
Networks for which AS266460 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS266650 | QERO TELECOMUNICACOES DO BRASIL LTDA | Unclassified | IPv4 IPv6 | 279 |
| AS61625 | Grupo We Dev LTDA | Residential | IPv4 IPv6 | 245 |
| AS271678 | NATAL FIBRA TELECOMUNICACOES LTDA | Unclassified | IPv4 IPv6 | 213 |
| AS271577 | CLIKPOWER TELECOMUNICACOES EIRELI | Unclassified | IPv4 IPv6 | 154 |
| AS263302 | TORPEDOLINK TELECOM | Unclassified | IPv4 | 122 |
| AS266352 | MUNDO NET | Unclassified | IPv4 IPv6 | 88 |
| AS271151 | RAFAEL DOMINGOS DA SILVA LTDA | Unclassified | IPv4 IPv6 | 69 |
| AS270390 | Evanuel dos Santos Gomes- ME | Unclassified | IPv4 | 61 |
| AS270881 | Netlinknet provedor de acesso a internet eireli-me | Unclassified | IPv4 | 61 |
| AS262818 | g j pereira | Unclassified | IPv4 IPv6 | 39 |
Adjacency
Adjacent networks
Every AS seen directly next to AS266460 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 979 |
| AS61832 | DB3 SERVICOS DE TELECOMUNICACOES S.A | Unclassified | IPv4 IPv6 | 729 |
| AS266650 | QERO TELECOMUNICACOES DO BRASIL LTDA | Unclassified | IPv4 IPv6 | 522 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 397 |
| AS61625 | Grupo We Dev LTDA | Residential | IPv4 IPv6 | 245 |
| AS271678 | NATAL FIBRA TELECOMUNICACOES LTDA | Unclassified | IPv4 IPv6 | 213 |
| AS271577 | CLIKPOWER TELECOMUNICACOES EIRELI | Unclassified | IPv4 IPv6 | 154 |
| AS262818 | g j pereira | Unclassified | IPv4 IPv6 | 126 |
| AS263302 | TORPEDOLINK TELECOM | Unclassified | IPv4 | 122 |
| AS266352 | MUNDO NET | Unclassified | IPv4 IPv6 | 88 |
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.