asn.dev

Observed topology

AS262565 AS262565 - CYBER INTERNET LTDA

Hosting APNIC Network Services

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262565: 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
AS52573Une Telecom LtdaResidentialIPv4 IPv6284
AS6939Hurricane Electric LLCTransitIPv4 IPv6266
AS53427TGLOBAL NETWORKSUnclassifiedIPv4163
AS4230CLARO S.A.ResidentialIPv457
AS24482SG.GSHostingIPv4 IPv619
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv619
AS35280F5 Networks SARLHostingIPv46

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS268679Mikol Net Telecomunicacoes LTDA Eirele MEUnclassifiedIPv4183
AS271270JSN SOLUCOES EM TECNOLOGIA LTDAUnclassifiedIPv4 IPv64

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS52573Une Telecom LtdaResidentialIPv4 IPv6387
AS6939Hurricane Electric LLCTransitIPv4 IPv6336
AS268679Mikol Net Telecomunicacoes LTDA Eirele MEUnclassifiedIPv4183
AS53427TGLOBAL NETWORKSUnclassifiedIPv4163
AS4230CLARO S.A.ResidentialIPv457
AS24482SG.GSHostingIPv4 IPv626
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv626
AS35280F5 Networks SARLHostingIPv46
AS271270JSN SOLUCOES EM TECNOLOGIA LTDAUnclassifiedIPv4 IPv64

Provenance

Where this comes from

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