Identified - Our engineers are closely monitoring updates from the foundation. Please find the next update by 06:00 UTC.
Feb 13, 2026 - 06:19 UTC
Investigating - We are currently experiencing a network-wide stall on Blast Sepolia network at block 33,103,445 Customers will be unable to query new blocks or submit transactions until the network resumes block production. This is an upstream issue affecting the entire Blast Sepolia network.
Feb 12, 2026 - 23:58 UTC
Identified - Our engineers are closely monitoring updates from the foundation. Please find the next update by 06:00 UTC.
Feb 13, 2026 - 08:54 UTC
Investigating - Weβre experiencing elevated error rates on Vana Mainnet Beacon requests and degraded Archive RPC availability.
Investigation indicates a network consensus anomaly (βbad blockβ) causing archive nodes to halt at a specific block height.
We are actively working with the Vana Foundation on resolution. We will provide updates as new information becomes available from the foundation, or sooner if there is a significant change in status.
Feb 09, 2026 - 17:21 UTC
In effort to ensure quick and reliable performance, weβre initiating a client migration on Binance Smart Chain from the Erigon client to the Reth client. This is expected to completed by February 27.
BSC Testnet has already been migrated, allowing your team to test and observe for any potential issues. While such issues are unlikely, there are a few minor differences to note.
Minor: - `eth_getBlockByNumber`: size field is 1 byte smaller in Reth (may affect some archive assumptions) - Minor formatting differences:`debug_traceBlock` / `trace_block`: error message capitalization (βOut of gasβ vs βout of gasβ) - eth_feeHistory: returns 0 instead of 0.0
Important: - This migration deprecates all erigon_* methods on BNB Smart Chain, as they are not supported by Reth. Posted on
Feb 09, 2026 - 15:46 UTC
The Solana Foundation has requested an upgrade for all Solana Mainnet Agave and Jito clients to v3.1.8.
This release improves reliability and performance when working with ledger-based workflows. Snapshot generation is now enabled when loading from the ledger tool, ensuring smoother state initialization. Additionally, the preallocation limit for Entryβs VersionedTransaction has been increased to better handle higher transaction volumes.
No downtime is expected, but customers may experience brief connection interruptions and a small number of HTTP 503 responses as services restart and resynchronize with the cluster.
Completed -
The scheduled maintenance has been completed.
Feb 13, 01:45 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 12, 23:45 UTC
Scheduled -
Updating Blast MAINNET to v1.8.0. It is scheduled to activate on Friday, Feb 13 2026 @ 10am PST / 1771005600. This release is a fast follow that fixes a missing default value in the recent v1.7.0 release.
Feb 12, 23:40 UTC
Resolved -
This incident has been resolved.
Feb 12, 22:49 UTC
Investigating -
Our Hemi Mainnet nodes have stalled at block 3,755,492 - The QuickNode team is applying fixes and will update with more information once it is available.
Feb 12, 21:58 UTC
Resolved -
This incident has been resolved.
Feb 12, 21:41 UTC
Investigating -
We are currently experiencing a network-wide stall on Flow testnet at block 94,601,480 Customers will be unable to query new blocks or submit transactions until the network resumes block production. This is an upstream issue affecting the entire Flow testnet.
Feb 12, 02:58 UTC
Resolved -
This incident has been resolved.
Feb 12, 16:24 UTC
Identified -
Our Ault Testnet nodes have stalled at block 5,249,094 - The QuickNode team is applying fixes and will update with more information once it is available.
Feb 12, 15:43 UTC
The ton-liteserver v2026.02 upgrade is mandatory. This release includes changes to broadcast handling and compression mechanisms. Nodes that are not upgraded will gradually lose synchronization with the network as other validators update.
The ton-http-api and ton-indexer components are updated for compatibility with the new node version.
The upgrade will be performed as a rolling update, sequentially across nodes.
No downtime is expected, but customers may experience brief connection interruptions and a small number of HTTP 503 responses as services restart and resynchronize with the network.
Feb 12, 11:25 UTC
Resolved -
This incident has been resolved.
Feb 12, 03:17 UTC
Update -
We are continuing to investigate this issue.
Feb 12, 00:04 UTC
Investigating -
We are currently experiencing a network-wide stall on B3 Sepolia at block 56,679,129. Customers will be unable to query new blocks or submit transactions until the network resumes block production. This is an upstream issue affecting the entire B3 Sepolia testnet.
Feb 12, 00:03 UTC
Completed -
The scheduled maintenance has been completed.
Feb 11, 20:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 11, 18:00 UTC
Scheduled -
This release defines the upcoming Lisovo hardfork, includes performance improvements, and upstream updates from go-ethereum. The Amoy Testnet Lisovo Hardfork will happen on block 33,634,700, at around ~2PM UTC, February 12th, 2026. Updating bor (v2.6.0-beta) and Erigon (v3.4.0-beta)
Feb 11, 17:58 UTC
Resolved -
This incident has been resolved.
Feb 11, 17:45 UTC
Monitoring -
Maintenance has been completed, we are monitoring for performance.
Feb 11, 17:30 UTC
Investigating -
We are performing urgent middleware maintenance on our Solana infrastructure. You may see heightened response times on some methods during this maintenance, which will resolve when the work is finished.
Users may want to raise timeouts on RPC requests during this time.
Feb 11, 17:15 UTC
Resolved -
The Starknet Sepolia network has resumed block production. Blocks are now progressing normally and customers should be able to query new blocks and submit transactions. We will continue to monitor for stability.
Feb 11, 14:33 UTC
Investigating -
We are currently experiencing a network-wide stall on Starknet Sepolia at block 6418614. Customers will be unable to query new blocks or submit transactions until the network resumes block production. This is an upstream issue affecting the entire Starknet Sepolia testnet.
Feb 11, 14:30 UTC
Completed -
The scheduled maintenance has been completed.
Feb 10, 11:00 UTC
Update -
To stabilize the platform during maintenance, we have temporarily applied rate limits to a small number of resource intensive methods on archive nodes. This may result in intermittent tooBusy responses for affected requests.
We are actively monitoring and will remove these limits once system performance normalizes.
Feb 9, 18:06 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 9, 11:00 UTC
Scheduled -
We will upgrade our XRPL Mainnet and Testnet nodes to rippled v3.1.0 on February 9, 2026, at 11:00 UTC. This release includes protocol updates, performance improvements, and stability fixes relevant to XRPL node operators.
No downtime is expected, but customers may experience brief connection interruptions and a small number of HTTP 503 responses as services restart and resynchronize with the network.
Resolved -
This incident has been resolved.
Feb 9, 22:36 UTC
Identified -
The issue has been identified and a fix is being implemented.
Feb 9, 22:07 UTC
Investigating -
We are investigating intermittent 503 errors affecting Solana Devnet. Some customers may experience temporary request failures or degraded performance.
Our team is actively working to mitigate the issue and restore full service stability.
We will provide an update as more information becomes available.
Feb 9, 22:00 UTC
Resolved -
This incident has been resolved.
Feb 5, 15:00 UTC
Monitoring -
Stellar Foundation identified the root cause and is working on a permanent fix. We have applied the workaround they provided and our nodes are now operational. We will continue monitoring to ensure stability until the permanent fix is released.
Feb 5, 14:49 UTC
Investigating -
We are investigating problems with Stellar Testnet endpoints. Currently experiencing 503 errors following upstream Stellar Testnet horizon disruption: https://status.stellar.org/incidents/60h5qgd5vz31 Stellar Mainnet endpoints continue to operate without disruption.
Feb 5, 13:09 UTC
Completed -
The scheduled maintenance has been completed.
Feb 5, 14:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 5, 12:00 UTC
Scheduled -
Scheduled maintenance will be performed during the maintenance window.
**Client Updates:** β’ java-tron: Upgrading to v4.8.1
**Upgrade Details:** β’ Scheduled for 12:00 UTC on February 5th
**Release Notes Summary:**
## Scheduled Maintenance - Mandatory Upgrade
**Breaking Changes:** - **TIP-6780**: `SELFDESTRUCT` opcode behavior modified within the same transaction - smart contracts using self-destruct may behave differently
Resolved -
This incident has been resolved.
Feb 5, 01:00 UTC
Investigating -
We are currently investigating degraded performance impacting Polygon Amoy nodes in the IAD region. Users may experience 503s and elevated latency during this time. Our engineers are looking into root cause and we will provide a status update as soon as possible.
Feb 4, 21:20 UTC
Resolved -
This incident has been resolved.
Feb 4, 20:39 UTC
Identified -
Users may be served null responses, timeouts, and other errors when using the Quicknode Token and NFT APIs on Ethereum Mainnet. Our engineering team has identified the issue and a solution is actively being worked on.
Feb 4, 19:50 UTC
Completed -
The scheduled maintenance has been completed.
Feb 4, 14:03 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 4, 12:00 UTC
Scheduled -
We will perform an urgent hotfix upgrade of our Aptos Mainnet nodes to aptos-node v1.40.3 on February 4, 2026, at 12:00 UTC. This release contains critical fixes required to maintain network stability and correct Mainnet operation.
No downtime is expected, but customers may experience brief connection interruptions and a small number of HTTP 503 responses as services restart and resynchronize with the network.
Completed -
The scheduled maintenance has been completed.
Feb 4, 12:32 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 4, 11:00 UTC
Scheduled -
We will perform an urgent hotfix upgrade of our Aptos Testnet nodes to aptos-node v1.40.2-rc on February 4, 2026, at 11:00 UTC. This release addresses critical stability issues identified in the previous Testnet build and is required for continued correct Testnet operation.
No downtime is expected, but customers may experience brief connection interruptions and a small number of HTTP 503 responses as services restart and resynchronize with the network.
Completed -
The scheduled maintenance has been completed.
Feb 4, 09:19 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 3, 11:00 UTC
Scheduled -
We will perform an urgent security upgrade of the Geth client to v1.6.6 across BSC Mainnet and Chapel on February 3, 2026, at 11:00 UTC. This release contains important security fixes and is required to maintain network safety and client stability.
No downtime is expected, but customers may experience brief connection interruptions and a small number of HTTP 503 responses as services restart and resynchronize with the network.
Completed -
The scheduled maintenance has been completed.
Feb 2, 21:45 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 2, 19:45 UTC
Scheduled -
Horace (Story v1.5.2) is a mandatory hardfork upgrade of the consensus client for Story Mainnet (upgrade height 13780500) and Aeneid Testnet (upgrade height 14017000).
Feb 2, 19:30 UTC
Resolved -
All affected nodes are now operational and performing as expected. Thank you for your patience during this incident.
Feb 1, 15:06 UTC
Monitoring -
More nodes are back at the tip. The QuickNode team is monitoring and recovering the node to full capacity. We will update you with more information as soon as it becomes available.
We will provide the next update by 14:00 UTC or sooner.
Feb 1, 07:00 UTC
Identified -
The QuickNode teams are working with the foundation team and have recovered some of the nodes. Some nodes are back at the tip. We will update you with more information as soon as it becomes available.
We will provide the next update by 8:00 UTC or sooner.
Feb 1, 04:48 UTC
Investigating -
The zkEVM mainnet nodes appear to have stalled at block 29,263,644. The QuickNode teams are investigating and will update you with more information as soon as it becomes available.
We will provide the next update by 8:00 UTC or sooner.
Feb 1, 04:10 UTC
Resolved -
This incident has been resolved.
Feb 1, 02:39 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jan 31, 23:50 UTC
Investigating -
ZKsync Mainnet is currently experiencing network performance degradation. You may experience requests resulting in 503 errors and/or elevated latency. We're awaiting new information from the foundation and will provide an update as soon as possible.
Jan 31, 22:57 UTC
Resolved -
Block 151,960,880 will remain the earliest available block until our standard pruning policy reaches its threshold at a distance of 1,832,727 blocks. Once standard pruning resumes, we will continue to retain the most recent 1,832,727 blocks as detailed in our "Node Type" documentation: https://www.quicknode.com/docs/platform/supported-chains-node-types
Jan 31, 00:56 UTC
Investigating -
Our engineers are actively investigating and working on extending the data availability window. Weβll provide the next update on or before 31 Jan at 2:00 PM UTC.
Jan 29, 07:28 UTC