Observed topology
AS264386 MMM E G TELECOMUNICACOES LTDA - ME
Unclassified LACNIC NSP
Transit
Upstream networks
Networks observed carrying traffic for AS264386: 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 AS264386 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS268164 | ADRIANO CIRILO PASQUAL DONEDA EIRELI | Unclassified | IPv4 IPv6 | 523 |
| AS269650 | ARK TELECOM LTDA - ME | Unclassified | IPv4 IPv6 | 279 |
| AS263374 | YZO TELECOM TECNOLOGIA EIRELI - ME | Unclassified | IPv4 | 222 |
| AS268714 | MURILLO AQUISANER VIEIRA | Unclassified | IPv4 IPv6 | 151 |
| AS267256 | ONETIS TECNOLOGIA LTDA | Unclassified | IPv6 | 66 |
| AS267389 | 5GNET INTERNET | Unclassified | IPv4 | 2 |
Adjacency
Adjacent networks
Every AS seen directly next to AS264386 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS52573 | Une Telecom Ltda | Residential | IPv4 IPv6 | 974 |
| AS273683 | ALLREDE TELECOM LTDA | Residential | IPv4 IPv6 | 839 |
| AS268164 | ADRIANO CIRILO PASQUAL DONEDA EIRELI | Unclassified | IPv4 IPv6 | 523 |
| AS267256 | ONETIS TECNOLOGIA LTDA | Unclassified | IPv4 IPv6 | 398 |
| AS269650 | ARK TELECOM LTDA - ME | Unclassified | IPv4 IPv6 | 279 |
| AS263374 | YZO TELECOM TECNOLOGIA EIRELI - ME | Unclassified | IPv4 | 222 |
| AS268714 | MURILLO AQUISANER VIEIRA | Unclassified | IPv4 IPv6 | 151 |
| AS61657 | Jr Net Informatica Ltda - ME | Residential | IPv4 | 60 |
| AS267389 | 5GNET INTERNET | Unclassified | IPv4 | 2 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-29 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.36M 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.