Observed topology
AS266346 AS266346 - G2G NETWORKS SERVICOS DE COMUNICACAO
Unclassified LACNIC
Transit
Upstream networks
Networks observed carrying traffic for AS266346: 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 |
|---|---|---|---|---|
| AS268624 | Gamers Club Ltda | Unclassified | IPv4 IPv6 | 1,440 |
| AS52571 | G2G COM PROD ELETRO E SERV LTDA | Unclassified | IPv4 IPv6 | 343 |
| AS263601 | Anderson Marcos Coelho e Cia Ltda - ME | Residential | IPv4 | 59 |
| AS28140 | G2G INTERNET E SERVICOS DE TELECOM LTDA | Residential | IPv4 IPv6 | 35 |
| AS52468 | UFINET PANAMA S.A. | Unclassified | IPv6 | 12 |
Transit
Downstream networks
Networks for which AS266346 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 AS266346 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS268624 | Gamers Club Ltda | Unclassified | IPv4 IPv6 | 1,676 |
| AS52571 | G2G COM PROD ELETRO E SERV LTDA | Unclassified | IPv4 IPv6 | 404 |
| AS262623 | NETSALTO PROVEDOR DE ACESSO A INTERNET LTDA | Unclassified | IPv4 | 236 |
| AS263601 | Anderson Marcos Coelho e Cia Ltda - ME | Residential | IPv4 | 118 |
| AS28140 | G2G INTERNET E SERVICOS DE TELECOM LTDA | Residential | IPv4 IPv6 | 35 |
| AS52468 | UFINET PANAMA S.A. | Unclassified | IPv4 IPv6 | 14 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-06 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.