asn.dev

Observed topology

AS264017 WLAN SOLUCOES TECNOLOGICAS

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264017: 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
AS267613ELETRONET S.A.UnclassifiedIPv4 IPv6137
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv663
AS52925Ascenty Data Centers e Telecomunicacoes S/AUnclassifiedIPv4 IPv662
AS28649Desktop Sigmanet Comunicacao Multimidia SAResidentialIPv449
AS6939Hurricane Electric LLCTransitIPv4 IPv646
AS1031PEER 1031 LLCUnclassifiedIPv412
AS24482SG.GSHostingIPv4 IPv63
AS24961WIIT AGHostingIPv42
AS35280F5 Networks SARLHostingIPv62
AS37721Virtual Technologies & SolutionsResidentialIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS14463TDKOM INFORMATICA LTDAResidentialIPv432

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS267613ELETRONET S.A.UnclassifiedIPv4 IPv6137
AS28649Desktop Sigmanet Comunicacao Multimidia SAResidentialIPv481
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv663
AS52925Ascenty Data Centers e Telecomunicacoes S/AUnclassifiedIPv4 IPv662
AS6939Hurricane Electric LLCTransitIPv4 IPv646
AS14463TDKOM INFORMATICA LTDAResidentialIPv432
AS1031PEER 1031 LLCUnclassifiedIPv412
AS24482SG.GSHostingIPv4 IPv63
AS24961WIIT AGHostingIPv42
AS35280F5 Networks SARLHostingIPv62

All 11 adjacent →

Provenance

Where this comes from

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