Chainstack incident
Los Angeles (LAX) cluster degraded performance
Minor Resolved
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))Polygon zkEVM Trader Nodes (Polygon zkEVM Mainnet Full (Chainstack Cloud, Los Angeles) )ZKsync Era Trader Nodes (ZKsync Era Mainnet Archive (Chainstack Cloud, Los Angeles) )
Update timeline
- investigating Apr 29, 2026, 02:46 AM UTC
We are currently investigating this incident.
- monitoring Apr 29, 2026, 02:47 AM UTC
We implemented a fix and are currently monitoring the result.
- resolved Apr 29, 2026, 02:57 AM UTC
This incident has been resolved.
Looking to track Chainstack downtime and outages?
Pingoru polls Chainstack's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Chainstack reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Chainstack alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
Start monitoring Chainstack for free
5 free monitors · No credit card required