asn.dev

Observed topology

AS266060 AS266060 - DIGIL 360 PROVEDORES DE ACESSO LTDA-ME

Unclassified APNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266060: 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
AS266465COSTA & SILVA LTDA - MEUnclassifiedIPv4 IPv6138
AS266143UP LINK INTERNET BANDA LARGAUnclassifiedIPv4 IPv695
AS272447World FibraUnclassifiedIPv463
AS262300SUPER CONNECT TELECOM LTDAResidentialIPv434
AS263432CORPORATIVA TELECOMUNICACOES EIRELI MEUnclassifiedIPv4 IPv634
AS6939Hurricane Electric LLCTransitIPv426
AS24482SG.GSHostingIPv42
AS35280F5 Networks SARLHostingIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS266465COSTA & SILVA LTDA - MEUnclassifiedIPv4 IPv6138
AS266143UP LINK INTERNET BANDA LARGAUnclassifiedIPv4 IPv695
AS272447World FibraUnclassifiedIPv463
AS262300SUPER CONNECT TELECOM LTDAResidentialIPv434
AS263432CORPORATIVA TELECOMUNICACOES EIRELI MEUnclassifiedIPv4 IPv634
AS6939Hurricane Electric LLCTransitIPv426
AS24482SG.GSHostingIPv42
AS35280F5 Networks SARLHostingIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42

Provenance

Where this comes from

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