asn.dev

Observed topology

AS274692 AS274692 - UNIQUELINK PROVEDOR DE INTERNET

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS274692: 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
AS263966WORLD WIFI TELECOMUNICACOES LTDA - MEResidentialIPv622
AS6939Hurricane Electric LLCTransitIPv616
AS28189JR & JS ENGENHARIA E COMERCIO LTDAUnclassifiedIPv612
AS24482SG.GSHostingIPv61
AS35280F5 Networks SARLHostingIPv61
AS37721Virtual Technologies & SolutionsResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS268577LIGEIRO FIBRA TELECOM LTDAUnclassifiedIPv461

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS268577LIGEIRO FIBRA TELECOM LTDAUnclassifiedIPv461
AS263966WORLD WIFI TELECOMUNICACOES LTDA - MEResidentialIPv4 IPv650
AS28189JR & JS ENGENHARIA E COMERCIO LTDAUnclassifiedIPv4 IPv633
AS6939Hurricane Electric LLCTransitIPv4 IPv627
AS24482SG.GSHostingIPv4 IPv62
AS35280F5 Networks SARLHostingIPv61
AS37721Virtual Technologies & SolutionsResidentialIPv61

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.