Observed topology
AS263649 AS263649 - BrPhonia Provedor Ip Ltda
Residential LACNIC
Transit
Upstream networks
Networks observed carrying traffic for AS263649: 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 |
|---|---|---|---|---|
| AS53062 | GGNET TELECOMUNICACOES LTDA | Unclassified | IPv4 IPv6 | 303 |
| AS28283 | Adylnet Telecom | Residential | IPv4 IPv6 | 153 |
| AS1031 | PEER 1031 LLC | Unclassified | IPv4 IPv6 | 124 |
| AS999 | CORIX NETWORKS | Unclassified | IPv4 | 108 |
| AS52863 | UPX TECNOLOGIA LTDA | Unclassified | IPv4 | 56 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 24 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 16 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 12 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 4 |
| AS35280 | F5 Networks SARL | Hosting | IPv6 | 2 |
Transit
Downstream networks
Networks for which AS263649 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS272053 | ANTUNES FLORES SERGIO OMAR (NUEVA NET) | Unclassified | IPv4 IPv6 | 478 |
| AS263543 | Butzen e Mentges Ltda | Unclassified | IPv4 IPv6 | 105 |
| AS270272 | ZIRR & HEIMERDINGER LTDA | Unclassified | IPv4 IPv6 | 102 |
| AS266375 | R. N. Informatica Ltda - ME | Unclassified | IPv4 IPv6 | 87 |
| AS268682 | G.M.BALLE - ME | Unclassified | IPv4 IPv6 | 55 |
Adjacency
Adjacent networks
Every AS seen directly next to AS263649 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS53062 | GGNET TELECOMUNICACOES LTDA | Unclassified | IPv4 IPv6 | 921 |
| AS272053 | ANTUNES FLORES SERGIO OMAR (NUEVA NET) | Unclassified | IPv4 IPv6 | 478 |
| AS28283 | Adylnet Telecom | Residential | IPv4 IPv6 | 328 |
| AS1031 | PEER 1031 LLC | Unclassified | IPv4 IPv6 | 138 |
| AS999 | CORIX NETWORKS | Unclassified | IPv4 | 108 |
| AS263543 | Butzen e Mentges Ltda | Unclassified | IPv4 IPv6 | 105 |
| AS270272 | ZIRR & HEIMERDINGER LTDA | Unclassified | IPv4 IPv6 | 102 |
| AS266375 | R. N. Informatica Ltda - ME | Unclassified | IPv4 IPv6 | 87 |
| AS52863 | UPX TECNOLOGIA LTDA | Unclassified | IPv4 | 56 |
| AS268682 | G.M.BALLE - ME | Unclassified | IPv4 IPv6 | 55 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M 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.