asn.dev

Observed topology

AS264206 Mixconect Telecom Ltda ME

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264206: 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
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6125
AS3356Level 3 Parent, LLCTransitIPv4 IPv678
AS6939Hurricane Electric LLCTransitIPv673
AS24482SG.GSHostingIPv43
AS35280F5 Networks SARLHostingIPv63
AS268296BARRANET TELECOMUNICACOES LTDAUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS264089Nova Telecom LtdaUnclassifiedIPv4126
AS268296BARRANET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv666
AS263554PERSIO SGUBIN JR. & CIA. LTDA. - BLACK WINDOW INTEUnclassifiedIPv4 IPv635

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6274
AS3356Level 3 Parent, LLCTransitIPv4 IPv6151
AS264089Nova Telecom LtdaUnclassifiedIPv4126
AS6939Hurricane Electric LLCTransitIPv673
AS268296BARRANET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv667
AS263554PERSIO SGUBIN JR. & CIA. LTDA. - BLACK WINDOW INTEUnclassifiedIPv4 IPv635
AS24482SG.GSHostingIPv48
AS35280F5 Networks SARLHostingIPv63

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.