asn.dev

Observed topology

AS267963 HAYAN TELECOM

Unclassified LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267963: 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
AS263661BRASIL DIGITAL SERVICOS DE INFORMATICA E COMERCIOResidentialIPv4 IPv695
AS6939Hurricane Electric LLCTransitIPv4 IPv683
AS262901Vcnet Provedora de Internet Ltda.UnclassifiedIPv4 IPv658
AS262317ROS TelecomResidentialIPv4 IPv653
AS263075TV Cabo de Santo Anastacio LtdaUnclassifiedIPv4 IPv639
AS529651TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDAUnclassifiedIPv4 IPv624

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271732K SILVA OLIVEIRAUnclassifiedIPv4 IPv632

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS263661BRASIL DIGITAL SERVICOS DE INFORMATICA E COMERCIOResidentialIPv4 IPv695
AS6939Hurricane Electric LLCTransitIPv4 IPv683
AS262901Vcnet Provedora de Internet Ltda.UnclassifiedIPv4 IPv669
AS262317ROS TelecomResidentialIPv4 IPv653
AS529651TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDAUnclassifiedIPv4 IPv645
AS263075TV Cabo de Santo Anastacio LtdaUnclassifiedIPv4 IPv639
AS271732K SILVA OLIVEIRAUnclassifiedIPv4 IPv632

Provenance

Where this comes from

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