Observed topology
AS263145 GRUPO MEGA FLASH SERVICOS E COM LTDA - EPP
Residential LACNIC
Transit
Upstream networks
Networks observed carrying traffic for AS263145: 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 AS263145 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS269409 | Rio Online Telecomunicacoes e Informatica Ltda Me | Unclassified | IPv4 IPv6 | 514 |
| AS272575 | DELTA R SEGURANCA E SERVICOS | Unclassified | IPv4 IPv6 | 104 |
| AS266958 | Net Telecom MD Ltda-ME | Unclassified | IPv4 IPv6 | 91 |
| AS269700 | EVOLUTION PROVEDORES E INFORMATICA LTDA-ME | Unclassified | IPv4 IPv6 | 91 |
| AS267072 | VELOZ NET SERVICOS E COMUNICACOES LTDA | Unclassified | IPv6 | 16 |
| AS272613 | INET DO BRASIL TELECOMUNICACOES EIRELI | Unclassified | IPv6 | 10 |
Adjacency
Adjacent networks
Every AS seen directly next to AS263145 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS53181 | Avanca Telecom e Servicos LTDA | Unclassified | IPv4 IPv6 | 737 |
| AS269409 | Rio Online Telecomunicacoes e Informatica Ltda Me | Unclassified | IPv4 IPv6 | 514 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 357 |
| AS269311 | DNET BRASIL LTDA | Unclassified | IPv4 IPv6 | 160 |
| AS272613 | INET DO BRASIL TELECOMUNICACOES EIRELI | Unclassified | IPv4 IPv6 | 157 |
| AS272575 | DELTA R SEGURANCA E SERVICOS | Unclassified | IPv4 IPv6 | 104 |
| AS266958 | Net Telecom MD Ltda-ME | Unclassified | IPv4 IPv6 | 91 |
| AS269700 | EVOLUTION PROVEDORES E INFORMATICA LTDA-ME | Unclassified | IPv4 IPv6 | 91 |
| AS267072 | VELOZ NET SERVICOS E COMUNICACOES LTDA | Unclassified | IPv6 | 16 |
| AS263009 | FORTE TELECOM LTDA. | Hosting | IPv4 | 8 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-21 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.