Observed topology
AS263500 AS263500 - Star Telecom S/A
Unclassified LACNIC NSP
Transit
Upstream networks
Networks observed carrying traffic for AS263500: 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 AS263500 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS263620 | Sertaonet Internet Provider LTDA-ME | Unclassified | IPv4 | 116 |
| AS270296 | HQV INFORMATICA LTDA | Unclassified | IPv4 IPv6 | 86 |
| AS264562 | PBR SERVICOS DE TELECOMUNICACOES LTDA | Residential | IPv4 | 59 |
| AS52700 | ITLINE TELECOM | Unclassified | IPv4 IPv6 | 30 |
| AS274337 | Mario Jose Rocha | Unclassified | IPv6 | 19 |
| AS263022 | CARIRIWEB PROVEDORES DE INTERNET LTDA | Unclassified | IPv4 | 10 |
| AS22689 | SERCOMTEL S/A TELECOMUNICACOES | Unclassified | IPv4 | 4 |
Adjacency
Adjacent networks
Every AS seen directly next to AS263500 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS61568 | ALOO TELECOM - FSF TECNOLOGIA SA | Residential | IPv4 IPv6 | 1,406 |
| AS61832 | DB3 SERVICOS DE TELECOMUNICACOES S.A | Unclassified | IPv4 IPv6 | 225 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 138 |
| AS263620 | Sertaonet Internet Provider LTDA-ME | Unclassified | IPv4 | 116 |
| AS270296 | HQV INFORMATICA LTDA | Unclassified | IPv4 IPv6 | 86 |
| AS264562 | PBR SERVICOS DE TELECOMUNICACOES LTDA | Residential | IPv4 | 59 |
| AS52700 | ITLINE TELECOM | Unclassified | IPv4 IPv6 | 30 |
| AS274337 | Mario Jose Rocha | Unclassified | IPv6 | 19 |
| AS28264 | ADLLink Provedor de Internet Via Radio LTDA | Unclassified | IPv4 IPv6 | 13 |
| AS263022 | CARIRIWEB PROVEDORES DE INTERNET LTDA | Unclassified | IPv4 | 10 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-08 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.