--- service: "QuickNode" status: "maintenance" reports_last_hour: 0 reports_last_12_hours: 0 baseline_reports_per_hour: 1 checked_at: "2026-10-31T19:36:01.958Z" url: "https://instatus.com/now/quicknode.com" official_status_page: "https://status.quicknode.com" website: "https://www.quicknode.com" --- # Is QuickNode down? It's under maintenance. 0 reports in the last hour. ## Official updates - **[Standard] Ethereum TN&MN - Reth v2.9.0** (SCHEDULED, 2026-11-09T00:00:00.000Z): We are upgrading our Ethereum Reth infrastructure from v2.5.2 to v2.9.0. This upgrade combines four releases of improvements. It includes a new EVM implementation (evm2) that makes block execution about 10% faster, faster historical-state and trace queries, and several RPC correctness fixes. No hard fork is involved, and users do not need to take any action. During the maintenance window, brief interruptions to RPC availability may occur. RPC Changes: - eth_getProof — fixed. Proof responses now match the Ethereum execution-apis specification. - eth_call / eth_estimateGas — fixed. When the node works out how much gas a caller can afford, it now reserves blob fees from the account balance. - eth_estimateGas — changed. Estimates are now capped at the node's RPC gas cap. - eth_maxPriorityFeePerGas — changed. The fee oracle now ignores transactions with a tip below 2 wei, so the suggested priority fee no longer drops to 0. This matches Geth. - trace_* (Parity-style) — changed. Output now matches other clients: - Deleted accounts report empty stateDiff storage. - vmTrace ops and subs include only operations that actually executed. - Reverted CREATE calls return {gasUsed, output} without an address. - trace_callMany / trace_filter — changed. trace_callMany without a block parameter and trace_filter without block bounds now default to latest. If you need pending state or a historical range, specify the block or range explicitly. - trace_get — fixed. Results are now selected by trace tree path. Replaying a missing transaction returns null. https://github.com/paradigmxyz/reth/releases/tag/v2.9.0 Intermediate releases (v2.6.0 – v2.8.1): https://github.com/paradigmxyz/reth/releases - **[Standard] Bitcoin MN &TN - Bitcoin Core v32.1** (SCHEDULED, 2026-11-09T00:00:00.000Z): We are upgrading our Bitcoin infrastructure from Bitcoin Core v31.1 to v32.1. This is a new major release (v32.0 was tagged but never formally released, so v32.1 is the first official 32.x version). It contains no consensus changes and carries no fork or chain split risk. It includes performance improvements, a faster fee estimator, and several RPC response changes that may affect applications parsing mempool, fee, or deployment data. Please review the RPC changes below before the maintenance window. During the maintenance window, brief interruptions to RPC availability may occur. RPC Changes: • Mempool RPCs — deprecated fields removed. getrawmempool, getmempoolancestors, getmempooldescendants, and getmempoolentry no longer return the bip125-replaceable field. getmempoolinfo no longer returns the fullrbf field. Full RBF has been the default behavior since v28. • Mempool RPCs — new vsize fields. getrawmempool, getmempoolentry, testmempoolaccept, and submitpackage now return vsize_adjusted (sigop-adjusted virtual size, used for policy) and vsize_bip141 (raw BIP141 virtual size). The existing vsize field is now deprecated; it has always returned the sigop-adjusted value. Use vsize_adjusted to keep current behavior or vsize_bip141 for the true BIP141 size. • getrawtransaction — new field. Now includes vsize_adjusted when the transaction is in the mempool. • estimatesmartfee — new estimator. Fee estimates now combine the existing block-policy estimator with a new mempool-based estimator, returning the lower of the two. Users may see lower fee estimates than before. A new optional options argument accepts fee_rate_estimator (auto, block_policy, or mempool_policy) and verbosity; pass block_policy to keep the previous behavior. Successful auto responses now include an estimator field. • sendrawtransaction, testmempoolaccept, submitpackage — richer errors. The bad-txns-nonstandard-inputs rejection now includes additional debug detail explaining why the inputs are non-standard. The error code itself is unchanged. https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-32.1.md - **[Standard] Morph - Hoodi Mainnet - Upgrade to v0.6.4 & morph-v2.2.7 (Celadon Fork)** (SCHEDULED, 2026-11-02T00:00:00.000Z): We are upgrading our Morph Mainnet infrastructure to node v0.6.4 and morph-v2.2.7 ahead of the mandatory Celadon network upgrade, which activates on Hoodi Testnet at 2026-10-28 06:00 UTC. Celadon introduces MorphTx v2, which lets users pay gas with an alternative token and delegate their EOA to contract code (EIP-7702) in a single transaction. It also corrects the rounding of alt-token fee refunds, so users are charged the precisely rounded net fee. All existing transaction types, including MorphTx v0/v1 and standard 0x04 SetCode transactions, remain fully supported. During the maintenance window, brief interruptions to RPC availability may occur. RPC changes: - eth_sendRawTransaction — MorphTx v2 (type 0x7F, version 0x02) is accepted once Celadon activates. Before activation, v2 transactions are rejected. - Transaction-building requests (e.g. eth_sendTransaction, eth_estimateGas) — The MorphTx version no longer needs to be specified and is derived from the request. A non-empty authorizationList combined with feeTokenID, reference, or memo builds a v2 transaction. Otherwise, v1 is used. - eth_getTransactionByHash — Now returns authorizationList for MorphTx v2 transactions. - MorphTx v2 transactions with a non-empty authorizationList cannot create contracts (same rule as EIP-7702). - Fees for transactions paying gas in an alternative token may differ slightly from previous values due to the corrected refund rounding. https://github.com/morph-l2/morph/releases/tag/v0.6.4 https://github.com/morph-l2/go-ethereum/releases/tag/morph-v2.2.7 - **[Urgent] Stacks Mainnet - Upgrade to v9.7.0** (SCHEDULED, 2026-11-02T00:00:00.000Z): We are upgrading our Stacks Mainnet infrastructure to v9.7.0 on 2026-11-02. This release patches recent Node.js security vulnerabilities and introduces new v3 API endpoints for block and transaction data, along with enhanced transaction metadata. A brief database migration will occur during the upgrade, and brief interruptions to RPC availability may occur on that date. RPC Changes: - GET /extended/v3/blocks — New cursor-paginated endpoint for Stacks block summaries, including tenure_height, tx_count, and Bitcoin anchor block reference. - GET /extended/v3/blocks/{height_or_hash} — New endpoint providing Stacks block details, including parent block hash, block size, and execution cost. - GET /extended/v3/bitcoin-blocks — New cursor-paginated endpoint for Bitcoin block summaries with header time and associated Stacks/transaction counts. - GET /extended/v3/bitcoin-blocks/{height_or_hash} — New endpoint providing Bitcoin block details with header time and associated block/transaction counts. - GET /extended/v3/bitcoin-blocks/{height_or_hash}/blocks — New endpoint listing Stacks blocks anchored to a specific Bitcoin block. - event_count — Added to v3 transaction summaries across all v3 endpoints (transactions list, batch, block transactions, principal transactions, and search). - /v2 RPC proxy — Simplified to a plain passthrough; custom fee estimation and transaction endpoint configuration are no longer available. https://github.com/hirosystems/stacks-blockchain-api/releases/tag/v9.7.0 - **Solana Mainnet: Agave 4.4.0 and Yellowstone gRPC v17** (SCHEDULED, 2026-11-02T00:00:00.000Z): As part of our preparation for Agave 4.4 on Solana Mainnet, we are upgrading our Solana Mainnet endpoints to the latest releases: Agave 4.4.0, Yellowstone gRPC v17, and our matching RPC and WebSocket serving layers. Nodes restart one at a time, so requests continue to be served throughout. Devnet is the place to test your integration against these changes before they reach Mainnet. **Expected changes** JSON-RPC - getTransaction accepts an optional minContextSlot. If the node has not yet reached that slot, it returns error -32016 (minimum context slot not reached) instead of null. - getSignatureStatuses accepts optional commitment and minContextSlot. The default commitment is still processed. When you set one, statuses below it are not returned, and minContextSlot behaves as in getTransaction. - getLeaderSchedule: accepts an optional keyByVoteAccount to key the result by vote account instead of identity; returns error -32022 when you ask for an identity that is not in the schedule. It used to return an empty result {}. If your code treats {} as “not a leader this epoch”, handle this error instead. - getInflationGovernor now returns the cluster’s current inflation parameters instead of fixed default values. - getBlocks over wide ranges is faster. Results are unchanged. - Error messages for invalid base64 input keep the invalid base64 encoding: prefix, but the text after it may differ. Match on the prefix or the error code, not the full message. WebSocket - accountSubscribe and programSubscribe now apply dataSlice for binary encodings (base58, base64, base64+zstd). Notifications contain only the requested slice; a zero-length slice returns empty data. Before, dataSlice was ignored and the full account data was sent. If you send dataSlice but need full data, remove it. Yellowstone gRPC - The protobuf schema is unchanged, so existing clients need no update. - Subscribing with from_slot now replays without gaps or duplicates when the stream joins live data. from_slot is honored only on the first request of a stream; a later request’s from_slot is ignored. - On confirmed and finalized subscriptions, the CreatedBank slot event now arrives together with its block’s data, so its position in the stream can differ from before. - Alpenglow block-footer certificates are passed through exactly as the validator produces them, so none are dropped. ## QuickNode outage FAQ ### Is QuickNode down right now? It's under maintenance. 0 reports in the last hour. ### Is QuickNode down for everyone or just me? It looks like it's just you. Reports for QuickNode are at their usual level, so try reloading, checking your connection, or signing out and back in. ### What problems are people reporting with QuickNode? Nobody has said what's broken with QuickNode in the last hour. If something isn't working for you, pick it above so others can see. ### When was the last QuickNode outage? Reports for QuickNode haven't spiked in the last 30 days. ### Does QuickNode have a status page? Yes. QuickNode posts updates on its official status page, which currently says under maintenance. [Go to status page](https://status.quicknode.com/) ### What can I do if QuickNode isn't working? Check this page and QuickNode's status page for updates, and wait a few minutes before trying again. Skip reinstalling: if it's an outage, the fix is on their side. ### How do I report a QuickNode problem? Hit “I have an issue too” at the top of this page and pick what's broken. Your report shows on the live chart within a minute, and you can leave a comment to tell others what you're seeing. ### How does Instatus Now know? We combine reports from people on this page with QuickNode's official status page, which we check every minute.