asn.dev

Observed topology

AS267460

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267460: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269014ALLNET TELECOM LTDAUnclassifiedIPv4 IPv6767
AS274487NETGO TELECOM SERVICOS DE TELECOMUNICACAO LTDAUnclassifiedIPv4 IPv634
AS269433LINK TELECOM SERVICOS DE INTERNET LTDA.ResidentialIPv632

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS269014ALLNET TELECOM LTDAUnclassifiedIPv4 IPv61,517
AS274487NETGO TELECOM SERVICOS DE TELECOMUNICACAO LTDAUnclassifiedIPv4 IPv634
AS269433LINK TELECOM SERVICOS DE INTERNET LTDA.ResidentialIPv632
AS24482SG.GSHostingIPv4 IPv620
AS6939Hurricane Electric LLCTransitIPv617
AS35280F5 Networks SARLHostingIPv4 IPv616
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv616
AS270551CORELINK CONECT SEG E TRANSP DE DADOS LTDAUnclassifiedIPv614

Provenance

Where this comes from

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