asn.dev

Observed topology

AS262689 AS262689 - UNOUN INTERNET LTDA

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262689: 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
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv4 IPv6883
AS61598SMART DATACENTER LTDAUnclassifiedIPv431
AS6939Hurricane Electric LLCTransitIPv4 IPv629
AS52711FASTNET TELECOMUnclassifiedIPv4 IPv621
AS24482SG.GSHostingIPv4 IPv62
AS35280F5 Networks SARLHostingIPv4 IPv62
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS268467Voa InternetUnclassifiedIPv648
AS61598SMART DATACENTER LTDAUnclassifiedIPv415

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv4 IPv6965
AS268467Voa InternetUnclassifiedIPv4 IPv688
AS6939Hurricane Electric LLCTransitIPv4 IPv648
AS61598SMART DATACENTER LTDAUnclassifiedIPv446
AS52711FASTNET TELECOMUnclassifiedIPv4 IPv621
AS24482SG.GSHostingIPv4 IPv64
AS35280F5 Networks SARLHostingIPv4 IPv62
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv62

Provenance

Where this comes from

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