QuickNode Status

Resolved: The 0G Galileo testnet network stall has been resolved, and the chain is progressing normally again. The issue was network wide and not isolated to QuickNode. We will continue monitoring for stability.

Investigating: The 0G Galileo testnet network appears to have stalled at block 25181554 - The stall is network wide and is not isolated to Quicknode. Our team has reached out to the foundation for further information. This page will be updated as we receive further information.

Resolved: This incident has been resolved.

Monitoring: We have implemented a fix, and service is recovering.

We are actively monitoring the situation and will share additional updates as we confirm continued stability

Investigating: On Cosmos, customers may experience degraded performance for both HTTP and WebSocket traffic, including increased error rates (ex, 503 responses), elevated latency, and intermittent request failures.

To resolve this, we are performing an upgrade and working to restore normal service as quickly as possible. We will share the next update as soon as we confirm the cause and mitigation steps, and we’ll continue to provide updates as more information becomes available.

Resolved: This incident has been resolved.

Monitoring: The block height stall on Fluent Testnet has been addressed and all nodes are now synced and producing blocks normally. We are monitoring to ensure stability.

We will provide a final update shortly to confirm full resolution.

Investigating: We are aware of a block height stall affecting Fluent Testnet. Requests may return stale or inconsistent data during this time.

We are coordinating closely with the Fluent chain team to identify and resolve the underlying cause. Our engineering team is actively working to restore normal service.

Recommended action: No action is required on your end. Requests to Fluent Testnet may return outdated block data until the issue is resolved.

We will provide a further update within the next 60 minutes.

Resolved: The issue affecting Ink Sepolia testnet has been resolved. Backend nodes have returned to normal operation and are now passing health checks. All Ink Sepolia testnet RPC endpoints are now fully operational. If you continue to experience any issues, please contact our support team.

Investigating: We are currently experiencing service disruptions on Ink Sepolia testnet due to backend node degradation. Multiple backend nodes are failing health checks and not providing block data within expected timeframes.

Ink Sepolia testnet RPC endpoints are currently affected. Customers may experience request failures, timeouts, or inconsistent block data until our backend nodes are restored. Our engineering team is actively investigating and working to resolve the backend pool issues.

We will provide the next update by 2:30pm or sooner.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

We will follow up with an update by 21:00 UTC.

Identified: Our team has identified the issue with the affected nodes and are currently working on recovery.

We will follow up with an update by 20:30 UTC.

Investigating: We are investigating an issue impacting Gnosis (GNO) Mainnet Archive RPC where some requests are returning elevated HTTP 503 errors and may experience degraded availability.

The team is actively working to identify the cause and restore normal service.

We will follow up with an update by 20:00 UTC.

Resolved: Bitcoin Cash (BCH) mainnet block production has resumed and the network is producing new blocks again. We will continue monitoring for stability.

Investigating: We are currently investigating a block production stall on the Bitcoin Cash (BCH) mainnet. The network appears to have stopped producing new blocks, which is also confirmed by public explorers showing the same block height. We are monitoring the situation closely and will provide updates as they become available.

Resolved: 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.

All Sonic mainnet RPC endpoints are now fully operational. If you continue to experience any issues, please contact our support team. https://portal.usepylon.com/quicknode/forms/submit-a-support-ticket

Identified: 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

For official updates from Sonic: https://x.com/SonicLabs/status/2036763965041021347

Identified: 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

For official updates from Sonic: https://x.com/SonicLabs/status/2036763965041021347

We will provide the next update by 3PM or sooner.

Investigating: 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.

Resolved: This incident has been resolved.

Investigating: BCH Testnet is experiencing slow block production. We are investigating and will update with more information once it is available.