# Chainlink CCIP Network Specific Limits
Source: https://docs.chain.link/ccip/evm/service-limits/hyperevm
Last Updated: 2026-11-06

> For the complete documentation index, see [llms.txt](/llms.txt).

This page describes known network-specific limitations that may result from the design of a particular network. End users, application developers, blockchain development teams, token developers and others should read and understand these risks when considering interacting with these networks on CCIP.

## HyperEVM

**Testnet availability**: HyperEVM Testnet is operated by a third party and may be upgraded or modified without prior notice. Because these changes can affect CCIP's compatibility with the network, CCIP on HyperEVM Testnet is provided "as is" and does not carry the same level of service guarantees or warranties as CCIP on other supported networks. Availability, performance, data availability, and message delivery may be interrupted or degraded at any time. Use HyperEVM Testnet for development and testing only.

**Risk**:
[Hyperliquid Data availability](/ccip/v1/service-responsibility#blockchain-development-team-responsibilities): If a HyperEVM RPC is out of sync or offline for 10+ minutes, missing logs from during the downtime are only available through a centralized resource that is hosted and maintained by Hyperliquid. In the event that logs related to specific CCIP messages are irrecoverable, those CCIP messages can become stuck or fail.

**CCIP Mitigation**:
Hyperliquid has provided a workaround to serve logs through a [dedicated resource](https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/hyperevm/raw-hyperevm-block-data) in case their network is inaccessible from RPC providers. CCIP is utilizing Hyperliquid's data source to backfill missing logs. In addition, CCIP Node Operators have implemented additional defense, using an multi-RPC approach, allowing for detection of out-of-sync or offline RPCs and an automatic fallback. If all configured RPCs are unavailable for a period of 10+ minutes AND the Hyperliquid data source does not provide them, logs may not be recoverable.