Investigating - We are currently investigating an upstream issue with Abstract testnet. The network is stalled at block 16,773,987. The Abstract Foundation has been notified and is investigating. All Abstract testnet 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 2PM UTC or sooner as information becomes available.
Mar 09, 2026 - 12:26 UTC
- **Missing RPC fields fixed** — A bug causing certain RPC response fields to be absent has been resolved - **WebSocket subscriptions fixed** — A race condition affecting WebSocket subscription delivery has been corrected
Scheduled maintenance will be performed on the Cosmos Mainnet during the scheduled maintenance window.
**Client Updates:** - Gaiad: Upgrading to v27.0.0
**Upgrade Details:** - Governance upgrade via proposal: https://www.mintscan.io/cosmos/proposals/1025 - Upgrade Height: 30,151,300 (Roughly at Mar 11th 2026, 14:10:00 UTC) - There will be a short period of downtime (a few minutes) during the upgrade.
**Release Notes Summary:** - **Multi-send transaction behavior change:** Transactions using multi-send messages now incur a gas surcharge and are subject to a limit on the number of recipients.
Resolved -
The Injective mainnet upgrade to v1.18.2 has been completed successfully. INJ endpoints are fully operational.
Mar 9, 16:48 UTC
Investigating -
INJ endpoints may experience brief disruptions due to an upcoming mandatory Injective mainnet upgrade to v1.18.2. We are actively tracking the upgrade block height and will provide timing details as soon as they are confirmed.
Mar 9, 14:04 UTC
Completed -
The scheduled maintenance has been completed.
Mar 9, 04:30 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 9, 03:30 UTC
Scheduled -
Scheduled maintenance will be performed on Monad Testnet infrastructure during the scheduled maintenance window.
**Client Updates:** - Monad: Upgrading to v0.13.0
---
**Upgrade Highlights:**
RPC changes in the RPC after the v0.13.0 upgrade:
- `latest` block tag now maps to **Proposed** blocks, instead of Voted - `newHeads` and `logs` WebSocket subscriptions now stream **Voted** blocks, instead of Finalized - `eth_sendRawTransactionSync` now returns the receipt from **Proposed** blocks, instead of Voted
These changes improve the RPC polling and streaming rate by one block (~400 ms) and enhance developer and end-user experience.
Completed -
The scheduled maintenance has been completed.
Mar 9, 02:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 9, 00:00 UTC
Scheduled -
Scheduled maintenance will be performed during the maintenance window to upgrade the Tempo client and apply the T1C network upgrade.
**Client Updates:** - tempo: Upgrading to v1.4.0
---
**Release Notes Summary:**
**T1C Network Upgrade Activation** - **Moderato (testnet):** Monday, March 9 at 16:00 CET - **Mainnet:** Thursday, March 12 at 16:00 CET
**Breaking Changes After T1C Activation**
- **Keychain signature format change:** Only V2 keychain signatures (`type 0x04`) are accepted post-T1C. Transactions using legacy V1 signatures will be rejected. Pre-T1C keys remain accessible — only the signature type and hash calculation have changed. - **Key authorization `chain_id` wildcard removed:** `chain_id=0` is no longer valid. Key authorizations must specify the exact Tempo chain ID. - **Precompile set updated:** Precompiles transition from Prague to Osaka at T1C activation.
Completed -
The scheduled maintenance has been completed.
Mar 8, 19:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 8, 13:00 UTC
Scheduled -
A scheduled maintenance window has been planned for our Frankfurt (FRA) region on March 8, 2026 between 13:00 and 19:00 UTC. During this time, some users may experience brief intermittent packet loss or increased latency on the affected networks listed above. We will be actively monitoring throughout and will take all necessary measures to minimize impact. All other regions remain fully operational.
Mar 5, 14:28 UTC
Resolved -
After monitoring, latency on Sei Pacific has returned to normal levels. The issue has been fully resolved.
Customers should no longer experience slower response times on RPC requests. If you continue to experience any issues, please contact our support team.
Mar 7, 14:47 UTC
Monitoring -
A fix has been applied and our engineering team is actively monitoring to ensure the issue is fully resolved. Customers may still experience some residual slower response times on RPC requests.
We will provide the next update by 2PM UTC or sooner.
Mar 7, 13:06 UTC
Investigating -
We are currently experiencing elevated latency on Sei Pacific. Customers may experience slower response times on RPC requests. Endpoints remain operational but performance is degraded.
Our teams are actively investigating and working to restore normal performance levels. We will provide the next update by 2PM UTC or sooner.
Mar 7, 12:31 UTC
Resolved -
This incident has been resolved.
Mar 6, 22:19 UTC
Monitoring -
The Hedera Testnet network has resumed. Our team is monitoring for stability.
Mar 6, 21:51 UTC
Update -
We are continuing to investigate this issue.
Mar 6, 21:51 UTC
Investigating -
The Hedera Testnet network appears to have stalled at block 32392072 - The Quicknode team is investigating and will update with more information once it is available.
Mar 6, 21:42 UTC
Monitoring -
Foundation has confirmed block production has resumed without flashblocks and actively working on recovery.
Mar 6, 00:00 UTC
Investigating -
Unichain Sepolia has stalled network-wide at block 45,897,373. We are currently investigating and will work closely with the foundation on resolution.
Completed -
The scheduled maintenance has been completed.
Mar 5, 13:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 5, 12:00 UTC
Scheduled -
Scheduled maintenance will be performed on Fuel Mainnet during the scheduled maintenance window. These are simple gas configuration changes as directed by the Fuel chain team without changes to RPC.
Mar 4, 18:05 UTC
Resolved -
This incident has been resolved.
Mar 4, 23:55 UTC
Monitoring -
Network movement has resumed and our nodes are serving tip data. We will monitor performance closely and mark the incident as resolved as soon as possible.
Mar 4, 23:29 UTC
Investigating -
Optimism Mainnet has stalled network-wide at block 148,533,323. We are currently investigating and will work closely with the foundation on resolution.
Completed -
The scheduled maintenance has been completed.
Mar 4, 18:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 4, 14:00 UTC
Scheduled -
We will be upgrading our Ethereum consensus (Lighthouse) nodes to the latest stable version (v8.1.1) to incorporate a mandatory security fix along with networking and validator client bug fixes.
Notable changes: --- - Security: Critical security vulnerability fix affecting all prior Lighthouse versions — further details to be disclosed by the Lighthouse team in the coming days
- Bug Fixes: Validator Client — Fixed a regression from `v8.1.0` where the VC head monitoring stream would continuously time out, causing repeated Head service failed warnings. Networking — Fixed duplicate data columns in `DataColumnsByRange` responses caused by skip slots, which was causing peers to downscore nodes with `DuplicatedData` errors. Networking — Snappy decoding errors are now correctly classified as `InvalidData` instead of `IoError`, fixing improper error handling in RPC message decoding. Memory — Fixed a slow memory leak on long-running nodes caused by missing prune calls for the `observed_column_sidecars` cache during finalization Sync — Fixed head chain processing to correctly sort by peer count in descending order, improving sync peer selection
- Networking Improvements: Peers sending invalid RPC requests that result in decoding errors are now penalized and disconnected ---
Resolved -
This incident has been resolved.
Mar 4, 04:00 UTC
Investigating -
The Fuel Sepolia network appears to have stalled at block 56,428,550 - The Quicknode team is investigating and will update with more information once it is available.
Mar 3, 18:18 UTC
Completed -
The scheduled maintenance has been completed.
Mar 2, 18:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 2, 15:45 UTC
Scheduled -
We are upgrading our Injective Testnet nodes in preparation for a chain-level upgrade that with take place at block height 115505000.
Mar 2, 15:20 UTC
Resolved -
The issue affecting the XRPL EVM network, which caused the chain to stall at block 4,748,999, has been fully resolved. The network is now operating normally and blocks are progressing as expected.
Our team has confirmed stability and will continue to monitor the network closely.
We appreciate your patience while we worked to resolve this incident.
Mar 2, 17:01 UTC
Investigating -
We are currently investigating an incident affecting the XRPL EVM network. Our team is actively working on identifying the root cause and implementing a resolution. Further updates will be shared as soon as more information becomes available.
Mar 2, 13:33 UTC
Resolved -
This incident has been resolved.
Mar 2, 16:22 UTC
Update -
We are continuing to investigate this issue.
Mar 2, 16:22 UTC
Investigating -
Injective Testnet nodes are currently undergoing a network upgrade to v1.18.1 at block height 115,505,000. This upgrade was recently released and is now being applied. During this process, testnet services may be temporarily unavailable. Our team is actively completing the upgrade and will provide updates as progress continues.
Mar 2, 16:19 UTC
Completed -
The scheduled maintenance has been completed.
Feb 27, 00:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 16, 00:00 UTC
Scheduled -
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.
Feb 9, 15:46 UTC
Resolved -
This incident has been resolved.
Feb 26, 20:17 UTC
Monitoring -
Latencies have returned to average levels and the timeout issues appear to have subsided. Our team continues to monitor the situation closely to ensure stability is maintained. We will provide a final update once we are fully confident the network is operating normally. Next update will be provided by 20:00 UTC at the latest.
Feb 26, 17:15 UTC
Investigating -
We are currently investigating performance degradation affecting Ethereum Mainnet. Our team has identified signs of infrastructure impact and is actively working with the Ethereum Foundation to determine the root cause. We will provide updates as the investigation progresses.
Feb 26, 14:20 UTC
Resolved -
This incident has been resolved.
Feb 26, 19:27 UTC
Monitoring -
After investigation, the block sync issue at block 436,172,925 has been isolated to specific nodes. Service should now be operational for all customers. We are continuing to monitor for stability.
Feb 26, 13:54 UTC
Investigating -
We are currently experiencing an issue with our Arbitrum mainnet infrastructure stuck at block 436,172,925. Customers may be unable to query the latest blocks or experience delays in transaction confirmations. Our engineering team is actively working to resolve the sync issue and will provide the next update by 3PM UTC or sooner.
Feb 26, 13:46 UTC
Completed -
The scheduled maintenance has been completed.
Feb 26, 15:45 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 26, 11:45 UTC
Scheduled -
We will be upgrading Ethereum Sepolia, Hoodi and Mainnet erigon nodes to the latest stable version (v3.3.8) to incorporate critical bug fixes and stability improvements.
Resolved -
After performing an upgrade, our XRP Ledger EVM infrastructure has successfully synced past block 4,688,680. Service is now operational and customers should be able to query the latest blocks and submit transactions normally. We will continue to monitor for stability.
Feb 26, 14:26 UTC
Investigating -
We are currently experiencing an issue with our XRP Ledger EVM infrastructure stuck at block 4,688,680. Customers may be unable to query the latest blocks or experience delays in transaction confirmations. Our engineering team is actively working to resolve the sync issue and will provide the next update by 3PM UTC or sooner.
Feb 26, 13:51 UTC
Completed -
The scheduled maintenance has been completed.
Feb 26, 10:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 26, 05:00 UTC
Scheduled -
We will be upgrading Ethereum Sepolia, Hoodi and Mainnet erigon nodes to the latest stable version (v3.3.8) to incorporate critical bug fixes and stability improvements.
Resolved -
Nomina (Omni Core) has been officially decommissioned and is no longer available via QuickNode RPC endpoints. All related infrastructure has been shut down.
Feb 25, 19:59 UTC
Identified -
The Nomina Blockchain has halted at block 31300048 due to the announcement from the Nomina team to deprecate the chain and consolidate services on Ethereum. Check out the official Nomina announcement for further information:
Completed -
The scheduled maintenance has been completed.
Feb 25, 18:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 25, 14:00 UTC
Scheduled -
In preparation for the Lisoo/LisovoPro hardfork at block 83756500, we will be upgrading our Polygon nodes.
There are no explicit API method format/signature changes called out for this upgrade.
However, there are a few API-relevant things to be aware of: Bug fixes affecting RPC behavior:
- `eth_simulateV1` - had a crash bug that is now fixed (two separate fixes: one for the method handler, one in consensus/misc/eip4844). If you were working around crashes, behavior may normalize.
- State-sync transactions in tracers - eth_tracers now correctly includes state-sync txs in traces post-Madhugiri HF. If you rely on trace results, output may change for those transactions.
Consensus/fee changes that could affect responses:
- Dynamic EIP-1559 parameters — base fee calculation parameters are now dynamic. This could affect `eth_gasPrice`, `eth_feeHistory`, and related fee estimation calls.
- P256 precompile gas cost update — calls to the P256 precompile (RIP-7212) will now use updated gas costs, affecting gas estimation for transactions using it.
- PIP-82 / BurntContract changes — changes to how fees are burned; shouldn't change API formats but could affect balance/accounting queries.
New opcode:
- CLZ opcode added — relevant if you're doing gas estimation for contracts that use it. The short answer: no breaking changes to API method names or response schemas are documented. The main things to watch are fee estimation behavior (dynamic EIP-1559 params) and tracer output for state-sync transactions. The hardfork hits Mainnet at block 83756500, around 2 PM UTC on March 4, 2026.
Resolved -
This incident has been resolved.
Feb 25, 00:14 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Feb 24, 22:08 UTC
Investigating -
We are currently investigating performance degradation affecting Solana endpoints in the US region. Customers may experience increased latency and slower RPC responses. Our engineering team is actively working to identify the root cause and restore normal performance.
Next update: : as we continue our investigation and have more information to share.
Feb 24, 21:06 UTC
Resolved -
The QuickNode team has completed the investigation and the performance has now returned to normal. We will continue to monitor for any performance issues. Please let us know if you experience any further issues.
Feb 24, 17:06 UTC
Investigating -
The QuickNode team is investigating the degraded performance of Litecoin Testnet You may see increased response times or timeouts while we work to resolve this incident. We will update this page as we acquire new information.
Feb 24, 15:48 UTC
Resolved -
Blockchain has caught up to tip and is functioning correctly. Our team will continue to monitor and optimize.
Feb 24, 13:16 UTC
Identified -
Our team has applied the change recommended by the Abstract Foundation to restore nodes' syncing and is continuing to monitor catch-up progress.
The next update will be 14:00 UTC or sooner.
Feb 24, 08:32 UTC
Investigating -
The Abstract Mainnet appears to have stalled at block 42,049,044. The QuickNode team is working with the foundation team on it and will update with more information once it is available.
Feb 24, 05:43 UTC
Resolved -
This incident has been resolved.
Feb 24, 05:34 UTC
Update -
We are continuing to investigate this issue.
Feb 24, 01:19 UTC
Investigating -
The Flow EVM Mainnet appears to have stalled at block 57,211,887 and Flow Mainnet at 143,217,050 - The QuickNode team is investigating and will update with more information once it is available.
Feb 24, 01:17 UTC
Resolved -
This incident has been resolved.
Feb 24, 03:32 UTC
Update -
Our engineers are closely listening to updates from the foundation. Please find the next update on or before 19th Feb, 18:00 UTC.
Feb 15, 08:27 UTC
Identified -
Our engineers are closely monitoring updates from the foundation. Please find the next update by 06:00 UTC.
Feb 13, 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 9, 17:21 UTC
Resolved -
This incident has been resolved.
Feb 24, 00:20 UTC
Investigating -
The XRPLEVM Testnet is currently experiencing a chain halt following a network upgrade applied by the XRPLEVM Foundation earlier today. This is a network-level issue and the Foundation is actively working on a resolution. We are monitoring closely and will update this page as soon as more information is available.
Feb 23, 17:17 UTC
Resolved -
This incident has been resolved.
Feb 24, 00:00 UTC
Identified -
The issue has been identified and a fix is being implemented.
Feb 23, 23:22 UTC
Investigating -
Plasma testnet appears to have stalled at block 16,074,334 - The QuickNode team is investigating and will update with more information once it is available.
Feb 23, 23:04 UTC
Resolved -
This incident has been resolved. Base Sepolia nodes are fully operational and block production has returned to normal. We appreciate your patience throughout this process and will continue to monitor the network to ensure stability is maintained.
Feb 23, 17:00 UTC
Monitoring -
Block progression has resumed on Base Sepolia. We are keeping a close eye on the network and remain in touch with the Foundation as we work toward full resolution. Further updates to follow.
Feb 23, 12:40 UTC
Investigating -
We are currently investigating an issue affecting Base Sepolia where block height has stalled at 38,039,244. We are in active communication with the Foundation and are working toward restoring normal block progression. Further updates will be provided as the situation develops.
Feb 23, 11:53 UTC