Observed topology
AS264288 GNET PROVEDOR
Residential LACNIC
Transit
Upstream networks
Networks observed carrying traffic for AS264288: 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 |
|---|---|---|---|---|
| AS61568 | ALOO TELECOM - FSF TECNOLOGIA SA | Residential | IPv4 IPv6 | 122 |
| AS14840 | BR.Digital Telecom | Unclassified | IPv4 | 119 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 100 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 63 |
| AS61832 | DB3 SERVICOS DE TELECOMUNICACOES S.A | Unclassified | IPv4 IPv6 | 44 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 8 |
Transit
Downstream networks
Networks for which AS264288 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS267048 | PROVEDORES SERVICO EQUIPAMENTO NIVE NET EIRELI | Unclassified | IPv4 IPv6 | 672 |
| AS265426 | SS TELECOM LTDA | Residential | IPv4 IPv6 | 448 |
| AS271168 | JJ DOS SANTOS SERVICO DE COMUNICACAO ME | Unclassified | IPv4 | 357 |
| AS266049 | Rede.com Telecom Ltda - ME | Unclassified | IPv4 IPv6 | 312 |
| AS52709 | w de c canto junior | Unclassified | IPv4 IPv6 | 276 |
| AS269274 | VIANET TELECOM | Unclassified | IPv4 IPv6 | 252 |
| AS267143 | CM Net Servicos de Comunicacao Multimidia LTDA | Unclassified | IPv4 | 250 |
| AS270727 | Web Connect | Hosting | IPv4 IPv6 | 232 |
| AS61831 | GIGANET PROVEDOR DE INTERNET LTDA | Unclassified | IPv4 IPv6 | 230 |
| AS268381 | NASCIMENTO & FILHO LTDA ME | Unclassified | IPv4 IPv6 | 206 |
Adjacency
Adjacent networks
Every AS seen directly next to AS264288 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS61568 | ALOO TELECOM - FSF TECNOLOGIA SA | Residential | IPv4 IPv6 | 2,091 |
| AS14840 | BR.Digital Telecom | Unclassified | IPv4 IPv6 | 1,375 |
| AS61832 | DB3 SERVICOS DE TELECOMUNICACOES S.A | Unclassified | IPv4 IPv6 | 1,086 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 759 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 705 |
| AS267048 | PROVEDORES SERVICO EQUIPAMENTO NIVE NET EIRELI | Unclassified | IPv4 IPv6 | 672 |
| AS265426 | SS TELECOM LTDA | Residential | IPv4 IPv6 | 609 |
| AS266049 | Rede.com Telecom Ltda - ME | Unclassified | IPv4 IPv6 | 607 |
| AS266934 | G5 TELECOM | Unclassified | IPv4 IPv6 | 501 |
| AS265311 | Bezerra Speed Internet | Residential | IPv4 IPv6 | 398 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-11 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.47M 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.