Chainstack incident
BSC Mainnet lagging across multiple clusters
Minor Resolved
Chainstack experienced a minor incident on August 5, 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 1h 17m. 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 Archive (Chainstack Cloud, Ashburn))BNB Smart Chain Trader Nodes (BNB Smart Chain Mainnet Full (Chainstack Cloud, Singapore))BNB Smart Chain Trader Nodes (BNB Smart Chain Mainnet Full (Chainstack Cloud, Ashburn))BNB Smart Chain Trader Nodes (BNB Smart Chain Mainnet Full (Chainstack Cloud, London))
Update timeline
- investigating Aug 05, 2026, 04:24 AM UTC
BSC Mainnet upstream nodes are lagging across multiple clusters. We are currently investigating this incident.
- monitoring Aug 05, 2026, 05:26 AM UTC
We implemented a fix and are currently monitoring the result.
- resolved Aug 05, 2026, 05:41 AM UTC
This incident has been resolved.