Chainstack incident

Degraded performance affecting services in London cluster

Minor Resolved

Chainstack experienced a minor incident on September 2, 2026 affecting BNB Smart Chain Trader Nodes (BNB Smart Chain Mainnet Full (Chainstack Cloud, London)) and Ethereum Trader Nodes (Ethereum Mainnet Archive (Chainstack Cloud, London)) and 1 more component, lasting 2h 59m. The incident has been resolved; the full update timeline is below.

Started
Sep 02, 2026, 01:17 AM UTC
Resolved
Sep 02, 2026, 04:16 AM UTC
Duration
2h 59m
Detected by Pingoru
Sep 02, 2026, 01:17 AM UTC

Affected components

BNB Smart Chain Trader Nodes (BNB Smart Chain Mainnet Full (Chainstack Cloud, London))Ethereum Trader Nodes (Ethereum Mainnet Archive (Chainstack Cloud, London))Ethereum Trader Nodes (Ethereum Mainnet Full (Chainstack Cloud, London))Gnosis Trader Nodes (Gnosis Mainnet Full (Chainstack Cloud, London))Gnosis Trader Nodes (Gnosis Mainnet Archive (Chainstack Cloud, London))Polygon Trader Nodes (Polygon Mainnet Full (Chainstack Cloud, London))Polygon Global Nodes (Polygon Amoy Testnet)Polygon Trader Nodes (Polygon Mainnet Archive (Chainstack Cloud, London))

Update timeline

  1. investigating Sep 02, 2026, 01:17 AM UTC

    We are investigating degraded performance affecting select services in London. Requests may experience timeouts.

  2. monitoring Sep 02, 2026, 01:21 AM UTC

    The affected services have recovered and are operating normally. We are monitoring the situation.

  3. resolved Sep 02, 2026, 01:41 AM UTC

    This incident has been resolved.

  4. investigating Sep 02, 2026, 01:56 AM UTC

    We are investigating renewed timeouts affecting Ethereum Mainnet in London.

  5. monitoring Sep 02, 2026, 02:42 AM UTC

    We are monitoring the affected services.

  6. resolved Sep 02, 2026, 04:16 AM UTC

    This incident has been resolved.