Chainstack incident
Degraded Performance on BSC Mainnet in London
Minor Resolved
Chainstack experienced a minor incident on July 19, 2026 affecting BNB Smart Chain Global Nodes (BNB Smart Chain Mainnet) and BNB Smart Chain Trader Nodes (BNB Smart Chain Mainnet Archive (Chainstack Cloud, London)) and 1 more component, lasting 3h 49m. The incident has been resolved; the full update timeline is below.
Affected components
BNB Smart Chain Global Nodes (BNB Smart Chain Mainnet)BNB Smart Chain Trader Nodes (BNB Smart Chain Mainnet Archive (Chainstack Cloud, London))BNB Smart Chain Trader Nodes (BNB Smart Chain Mainnet Full (Chainstack Cloud, London))
Update timeline
- identified Jul 19, 2026, 01:21 AM UTC
We have identified the issue causing the degraded performance on our BSC Mainnet nodes in London region. Elevated response times are expected for `eth_getLogs` calls. The root cause has been traced to a resource exhaustion. We are currently working on mitigation strategies.
- resolved Jul 19, 2026, 05:11 AM UTC
We implemented a fix by adding more capacity, and things have stabilized. The incident has been resolved.