asn.dev

Observed topology

AS268131 AS268131 - MIX NET TELECOMUNICACOES LTDA - ME

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268131: 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
AS61591WESTLINK TECNOLOGIA E COMUNICACAO LTDA. - MEResidentialIPv4 IPv6495
AS6939Hurricane Electric LLCTransitIPv4 IPv6140
AS24482SG.GSHostingIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS268215ULTRA+ TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6215
AS270633a j ribeiro telecomunicacoesUnclassifiedIPv4 IPv6213

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS61591WESTLINK TECNOLOGIA E COMUNICACAO LTDA. - MEResidentialIPv4 IPv6827
AS6939Hurricane Electric LLCTransitIPv4 IPv6224
AS268215ULTRA+ TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6215
AS270633a j ribeiro telecomunicacoesUnclassifiedIPv4 IPv6213
AS24482SG.GSHostingIPv4 IPv612
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv612

Provenance

Where this comes from

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