Chainstack incident

Arbitrum Mainnet eth_getLogs degradation in Frankfurt

Minor Resolved

Chainstack experienced a minor incident on August 16, 2026 affecting Arbitrum Global Nodes (Arbitrum One Mainnet) and Arbitrum Trader Nodes (Arbitrum One Mainnet Archive (Chainstack Cloud, Frankfurt)) and 1 more component, lasting 33m. The incident has been resolved; the full update timeline is below.

Started
Aug 16, 2026, 03:58 AM UTC
Resolved
Aug 16, 2026, 04:31 AM UTC
Duration
33m
Detected by Pingoru
Aug 16, 2026, 03:58 AM UTC

Affected components

Arbitrum Global Nodes (Arbitrum One Mainnet)Arbitrum Trader Nodes (Arbitrum One Mainnet Archive (Chainstack Cloud, Frankfurt))Arbitrum Trader Nodes (Arbitrum One Mainnet Full (Chainstack Cloud, Frankfurt))

Update timeline

  1. investigating Aug 16, 2026, 03:58 AM UTC

    We are investigating an issue affecting `eth_getLogs` request response times in our Frankfurt cluster. Our team is working on a resolution.

  2. identified Aug 16, 2026, 04:18 AM UTC

    We are continuing to work on a fix for this incident.

  3. resolved Aug 16, 2026, 04:31 AM UTC

    This incident has been resolved.