Chainstack incident

Los Angeles (LAX) cluster degraded performance

Minor Resolved

Chainstack experienced a minor incident on April 29, 2026 affecting Arbitrum Trader Nodes (Arbitrum One Mainnet Archive (Chainstack Cloud, Los Angeles)) and Arbitrum Trader Nodes (Arbitrum One Mainnet Full (Chainstack Cloud, Los Angeles)) and 1 more component, lasting 10m. The incident has been resolved; the full update timeline is below.

Started
Apr 29, 2026, 02:46 AM UTC
Resolved
Apr 29, 2026, 02:57 AM UTC
Duration
10m
Detected by Pingoru
Apr 29, 2026, 02:46 AM UTC

Affected components

Arbitrum Trader Nodes (Arbitrum One Mainnet Archive (Chainstack Cloud, Los Angeles))Arbitrum Trader Nodes (Arbitrum One Mainnet Full (Chainstack Cloud, Los Angeles))Avalanche Trader Nodes (Avalanche Mainnet Full (Chainstack Cloud, Los Angeles))Base Trader Nodes (Base Mainnet Full (Chainstack Cloud, Los Angeles))Base Trader Nodes (Base Mainnet Archive (Chainstack Cloud, Los Angeles))Bitcoin Trader Nodes (Bitcoin Mainnet Full (Chainstack Cloud, Los Angeles))Fantom Trader Nodes (Fantom Mainnet Archive (Chainstack Cloud, Los Angeles))Fantom Trader Nodes (Fantom Mainnet Full (Chainstack Cloud, Los Angeles))Optimism Trader Nodes (Optimism Mainnet Archive (Chainstack Cloud, Los Angeles))Optimism Trader Nodes (Optimism Mainnet Full (Chainstack Cloud, Los Angeles))

Update timeline

  1. investigating Apr 29, 2026, 02:46 AM UTC

    We are currently investigating this incident.

  2. monitoring Apr 29, 2026, 02:47 AM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Apr 29, 2026, 02:57 AM UTC

    This incident has been resolved.