The issue affecting Sonic mainnet RPC endpoints has been resolved. Our engineering team successfully completed the Sonic client upgrades to v2.1.6 and database resyncing at 00:00 UTC on 27 March.
Our engineering team is actively applying the Sonic client upgrades to v2.1.6 and database resyncing to restore service.
Sonic Mainnet RPC endpoints are currently affected. Customers may experience request failures or timeouts until our nodes complete the upgrade and resync process. The native Sonic explorer remains operational: https://explorer.soniclabs.com/blocks
We are currently experiencing service disruptions on Sonic mainnet RPC endpoints due to validator syncing issues. The Sonic team has clarified this is NOT a network stall. The Sonic network remains fully operational, continues to produce blocks, and transactions are processing as expected.
The Sonic team has identified the issue and provided a fix requiring client upgrades to v2.1.6 and database resyncing. Our engineering team is actively applying this update to restore service.
Sonic mainnet RPC endpoints are currently affected. Customers may experience request failures or timeouts until our nodes complete the upgrade and resync process. The native Sonic explorer remains operational: https://explorer.soniclabs.com/blocks
We are currently experiencing service disruptions on Sonic mainnet due to an upstream network-wide block stall. The network is stalled at block 66,026,794. This is a network-wide issue and is not isolated to Quicknode. The Sonic Foundation has been notified. All Sonic mainnet RPC endpoints are currently affected by the upstream network stall. New blocks are not being produced until the network resumes. We will provide the next update by 11:30am or sooner as information becomes available.
Posted Mar 25, 2026 - 10:29 UTC
This incident affected: Sonic (Mainnet — JSON-RPC API, Mainnet — Websockets API, Mainnet — Streams, Mainnet — Webhooks).