Observed topology
AS263427 AS263427 - Carlos Henrique Santos de Oliveira ME
Unclassified APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS263427: 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 |
|---|---|---|---|---|
| AS14840 | BR.Digital Telecom | Unclassified | IPv4 IPv6 | 325 |
| AS37468 | Angola Cables | Unclassified | IPv4 IPv6 | 292 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 270 |
| AS268925 | SIGA CORP LTDA | Unclassified | IPv4 IPv6 | 64 |
| AS263327 | ONLINE TELECOMUNICACOES LTDA | Residential | IPv4 | 60 |
| AS264562 | PBR SERVICOS DE TELECOMUNICACOES LTDA | Residential | IPv4 | 54 |
| AS264969 | FD CAVALCANTE DE LIMA ME | Unclassified | IPv4 | 51 |
| AS272794 | CONECTAMAX COMERCIO E SERVICOS | Unclassified | IPv4 | 18 |
Transit
Downstream networks
Networks for which AS263427 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 AS263427 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS14840 | BR.Digital Telecom | Unclassified | IPv4 IPv6 | 529 |
| AS37468 | Angola Cables | Unclassified | IPv4 IPv6 | 381 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 270 |
| AS266975 | EURONET TELECOM | Residential | IPv4 IPv6 | 155 |
| AS270346 | FULLNET CE | Residential | IPv4 IPv6 | 86 |
| AS268925 | SIGA CORP LTDA | Unclassified | IPv4 IPv6 | 64 |
| AS263327 | ONLINE TELECOMUNICACOES LTDA | Residential | IPv4 | 60 |
| AS264562 | PBR SERVICOS DE TELECOMUNICACOES LTDA | Residential | IPv4 | 54 |
| AS264969 | FD CAVALCANTE DE LIMA ME | Unclassified | IPv4 | 51 |
| AS269014 | ALLNET TELECOM LTDA | Unclassified | IPv6 | 46 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.46M 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.