Chainstack incident

Increased latency in LAX region

Major Resolved

Chainstack experienced a major incident on July 2, 2026 affecting Arbitrum Global Nodes (Arbitrum One Mainnet) and Arbitrum Global Nodes (Arbitrum Sepolia) and 1 more component, lasting 7h 15m. The incident has been resolved; the full update timeline is below.

Started
Jul 02, 2026, 08:56 AM UTC
Resolved
Jul 02, 2026, 04:12 PM UTC
Duration
7h 15m
Detected by Pingoru
Jul 02, 2026, 08:56 AM UTC

Affected components

Arbitrum Global Nodes (Arbitrum One Mainnet)Arbitrum Global Nodes (Arbitrum Sepolia)Avalanche Global Nodes (Avalanche Mainnet)Base Global Nodes (Base Mainnet)Bitcoin Global Nodes (Bitcoin Mainnet)Fantom Global Nodes (Fantom Mainnet)Optimism Global Nodes (Optimism Mainnet)Polygon zkEVM Global Nodes (Polygon zkEVM Mainnet)Starknet Global Nodes (Starknet Mainnet)ZKsync Era Global Nodes (ZKsync Era Mainnet)

Update timeline

  1. investigating Jul 02, 2026, 08:56 AM UTC

    Arbitrum Sepolia & Avalanche Mainnet Global nodes may experience increase in latency specifically from Los Angeles (LAX) region due to Cloudflare maintenance:

  2. identified Jul 02, 2026, 10:29 AM UTC

    Impact increased to more protocols & networks in LAX region.

  3. monitoring Jul 02, 2026, 04:12 PM UTC

    We implemented a fix and are currently monitoring the result.

  4. resolved Jul 02, 2026, 04:12 PM UTC

    Post conclusion of maintenance on Cloudflare side, there were no more timeouts and latency jumps observed. The incident is considered resolved