asn.dev

Observed topology

AS269138 MOV TELECOM SERVICOS DE PROVEDORES DE INTERNET LTD

Unclassified LACNIC

Upstreams 6 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 8
Adjacent (IPv6) 9
Upstream graph Who carries AS269138, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS269138 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269138: 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.

ASNetworkTypeFamiliesPaths seen
AS11432Telium Telecomunicacoes LtdaHostingIPv4 IPv6151
AS6939Hurricane Electric LLCTransitIPv4 IPv6126
AS40850UPIX NETWORKS INTERNATIONAL LLCUnclassifiedIPv4 IPv6119
AS24482SG.GSHostingIPv4 IPv610
AS35280F5 Networks SARLHostingIPv4 IPv68
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv68

Transit

Downstream networks

inferred

Networks for which AS269138 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS269118GTN-TELECOM INTERNET LTDA-MEUnclassifiedIPv4 IPv6287
AS271358AP INTERNETUnclassifiedIPv4 IPv6132

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS269138 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS11432Telium Telecomunicacoes LtdaHostingIPv4 IPv6327
AS269118GTN-TELECOM INTERNET LTDA-MEUnclassifiedIPv4 IPv6287
AS40850UPIX NETWORKS INTERNATIONAL LLCUnclassifiedIPv4 IPv6238
AS6939Hurricane Electric LLCTransitIPv4 IPv6230
AS271358AP INTERNETUnclassifiedIPv4 IPv6132
AS24482SG.GSHostingIPv4 IPv621
AS35280F5 Networks SARLHostingIPv4 IPv612
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv612
AS268684PONTO CERTO INTERNETResidentialIPv61

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-31 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.50M 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.