asn.dev

Observed topology

AS264420 AS264420 - TurboNet Telecom

Unclassified LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264420: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6122
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv692
AS53087TELY Ltda.ResidentialIPv4 IPv682
AS24482SG.GSHostingIPv4 IPv69
AS35280F5 Networks SARLHostingIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS265268Smart Solucoes TecnologicasUnclassifiedIPv4 IPv6254
AS274646EDILSON M DE ARAUJOUnclassifiedIPv4 IPv691
AS269486R.R SOARES INTERNETUnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS265268Smart Solucoes TecnologicasUnclassifiedIPv4 IPv6813
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6662
AS53087TELY Ltda.ResidentialIPv4 IPv6310
AS6939Hurricane Electric LLCTransitIPv4 IPv6270
AS274646EDILSON M DE ARAUJOUnclassifiedIPv4 IPv691
AS269486R.R SOARES INTERNETUnclassifiedIPv460
AS24482SG.GSHostingIPv4 IPv623
AS35280F5 Networks SARLHostingIPv4 IPv68
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv68

Provenance

Where this comes from

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