Service Under Maintenance

About This Site

Welcome to the QuickNode status page. We use this page to communicate any issues with our products including planned and unplanned outages.

Uptime over the past 90 days. View historical uptime.
0g Operational
0g - Galileo Testnet Operational
0g - Mainnet Operational
Abstract Operational
Abstract - Mainnet Operational
Abstract - Testnet Operational
Aleo Operational
Aleo - Mainnet Operational
Aleo - Testnet Operational
Aptos Operational
Aptos - Mainnet Operational
Aptos - Testnet Operational
Arbitrum Operational
Arbitrum - Mainnet Nitro Operational
Arbitrum - Mainnet Classic Operational
Arbitrum - Sepolia Operational
Arbitrum Nova Operational
Arbitrum Nova - Mainnet Operational
Arc Operational
Arc - Testnet Operational
Arc - Mainnet Operational
Ault Operational
Ault - Testnet Operational
Ault - Mainnet Operational
Avalanche Operational
Avalanche - Mainnet Operational
Avalanche - Fuji Testnet Operational
B3 Operational
B3 - Mainnet Operational
B3 - Sepolia Operational
Base Operational
Base - Mainnet Operational
Base - Sepolia Operational
Berachain Operational
Berachain - Mainnet Operational
Berachain - Bepolia Operational
Bitcoin Operational
Bitcoin - Mainnet Operational
Bitcoin - Testnet Operational
Bitcoin Cash Operational
Bitcoin Cash - Mainnet Operational
Bitcoin Cash - Testnet Operational
Blast Operational
Blast - Mainnet Operational
Blast - Sepolia Operational
BNB Smart Chain (BSC) Operational
BNB - Mainnet Operational
BNB - Testnet Operational
Celestia Operational
Celestia - Mainnet Operational
Celestia - Mocha Testnet Operational
Celo Operational
Celo - Mainnet Operational
Cosmos Operational
Cosmos - Mainnet Operational
Cyber Operational
Cyber - Mainnet Operational
Cyber - Sepolia Operational
DOGE Operational
DOGE - Mainnet Operational
Ethereum Operational
Ethereum - Mainnet Operational
Ethereum - Sepolia Operational
Ethereum - Hoodi Operational
Flare Operational
Flare - Coston2 Testnet Operational
Flare - Mainnet Operational
Flow Operational
Flow - Mainnet Operational
Flow - Testnet Operational
Fluent Operational
Fluent - Testnet Operational
Fluent - Mainnet Operational
Fraxtal (Select Access) Operational
Fraxtal - Mainnet Operational
Fuel Operational
Fuel - Mainnet Operational
Fuel - Sepolia Operational
Gnosis Operational
Gnosis - Mainnet Operational
Gravity Operational
Gravity - Alpham Operational
Gravity - Mainnet Operational
Hedera Operational
Hedera - Mainnet Operational
Hedera - Testnet Operational
Hemi Operational
Hemi - Mainnet Operational
Hemi - Testnet Operational
HyperLiquid Operational
HyperEVM - Mainnet Operational
HyperEVM - Testnet Operational
Hypercore - Mainnet Operational
Injective Operational
Injective - Mainnet Operational
Injective - Testnet Operational
Ink Operational
Ink - Mainnet Operational
Ink - Sepolia Operational
JOC Operational
JOC - Mainnet Operational
Kaia Operational
Kaia - Mainnet Operational
Kaia - Testnet Operational
Katana Operational
Katana - Mainnet Operational
Lens Operational
Lens - Mainnet Operational
Lens - Testnet Operational
Linea Operational
Linea - Mainnet Operational
Lisk (Select Access) Operational
Lisk - Mainnet Operational
Litecoin Operational
Litecoin - Mainnet Operational
Litecoin - Testnet Operational
Mantle Operational
Mantle - Mainnet Operational
Mantle - Sepolia Operational
MegaETH Operational
MegaETH - Mainnet Operational
Moca Operational
Moca - Testnet Operational
Mode (Select Access) Operational
Mode - Mainnet Operational
Monad Operational
Monad - Testnet Operational
Monad - Mainnet Operational
Morph Operational
Morph - Mainnet Operational
Morph - Hoodi Testnet Operational
NEAR Operational
NEAR - Mainnet Operational
NEAR - Testnet Operational
Optimism Operational
Optimism - Mainnet Operational
Optimism - Sepolia Operational
Osmosis (Select Access) Operational
Osmosis - Mainnet Operational
Osmosis - Mainnet Operational
Peaq Operational
Peaq - Mainnet Operational
Plasma Operational
Plasma - Mainnet Operational
Plasma - Testnet Operational
Polkadot Operational
Polkadot - Mainnet Operational
Polygon Operational
Polygon - Mainnet Operational
Polygon - Amoy Testnet Operational
RobinHood Operational
Robinhood - Testnet Operational
Robinhood - Mainnet Operational
Scroll Operational
Scroll - Mainnet Operational
SEI Operational
Sei - Pacific-1 Mainnet Operational
Sei - Atlantic-2 Testnet Operational
Solana Under Maintenance
Solana - Mainnet Under Maintenance
Solana - Devnet Operational
Solana - Testnet Operational
Soneium Operational
Soneium - Mainnet Operational
Sonic Operational
Sonic - Mainnet Operational
Stacks Operational
Stacks - Mainnet Operational
Stacks - Testnet Operational
Starknet Operational
Starknet - Mainnet Operational
Starknet - Sepolia Operational
Stellar Operational
Stellar - Mainnet Operational
Stellar - Testnet Operational
Sui Operational
Sui - Mainnet Operational
Sui - Testnet Operational
Tempo Operational
Tempo - Testnet Operational
Tempo - Mainnet Operational
TON Operational
TON - Mainnet Operational
Tron Operational
Tron - Mainnet Operational
Tron - Nile Testnet Operational
Unichain Operational
Unichain - Mainnet Operational
Unichain - Sepolia Testnet Operational
Vana Operational
Vana - Mainnet Operational
Vana - Moksha Testnet Operational
World Chain Operational
World Chain - Mainnet Operational
World Chain - Sepolia Operational
X Layer Operational
X Layer - Mainnet Operational
X Layer - Testnet Operational
XRP Ledger Operational
XRP Ledger - Mainnet Operational
XRP Ledger - Testnet Operational
XRPL EVM Operational
XRPL EVM - Mainnet Operational
XRPL EVM - Testnet Operational
Zcash Operational
Zcash - Mainnet Operational
Zcash - Testnet Operational
ZkSync Operational
ZKsync - Mainnet Operational
ZKsync - Testnet Operational
Zora (Select Access) Operational
Zora - Mainnet Operational
Quicknode Products Operational
Quicknode Faucet Operational
Multi-region Transaction Broadcast Operational
Single Flight RPC Operational
Quicknode NFT API Operational
Quicknode Token API Operational
IPFS Rest API Operational
Quicknode Solana DAS API Operational
Jupiter Swap API Operational
Quicknode Streams Operational
JITO Bundles & Transactions Operational
RPC Logs Operational
Quicknode Webhooks Operational
SQL API Operational
QuickNode Dashboard Operational
QuickNode Website Operational
Customer Support Operational
GIWA Operational
GIWA - Sepolia Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

[Urgent] Base - Sepolia and Mainnet- Upgrade to v1.5.0 Oct 19, 2026 00:00-23:59 UTC

We are upgrading our Base Sepolia and Mainnet infrastructure to v1.5.0 on 2026-10-19 to support the Denim hardfork on Sepolia. This release introduces hardfork support, performance improvements to proof generation and snapshot downloads, and critical bug fixes. Brief interruptions to RPC availability may occur on that date.

More info on the Denim hard fork: https://docs.base.org/upgrades/denim/overview#b20-improvements

Denim moves Base block production from one canonical block every two seconds to five complete canonical blocks per second, each with its own hash, state root, receipts, and forkchoice lifecycle. Denim replaces Flashblocks, so applications using Flashblocks must migrate to canonical block and RPC streams.

The "pending" block tag is also being retired. Denim activates at the protocol level on Sepolia at 18:00 UTC on October 21 — once that timestamp hits on Sepolia, Flashblocks subscriptions and any RPC call using "pending" (eth_getBalance, eth_getTransactionCount, eth_call, eth_estimateGas, eth_simulateV1, eth_getBlockByNumber, eth_getBlockTransactionCountByNumber, eth_getLogs ranges ending at "pending") stop returning preconfirmation data, with no direct equivalent. Replace these calls with normal requests against the latest canonical block before the fork activates. Inventory your Flashblocks subscriptions and "pending"-tag usage now and migrate ahead of October 21 — see the full migration table: https://docs.base.org/upgrades/denim/migrate-from-flashblocks

https://github.com/base/base/releases/tag/v1.5.0
Posted on Oct 15, 2026 - 17:31 UTC

[Standard] Stellar - Mainnet & Testnet - Upgrade to v29.0.1 Oct 20, 2026 00:00-23:59 UTC

We are upgrading our Stellar Mainnet RPC infrastructure to v29.0.1 on 2026-10-20. This patch release corrects the preflight simulation hosts for Protocol 29 and Protocol 28, ensuring each protocol's host builds against its own matching soroban-wasmi version and maintains compatibility with stellar-core. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
RPC — The protocol 28 host is now built from the rs-soroban-env v28.0.1 commit, the same code as the crates.io 28.0.1 release, so that each host can use its own `soroban-wasmi` build. Protocol 28 preflight simulation is unchanged. **Full Changelog**: https://github.com/stellar/stellar-rpc/compare/v29.0.0...v29.0.1

https://github.com/stellar/stellar-rpc/releases/tag/v29.0.1
Posted on Oct 13, 2026 - 17:32 UTC

Standard Stacks - Mainnet - Upgrade to 4.0.5 Oct 21, 2026 00:00-23:59 UTC

We are upgrading our Stacks Mainnet infrastructure to stacks-core 4.0.5 on 2026-10-21. This release includes bugfixes and stability improvements for block production, along with miner and signer stall fixes. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
- /v3/stacker_set — RPC OpenAPI schema and example updated for PoX-5 reward sets, now with a separate dedicated schema.
- RPC OpenAPI descriptions, schemas and examples — Updated across the board for Epoch 4.0 and PoX-5 compatibility.

https://github.com/stacks-network/stacks-core/releases/tag/4.0.5
Posted on Oct 14, 2026 - 18:12 UTC

[Standard] Monad Testnet - v0.16.5 Oct 21, 2026 00:00-23:59 UTC

We are upgrading our Monad Testnet infrastructure to v0.16.5 on 2026-10-21. This release improves RPC behavior around state overrides and simulation, hardens memory safety in EVM decoding and triedb operations, and refines node robustness. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
- eth_simulateV1 — Now enforces the configured maximum response size; requests exceeding this limit will be rejected. It also now exits gracefully when a block state merge fails instead of terminating the request abnormally.
- eth_simulateV1 — Empty full state overrides now zero the overridden account's storage, matching Geth behavior.
- Triedb range query — Now validates prefix key length to prevent buffer over-reads.

https://github.com/category-labs/monad-bft/releases/tag/v0.16.5
Posted on Oct 15, 2026 - 18:57 UTC

Solana Mainnet: Alpenglow Consensus Upgrade Oct 21, 2026 14:50-17:50 UTC

Update - **What to expect during the Alpenglow switch (Oct 21)**

- Timing. Anza estimates the activation at about 14:50 UTC. At the current block rate it could come as early as 13:20 UTC. The switch-over follows about 20 minutes later. Please be ready from 13:00 UTC.

- For a few seconds while the network hands over to Alpenglow, new transactions won’t be included in blocks. If the network takes longer to complete the switch, the pause lasts until it does.

- Around the switch, sendTransaction may briefly return a “node unhealthy” preflight error. Retry, or send with skipPreflight.

- Subscriptions at processed commitment may show a few slots that are never confirmed. Use confirmed or finalized for anything that must not be reverted.

- Yellowstone gRPC streams may disconnect once around the switch. Clients with automatic reconnect need no action.

- After the switch, confirmed and finalized stay within about a slot of each other, so finality is much faster.

Relevant Links:
- https://www.anza.xyz/alpenglow
- https://www.quicknode.com/blog/solana-alpenglow-upgrade
- https://solana.com/upgrades/alpenglow
Oct 15, 2026 - 22:13 UTC
Scheduled - Solana Mainnet is switching to Alpenglow, Solana's new consensus protocol (SIMD-0326). The Solana developers at Anza plan to turn it on Wednesday, October 21, around 14:50 UTC.

**What this means for you**
- This change applies to Solana Mainnet. Testnet and Devnet already run Alpenglow and are not affected.
- The network may be briefly unstable while the switch-over happens.
- Your Quicknode Solana endpoints stay the same. You don't need to change anything.

**What we're doing**
- Our Solana Mainnet infrastructure already runs Agave v4.3.0.
- We're pausing all planned maintenance on Solana Mainnet during the upgrade window.
- Our team will actively monitor the network during and after the switch-over, and we'll post updates here if we see any impact.

**Try Alpenglow now**
If you want to check how your application behaves under Alpenglow before it reaches Mainnet, it's already live on Solana Testnet and Devnet.

Relevant links:
https://www.anza.xyz/alpenglow
https://www.quicknode.com/blog/solana-alpenglow-upgrade
https://solana.com/upgrades/alpenglow
Oct 13, 2026 - 19:08 UTC

[Standard] Katana Mainnet - Upgrade to conduit-op-reth v2.4.0 Oct 22, 2026 00:00-23:59 UTC

We are upgrading our Katana Mainnet infrastructure to conduit-op-reth v2.4.0 on 2026-10-22. This release upgrades to upstream op-reth v2.6.0 (reth v2.5.2), bringing Engine API responsiveness improvements, persistence tuning, stricter chain spec validation, and security patches. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
eth_call, eth_estimateGas, eth_simulateV1 — Flashblocks pending-state overrides now apply only on transports serving the eth namespace. Requests on other transports will not receive override behavior.
eth_getProof, debug_executePayload — Proofs-history overrides now apply only on transports serving the debug namespace. Requests on other transports will not receive override behavior.

https://github.com/conduitxyz/conduit-op-reth/releases/tag/v2.4.0
Posted on Oct 15, 2026 - 18:34 UTC

[Standard] Hedera - Upgrade to Mirror Node v0.164.2 and JSON-RPC Relay v0.80.1 Oct 22, 2026 00:00-23:59 UTC

We are upgrading our Hedera infrastructure to Mirror Node v0.164.2 and JSON-RPC Relay v0.80.1 on 2026-10-22. Mirror Node v0.164.2 provides compatibility with consensus node v0.78 and prevents failures in the web3 module and contract call endpoints. JSON-RPC Relay v0.80.1 strengthens Ethereum JSON-RPC spec compliance, improves state override handling, adds EIP-1898 block identifier support, corrects error codes and receipt fields, and hardens the public endpoint with CORS allowlisting and client-IP detection. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
- state overrides — Now compliant with HIP-1485; state override syntax and behavior have been updated to align with Hedera specification.
- Block identifiers — EIP-1898 block identifier format is now supported for methods accepting block parameters; legacy block number and hash formats remain compatible.
- Transaction receipt fields — Receipt field names and values have been corrected for Ethereum JSON-RPC spec compliance; affected fields include status codes and transaction type indicators.
- Error codes — JSON-RPC error codes have been standardized to match the Ethereum JSON-RPC specification; clients relying on specific error codes may see different values for certain error conditions.
- WebSocket address limits — WS_MULTIPLE_ADDRESSES_LIMIT configuration parameter has been removed and replaced by MAX_ADDRESSES_PER_REQUEST (default 1000); WebSocket subscriptions are now subject to this per-request address cap.

https://github.com/hiero-ledger/hiero-mirror-node/releases/tag/v0.164.2
Posted on Oct 15, 2026 - 18:50 UTC

Oct 16, 2026

No incidents reported today.

Oct 15, 2026

Urgent Ethereum Mainnet - Upgrade to Geth v1.17.8
Completed - The scheduled maintenance has been completed.
Oct 15, 23:59 UTC
Scheduled - We are upgrading our Ethereum Mainnet infrastructure to Geth v1.17.8 on 2026-10-15. This is a security-focused release, along with several RPC correctness improvements. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
eth_createAccessList — Now works correctly when the sender account has no balance.
eth_simulateV1 — Fixed to correctly report ETH transfer logs post-Amsterdam fork.
eth_simulateV1 — Virtual blocks are now aligned with the Amsterdam specification.
eth_capabilities — Now reports the availability of receipts bounded by the transaction hash index.
eth_call — Transaction gas limit is no longer applied after the Amsterdam fork.

https://github.com/ethereum/go-ethereum/releases/tag/v1.17.8
Oct 8, 18:27 UTC
[Standard] Op-stack - Upgrade to op-reth v2.6.0 and op-node v1.19.9
Completed - The scheduled maintenance has been completed.
Oct 15, 23:59 UTC
Scheduled - We are upgrading our Optimism stack chains to op-reth v2.6.0 and op-node v1.19.9 on 2026-10-15. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
- Transaction pool — changed: A sender's transaction cost now includes the L1 data fee and operator fee, not only L2 execution cost. If a later-nonce transaction from the same sender cannot cover the fees of that sender's earlier transactions, it is now marked as queued instead of pending. It then expires after the standard pool lifetime instead of being retried every block. This matches op-geth behavior. Users submitting several transactions in a row from a low-balance account may see later transactions stay queued and expire.
- debug_executionWitness — improved: Now accepts a block hash as well as a block number.
- debug_executePayload — improved: Now also returns the ancestor headers used during execution.
- isSystemTx field — changed: For deposit transactions flagged as system transactions, transaction responses now return a JSON boolean (true) instead of "0x1", matching op-geth. This flag appears only in pre-Regolith blocks, which do not exist on Optimism Mainnet or Sepolia, so in practice users will not see a difference.

https://github.com/ethereum-optimism/optimism/releases/tag/op-reth/v2.6.0
https://github.com/ethereum-optimism/optimism/releases/tag/op-node/v1.19.9
Oct 7, 21:06 UTC
[Standard] Ethereum Hoodi and Sepolia - Upgrade to Reth v2.7.0
Completed - The scheduled maintenance has been completed.
Oct 15, 13:38 UTC
Update - We will be undergoing scheduled maintenance during this time.
Oct 15, 13:32 UTC
Update - We will be undergoing scheduled maintenance during this time.
Sep 28, 15:53 UTC
Scheduled - We are upgrading our Ethereum Hoodi and Sepolia infrastructure to Reth v2.7.0 on 2026-10-01. This is a required upgrade ahead of the Glamsterdam (Amsterdam) hardfork on Sepolia, scheduled for 2026-10-06 at 13:53:36 UTC. The release also includes all changes from v2.6.0, bringing expanded Amsterdam protocol support, performance improvements across block processing and historical-state queries, and several RPC correctness fixes. Brief interruptions to RPC availability may occur during the maintenance window.

RPC Changes:
- eth_estimateGas — Now respects the node's RPC gas cap, and the basic-transfer shortcut returns actual used gas, fixing post-Amsterdam overestimation of up to 75%.
- eth_getLogs — Returns an error when matching receipts have been pruned instead of incomplete results. Memory and CPU overhead have also been reduced.
- trace_callMany / trace_filter — Calls without a specified block (trace_callMany) or without block bounds (trace_filter) now default to latest. Users needing pending state or historical ranges should specify them explicitly.
- trace_get — Now selects results by trace tree path, and replaying a missing transaction returns null.
- eth_callBundle — Now derives the next-block base fee for bundle simulation.
- Transaction submission and signing — Rejects a supplied chainId that does not match the network, preventing accidental cross-chain resubmission.
- EIP-7702 authorization — Returns null for sender-nonce gaps consumed by authorization entries.
- Transaction pool — Pending blob transactions are parked when blob fee rises while base fee falls, and transactions below the tracked sender nonce are rejected.

https://github.com/paradigmxyz/reth/releases/tag/v2.7.0
https://github.com/paradigmxyz/reth/releases/tag/v2.6.0
Sep 22, 14:18 UTC
[Standard] Zcash Mainnet - Upgrade to Zebra 6.4.0
Completed - The scheduled maintenance has been completed.
Oct 15, 13:38 UTC
Update - We will be undergoing scheduled maintenance during this time.
Oct 15, 13:31 UTC
Scheduled - We are upgrading our Zcash Mainnet infrastructure to Zebra 6.4.0 on 2026-10-01. This release improves block template performance through precomputation, and includes multiple security and stability fixes.

Brief interruptions to RPC availability may occur on that date.

RPC Changes:
- getblocktemplate — Now uses precomputed block templates for the current chain tip when available, refreshed on tip changes and periodically, reducing latency for miners; templates may be a few seconds behind the mempool but are validated against the committed tip.
- getstandardfee — Reports updated conventional fee of 1000 zatoshis per ZIP-317 logical action (down from 5000; 2000 instead of 10000 for a minimal transaction).
- z_gettreestate — No longer returns null commitments for blocks moved to a side chain during concurrent reorgs.
- RPC response body size — `rpc.max_response_body_size` is now capped at 4,294,967,295 bytes; larger configured values are rejected during configuration loading.

https://github.com/ZcashFoundation/zebra/releases/tag/v6.4.0
Sep 23, 19:20 UTC
Urgent XRPL EVM Mainnet - Upgrade to v10.2.1
Completed - The scheduled maintenance has been completed.
Oct 15, 13:38 UTC
Update - We will be undergoing scheduled maintenance during this time.
Oct 15, 13:31 UTC
Scheduled - We are upgrading our XRPL EVM Mainnet infrastructure to node v10.2.1 on 2026-09-30. This is a hotfix release that updates the underlying cosmos/evm module to v0.6.2-august-2026-hotfix-xrplevm.2, addressing core EVM functionality improvements.

Brief interruptions to RPC availability may occur on that date.

https://github.com/xrplevm/node/releases/tag/v10.2.1
Sep 17, 16:38 UTC
[Standard] Stacks - Upgrade API to v9.3.1 & Core 4.0.4
Completed - The scheduled maintenance has been completed.
Oct 15, 13:38 UTC
Update - We will be undergoing scheduled maintenance during this time.
Oct 15, 13:31 UTC
Scheduled - We are upgrading our Stacks infrastructure to Stacks API v9.3.1 and stacks-core 4.0.4 on 2026-09-30. The API release includes a small database migration. The stacks-core release delivers bug fixes and stability improvements for more consistent block production, and introduces Clarity 7 ahead of Epoch 4.1. Brief interruptions to RPC availability may occur during the maintenance.

RPC Changes:

Stacks API (v9.3.1)
- v3 fungible token balances — fixed. Results are now sorted by numeric balance value.

Stacks Core (4.0.4)
- Error messages — changed. vm_error in transaction receipts, the cause field in read-only call responses, and block rejection reasons are now capped at 4096 bytes. Tuple and list values in these messages now render in Clarity syntax (e.g. (tuple (a u1))) instead of internal debug format. Users parsing these strings should update their handling.
- Smart contract deploys (from Epoch 4.1) — breaking. VersionedSmartContract payloads will be rejected as invalid. Deploy using the unversioned SmartContract payload, which defaults to Clarity 7.
- replace-at? (from Epoch 4.1) — fixed. A zero-length buffer or string element is now rejected at type-check time, or fails with an includable error at runtime, rather than making the transaction rejectable.

https://github.com/hirosystems/stacks-blockchain-api/releases/tag/v9.3.1
https://github.com/stacks-network/stacks-core/releases/tag/4.0.4
Sep 23, 15:45 UTC
[Standard, Fork] Ethereum - Sepolia/Hoodi - Upgrade to Geth-v1.17.6 & Erigon v3.7.0
Completed - The scheduled maintenance has been completed.
Oct 15, 13:31 UTC
Scheduled - We are upgrading our Ethereum Sepolia infrastructure to Geth v1.17.6 and Erigon v3.7.0 on 2026-09-30. Both releases include required support for the Amsterdam (Glamsterdam) hard fork, scheduled on Sepolia for October 6, 2026.
Geth v1.17.6 delivers performance improvements to block processing and initial sync. Erigon v3.7.0 brings broad RPC performance improvements, including faster eth_getLogs, eth_feeHistory, and eth_getProof responses, along with improved RPC correctness at the chain tip and closer alignment with Geth behavior.

Brief interruptions to RPC availability may occur.

RPC Changes (Geth):
- eth_getLogs — Now rejects ranges where toBlock is before fromBlock; requests with invalid block ranges will return an error.
- eth_getHeaderByNumber — Returns null for pending and unresolvable tags instead of attempting resolution.
- eth_simulateV1 — Post-merge difficulty overrides are now treated as no-op; difficulty parameters no longer affect simulation outcomes.
- eth_createAccessList — Removed per-authorization gas guard; gas accounting behavior has been simplified.
- debug_traceCall — Block parameter is now optional; omitting it will use the latest block by default.

RPC Changes (Erigon):
- All methods — A null value for a required positional argument now returns error -32602 instead of silently defaulting to zero, matching Geth.
- eth_call, eth_createAccessList, eth_simulateV1, eth_getProof, debug tracing — Requests using the pending block tag are rejected where matching state is unavailable; use latest or an explicit block number.
- eth_call, eth_estimateGas, eth_simulateV1, eth_createAccessList — Access lists are rejected before Berlin and blob hashes before Cancun; eth_createAccessList also rejects pre-Berlin blocks.
- eth_getFilterLogs — Now queries the filter's stored criteria without draining eth_getFilterChanges or renewing the filter lifetime. Log filters and subscriptions with more than four topic positions return -32602.
- eth_getFilterChanges, eth_subscribe("logs"), erigon_getLogsByHash — Logs now include blockTimestamp, matching eth_getLogs.
- erigon_getLogs, erigon_getLatestLogs — The timestamp field has been renamed to blockTimestamp.
- debug_traceTransaction, debug_traceBlock, debug_traceCallMany (callTracer with withLog) — Log indices are now block-wide for transaction and block traces, and bundle-wide for debug_traceCallMany, instead of transaction-local.
- callTracer — Omits to for failed CREATE/CREATE2 calls instead of returning the zero address, matching Geth.
- eth_getHeaderByHash, eth_getHeaderByNumber — New header-only query methods in the eth namespace.
- eth_estimateGas — State overrides now apply to balance and code checks as well as execution; blob funds are reserved before calculating gas allowance, matching Geth.
- eth_call — No longer charges the blob base fee when blob fields are supplied without a nonzero blob fee cap.
- trace_callMany — Preserves earlier simulated calls' state regardless of trace type and no longer reads changes from the next block.
- eth_sendRawTransaction — EIP-7702 delegated senders are limited to one in-flight transaction and cannot submit nonce-gapped transactions; same-nonce replacement remains supported.
- eth_syncing, eth_subscribe("syncing") — Now report sync-state changes over WebSocket and show snapshot download progress.

https://github.com/ethereum/go-ethereum/releases/tag/v1.17.6
https://github.com/erigontech/erigon/releases/tag/v3.7.0
Sep 23, 16:06 UTC
[Urgent] Mantle Mainnet - Upgrade op-geth to v1.6.3
Completed - The scheduled maintenance has been completed.
Oct 15, 13:31 UTC
Scheduled - We are upgrading our Mantle Mainnet infrastructure to op-geth v1.6.3 on 2026-09-29. This release introduces the Elysium execution client, providing compatibility with Ethereum L1 Glamsterdam through the Amsterdam execution framework. The upgrade includes upstream go-ethereum v1.17.3 with EIP-7708 ETH transfer logs, EIP-7928 block access lists, and related Engine and networking changes. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
- eth_simulateV1 — Now supports Mantle fee calculation and returns eth_config safely for blobless OP Stack configurations and Amsterdam forks.
Block headers — The canonical JSON key blockAccessListHash is now used for EIP-7928 block access list references.
- Deposit encoding — Failed BVM_ETH deposit transactions are now represented with correct JSON encoding in receipts and block data.

https://github.com/mantle-xyz/op-geth/releases/tag/v1.6.3
Sep 21, 16:59 UTC
[Urgent] XRP Ledger - Mainnet - Upgrade to xrpld 3.4.0
Completed - The scheduled maintenance has been completed.
Oct 15, 13:31 UTC
Scheduled - We are upgrading our XRP Ledger Mainnet infrastructure to xrpld 3.4.0 on 2026-09-28. This is a major release introducing two new amendments—LendingProtocolV1_1 (extending Single Asset Vaults and the Lending Protocol with closed-ended vaults and cash-basis accounting) and fixCleanup3_4_0 (bundling protocol fixes)—while retiring the fixAMMOverflowOffer amendment as a permanent part of the protocol. The release also includes bug fixes, security hardening, and stability improvements. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
ledger — Added nftoken_id, nftoken_offer_id, and delivered_amount (for AccountDelete transactions) to transaction metadata in ledger RPC responses, matching tx and account_tx methods.
NFT buy/sell flag validation — NFT RPC input now validates the buy/sell flag and will reject invalid flag combinations.

https://github.com/XRPLF/rippled/releases/tag/3.4.0
Sep 21, 18:08 UTC
Urgent Base - Mainnet - Upgrade to v1.4.2
Completed - The scheduled maintenance has been completed.
Oct 15, 13:30 UTC
Scheduled - We are upgrading our Base Mainnet infrastructure to v1.4.2 on 2026-09-28.

This release introduces support for the Cobalt hardfork, a consensus-critical network upgrade.
Brief interruptions to RPC availability may occur on that date.

https://github.com/base/base/releases/tag/v1.4.2
Sep 23, 17:35 UTC

Oct 14, 2026

[Urgent] Sui - Testnet - Upgrade to testnet-v1.82.1 (Includes JSON RPC decommission)
Completed - The scheduled maintenance has been completed.
Oct 14, 23:59 UTC
Scheduled - We are upgrading our Sui Testnet infrastructure to testnet-v1.82.1 on 2026-10-14. This release advances the Sui protocol to version 139 with consensus-affecting changes including reduced non-refundable storage fees (from 1% to 0.01% of the storage rebate) and new per-byte object read cost charging for non-system package inputs. The release also removes the JSON-RPC service from full nodes entirely and adds ML- signature support across gRPC and GraphQL. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
JSON-RPC service — API decommissioned: The entire JSON-RPC service has been removed from full nodes in this release; clients calling JSON-RPC endpoints will fail. Migrate to gRPC or GraphQL endpoints.
SimulateTransaction (gRPC) — When `enable-simulate-allowed-proposers` is enabled, transaction simulation now restricts results to allowed proposers only for clients sending an `x-sui-client-protocol-version` header of 136 or higher.
kv-rpc (gRPC) — Accepts optional `x-sui-consistent-read-checkpoint` request header; when set, the server waits until it can serve data up to that checkpoint before responding, returning `Unavailable` if it cannot within timeout.
https://github.com/MystenLabs/sui/releases/tag/testnet-v1.82.1
Oct 13, 20:15 UTC
[Standard] Hyperliquid Nanoreth Upgrade to nb-20261007
Completed - The scheduled maintenance has been completed.
Oct 14, 18:20 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 14, 16:20 UTC
Scheduled - We are upgrading our Hyperliquid Nanoreth node to nb-20261007. During the maintenance window, brief interruptions to RPC availability may occur. This release contains a bug fix for RPC compatibility.

## RPC Changes

**`eth_getLogs` — fixed**
Queries targeting future block ranges now return an 'invalid block range' error instead of an empty result, matching canonical hl-node behavior. Applications relying on empty responses for out-of-range queries will now receive an error instead.

---

https://github.com/hl-archive-node/nanoreth/releases/tag/nb-20261007
Oct 7, 16:20 UTC

Oct 13, 2026

[Standard] Bitcoin Cash - Mainnet & Testnet - Upgrade to v29.2.0
Completed - The scheduled maintenance has been completed.
Oct 13, 23:59 UTC
Scheduled - We are upgrading our Bitcoin Cash infrastructure to Bitcoin Cash Node v29.2.0 on 2026-10-13. This release introduces native Schnorr signature signing by default, adds and updates multiple RPC methods for ecosystem compatibility, removes the obsolete excessive blocksize feature, and includes performance optimizations and a JSON-RPC input sanitization security fix. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
New
• simulaterawtransaction — New method that calculates the balance change that would result from signing and broadcasting the given transaction(s).


https://github.com/bitcoin-cash-node/bitcoin-cash-node/releases/tag/v29.2.0
Oct 5, 18:00 UTC
Quicknode API Authentication Outage - Streams, KV Store, and Webhooks Affected
Resolved - The issue affecting our API authentication has been resolved. The incident was limited to a small number accounts. All services, including Quicknode Streams, KV Store, and Webhooks, are operating normally.
Oct 13, 16:16 UTC
Investigating - We are investigating an issue with our internal Quicknode API that is causing authentication failures for multiple accounts. Quicknode Streams, KV Store REST API, and Webhooks are currently affected. We will update this page as we acquire new information.
Oct 13, 15:23 UTC

Oct 12, 2026

[Standard] Avalanche - Upgrade to v1.15.1
Completed - The scheduled maintenance has been completed.
Oct 12, 23:59 UTC
Scheduled - We are upgrading our Avalanche infrastructure to avalanchego v1.15.1 on 2026-10-12. This is a backwards-compatible patch release focused on C-Chain (SAE) correctness and performance improvements, along with minor API enhancements. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
eth_estimateGas — Now includes the minimum gas limit required by the mempool for the transaction's size. Large transactions signed with estimates will no longer be rejected with 'insufficient gas limit for tx size'.
eth_createAccessList — Now includes the minimum gas limit required by the mempool for the transaction's size. Large transactions signed with estimates will no longer be rejected with 'insufficient gas limit for tx size'.
platform.getCurrentValidators — New fields 'restakedValidationRewards' and 'restakedDelegateeRewards' have been added to results for auto-renewed validators.

https://github.com/ava-labs/avalanchego/releases/tag/v1.15.1
Oct 2, 16:34 UTC
[Urgent] Sonic - Mainnet - Upgrade to v2.2.5
Completed - The scheduled maintenance has been completed.
Oct 12, 23:59 UTC
Scheduled - We are upgrading our Sonic Mainnet infrastructure to v2.2.5 on 2026-10-12. This is a stability release that hardens the security posture of publicly exposed RPC nodes by restricting custom JavaScript tracers in debug methods. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
debug_trace* — Custom JavaScript tracers are now rejected by default with a `custom tracer is not permitted` error. Built-in tracers continue to work without configuration changes.

https://github.com/0xsoniclabs/sonic/releases/tag/v2.2.5
Oct 7, 20:21 UTC

Oct 11, 2026

[Standard] Tron - Mainnet and Nile Testnet - Upgrade to v4.8.2.2
Completed - The scheduled maintenance has been completed.
Oct 11, 22:36 UTC
Update - We will be undergoing scheduled maintenance during this time.
Oct 11, 22:34 UTC
Scheduled - We are upgrading our Tron Mainnet infrastructure to v4.8.2.2 and our Tron Nile Testnet infrastructure to v4.8.2.2-PQ1-build1. This is a mandatory upgrade issued by the Tron Foundation, applying to both mainnet and Nile testnet.

During the maintenance window, brief interruptions to RPC availability may occur.

RPC Changes:
- Contract deployment transactions now go through refined validation, improving consistency and reliability for users deploying smart contracts. Stake 2.0 and SELFDESTRUCT instruction handling has been optimized for edge cases, improving consistency of contract execution results for affected calls.

Mainnet release: https://github.com/tronprotocol/java-tron/releases/tag/GreatVoyage-v4.8.2.2 Nile Testnet release: https://github.com/tron-nile-testnet/nile-testnet/releases/tag/GreatVoyage-Nile-v4.8.2.2-PQ1-build1
Sep 9, 19:08 UTC
Solana Mainnet - Alpenglow Regenesis
Resolved - This incident has been resolved.
Oct 11, 00:04 UTC
Investigating - Solana Mainnet is currently undergoing a regenesis as part of the Alpenglow upgrade. We are monitoring the process and will provide updates as more information becomes available.
Oct 8, 18:50 UTC
Scheduled: Solana Mainnet - Upgrade Agave to v4.3.0
Completed - The scheduled maintenance has been completed.
Oct 11, 00:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 8, 00:02 UTC
Scheduled - We will be upgrading our Agave nodes on Solana Mainnet to v4.3.0 on October 8th at 00:00 UTC.

This update includes the following Highlighted Changes:

- getBlock, getTransaction and blockSubscribe now reject requests that combine encoding: "base58" (or "binary") with maxSupportedTransactionVersion >= 1, returning JSON-RPC error -32602 "base58 encoding is not supported with maxSupportedTransactionVersion >= 1". Use json, jsonParsed or base64 encoding for Transaction V1 requests.

- getInflationReward now accepts at most 32 addresses per request; larger lists return JSON-RPC error -32602 "Too many inputs provided; max 32". Split larger requests into batches of 32.

- Yellowstone gRPC moves to the v16 line. Existing subscriptions keep working unchanged, including clients built from the v15 proto. The v16 additions (a bank_id field on updates, a block_footer subscription) are optional and inert on Mainnet until Alpenglow activates; regenerate your app from the v16 proto only if you want them.

No JSON-RPC method is added or removed. RPC, WebSocket and gRPC endpoints will remain available throughout the upgrade window.

Please reach out to our Support team if you are experiencing any issues during the maintenance window.
- https://quicknode.portal.usepylon.com/forms/submit-a-support-ticket
Oct 7, 20:57 UTC

Oct 10, 2026

Morph mainnet : Degraded performance in EU region
Resolved - This incident has been resolved.
Oct 10, 22:19 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Oct 10, 09:05 UTC
Identified - The issue has been identified and a fix is being implemented.
Oct 10, 09:00 UTC
Investigating - We are currently investigating this issue.
Oct 10, 08:50 UTC
Morph mainnet : Degraded performance in EU region
Resolved - This incident has been resolved.
Oct 10, 04:00 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Oct 10, 03:30 UTC
Identified - The issue has been identified and a fix is being implemented.
Oct 10, 02:15 UTC
Investigating - We are currently investigating this issue.
Oct 10, 02:00 UTC

Oct 9, 2026

[Urgent] Starknet - Mainnet - Upgrade to v0.24.2
Completed - The scheduled maintenance has been completed.
Oct 9, 19:02 UTC
Scheduled - We are upgrading our Starknet Mainnet infrastructure to Pathfinder v0.24.2 on 2026-10-09. This release modifies the behavior of the starknet_estimateMessageFee RPC method to enforce a minimum overall fee for L1 → L2 messages. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
starknet_estimateMessageFee — The overall_fee response field now has a minimum value of 5×10^13 wei for L1 → L2 messages. When this minimum applies, overall_fee no longer equals the sum of gas amounts multiplied by their prices.

https://github.com/software-mansion/pathfinder/releases/tag/v0.24.2
Oct 8, 14:39 UTC
Arbitrum Nova – Block production halted
Resolved - Block production on Arbitrum Nova has resumed, and our nodes are syncing normally. Thanks for your patience.
Oct 9, 13:30 UTC
Investigating - We're investigating an issue on Arbitrum Nova where no new blocks have been produced since block 85283638. We're in contact with the Arbitrum team to understand the cause, and we'll share an update as soon as we have more information.
Oct 9, 13:21 UTC
Morph mainnet : Degraded performance in EU region
Resolved - This incident has been resolved.
Oct 9, 06:30 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Oct 9, 06:15 UTC
Identified - The issue has been identified and a fix is being implemented.
Oct 9, 06:05 UTC
Investigating - We are currently investigating this issue.
Oct 9, 06:00 UTC
Urgent Hedera - Mainnet - Upgrade to v0.164.0
Completed - The scheduled maintenance has been completed.
Oct 9, 00:00 UTC
Scheduled - We are upgrading our Hedera Mainnet infrastructure to Hedera Mirror Node v0.164.0 on 2026-10-08. This release contains multiple security fixes (dozens of gaps closed), along with enhancements to REST API endpoints for contract results and improved gas estimation accuracy. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
/api/v1/contracts/{contract}/results/{timestamp} — Now includes synthetic contract results, making synthetic contract logs generated for non-EVM transfers searchable on this single-item lookup endpoint.
/api/v1/contracts/results/{id} — Now includes synthetic contract results consistently with other contract result list endpoints.
/api/v1/contracts/results — Non-wildcard synthetic contract results are now included consistently across all contract result list endpoints.
Gas estimation — Accuracy improved with fixes to gas estimate calculations in web3 queries.

https://github.com/hiero-ledger/hiero-mirror-node/releases/tag/v0.164.0
Oct 2, 14:37 UTC

Oct 8, 2026

Urgent Sui - Mainnet - Upgrade to mainnet-v1.81.1
Completed - The scheduled maintenance has been completed.
Oct 8, 23:59 UTC
Scheduled - We are upgrading our Sui Mainnet infrastructure to mainnet-v1.81.1 on 2026-10-08. This release introduces protocol version 138 with consensus and execution engine updates, including gas model refinements, memory invariant checks for Programmable Transaction Blocks, and object fund withdrawal validation. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
derivedderivedObject and multiGetDerivedObjects — New fields added to IAddressable in GraphQL for fetching derived objects.
multiGetDynamicFields — New GraphQL query for fetching multiple dynamic fields across different parent objects.
Balance.coinMetadata — New nullable field added to Balance in GraphQL responses.
Transaction.effects.checkpoint — Now resolves correctly for transactions delivered over GraphQL subscriptions; it was previously always null.

https://github.com/MystenLabs/sui/releases/tag/mainnet-v1.81.1
Oct 7, 20:03 UTC
[Standard] Optimism-Stack Chains - Upgrade to op-node v1.19.8 & op-reth v2.5.0
Completed - The scheduled maintenance has been completed.
Oct 8, 23:59 UTC
Scheduled - We are upgrading our Op-stack Mainnet and Testnet infrastructure to op-node v1.19.8 and op-reth v2.5.0. These are recommended maintenance releases. The op-node update adds stricter validation of hardfork activation times in rollup configurations and includes a block-building performance improvement. The op-reth update includes security updates for two underlying dependencies, improving TLS connection handling and the stability of transaction pool processing. No action is required from users.
During the maintenance window, brief interruptions to RPC availability may occur.

https://github.com/ethereum-optimism/optimism/releases/tag/op-node/v1.19.8
https://github.com/ethereum-optimism/optimism/releases/tag/op-reth/v2.5.0
Oct 1, 14:57 UTC
Near Mainnet - Degraded Performance
Resolved - This incident has been resolved.
Oct 8, 19:17 UTC
Monitoring - Service has stabilized and we are monitoring for stability.
Oct 8, 17:17 UTC
Investigating - We are currently investigating the elevated API errors being served on Near Mainnet. We will post updates as we receive further information.
Oct 8, 16:45 UTC
World Chain Mainnet – Intermittent 503 errors
Resolved - This incident has been resolved.
Oct 8, 18:35 UTC
Identified - The World Chain team has confirmed the root cause of the intermittent 503 errors and is preparing a new node client release with a fix. We'll deploy it across our World Chain Mainnet nodes as soon as it's available. In the meantime, we're continuing to monitor closely, and some requests may still intermittently return 503 errors.
Oct 5, 13:32 UTC
Investigating - World Chain Mainnet requests may intermittently return 503 errors. We've identified the cause as an issue in the node client affecting some of our backend nodes, and we're working with the World Chain team to resolve it. We're monitoring closely and will share updates as they become available.
Oct 5, 12:17 UTC
Urgent Stacks Mainnet - Upgrade to v4.0.4
Completed - The scheduled maintenance has been completed.
Oct 8, 00:01 UTC
Scheduled - We are upgrading our Stacks Mainnet infrastructure to stacks-core v4.0.4 on 2026-10-07. This is a stability and bugfix release addressing block production consistency, signature verification corrections in the Wasm backend, and removal of deprecated transaction-replay configuration. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
- /v3/tenures/fork_info — The nakamoto_blocks field is now always null and is deprecated; it will be removed in a future release.
- read-only function error cause — Error messages (including read-only call cause payloads) are now clamped to 4096 bytes at construction; Tuple and list values in error messages now render in Clarity syntax instead of internal debug format.
- SmartContract deploy payload — Versioned smart-contract deploys (VersionedSmartContract payload) are rejected as statically invalid from Epoch 4.1 onwards; deploy new contracts using the unversioned SmartContract payload, which uses the epoch's default Clarity version.
- Clarity 7 support — Epoch 4.1 introduces Clarity 7 as the default version; public or read-only functions may now take reserved names to implement trait methods from earlier Clarity versions that had those names free.

https://github.com/stacks-network/stacks-core/releases/tag/4.0.4
Sep 28, 20:26 UTC
[Urgent] Sui Testnet - Upgrade to testnet-v1.81.1
Completed - The scheduled maintenance has been completed.
Oct 8, 00:00 UTC
Scheduled - We are upgrading our Sui Testnet infrastructure to testnet-v1.81.1 on 2026-10-07. This release advances the Sui protocol to version 138, introducing memory invariant checks for PTB reference/value usage, enabling object funds withdrawal validation, and refining transaction effects and consensus handling. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
Transaction effects — On Testnet, transaction effects no longer report transaction dependencies. The effects encoding retains an empty dependency vector; object versions and per-object previous-transaction metadata are unchanged. This applies to gRPC methods that return effects, including GetTransaction, BatchGetTransactions, ExecuteTransaction, SimulateTransaction, and SubscribeCheckpoints.

https://github.com/MystenLabs/sui/releases/tag/testnet-v1.81.1
Oct 6, 18:59 UTC

Oct 7, 2026

Critical Tempo - Testnet - Upgrade to v1.16.0
Completed - The scheduled maintenance has been completed.
Oct 7, 23:59 UTC
Scheduled - We are upgrading our Tempo Testnet infrastructure to v1.16.0 on 2026-10-08. This release is required for the T12 network upgrade, which introduces configurable nonces for parallel expiring transactions, MPP sessions for closed-loop stablecoins, relaxed ABI validation, aligned DEX quote and swap calculations, and authorized burns for TIP-20 tokens. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
Native contract gas limits — Calls to native contracts must have more than 2,300 gas remaining before writing to storage; calls with insufficient gas will fail with an out-of-gas error. Integrations with hardcoded gas limits or explicit gas forwarding caps to native contracts must re-estimate on T12.
DEX tick liquidity storage — Stored tick liquidity totals stop updating after T12 activation. Integrations reading those totals directly from storage must switch to `getTickLevel` or sum remaining amounts of active orders; quote and swap APIs remain unchanged.
Expiring-nonce validation — Nonce validation behavior corrects error classification for expiring-nonce cases while keeping ordinary nonce overflow permanently invalid.

https://github.com/tempoxyz/tempo/releases/tag/v1.16.0
Oct 6, 14:13 UTC
[Standard] Hedera Mainnet - Upgrade JSON-RPC Relay to v0.79.0
Completed - The scheduled maintenance has been completed.
Oct 7, 23:59 UTC
Scheduled - We are upgrading our Hedera Mainnet JSON-RPC Relay infrastructure to v0.79.0 on 2026-10-07. This release introduces the Pectra network upgrade, adding support for EIP-7702 (type 4 "set code" transactions) and EIP-7623 (calldata cost accounting), along with accuracy improvements to fee estimation and contract calls, performance optimizations, and security hardening. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
- eth_call — Now uses blockhash instead of block number when querying the Mirror Node, eliminating ambiguity during chain reorgs or duplicate block heights.
- eth_feeHistory — baseFeePerGas is now computed as a gas-used-weighted average of block transaction prices, aligning responses with actual network costs; rewardPercentiles parameter is now validated and malformed arrays will return an error.
- eth_subscribe — logs filter now enforces a maximum address limit (default 1000) to prevent excessive query load.
- eth_sendRawTransaction — Type 4 (EIP-7702) transactions are rejected unless TX_TYPE_4_ENABLED is set to true; all transactions are subject to MAX_TRANSACTION_GAS_LIMIT (default 15000000).
- Nonce error responses — NONCE_TOO_LOW and NONCE_TOO_HIGH now both return error code -32000 instead of the previous non-standard codes 32001 and 32002.

https://github.com/hiero-ledger/hiero-json-rpc-relay/releases/tag/v0.79.0
Sep 30, 16:49 UTC
Aptos Testnet Scheduled State Reset
Resolved - This incident has been resolved.
Oct 7, 23:30 UTC
Investigating - The Aptos Foundation is beginning a scheduled state reset on Aptos Testnet at 17 UTC today, per AIP-147.

The reset returns Testnet to a fresh genesis and clears all prior on-chain state. The Aptos Foundation expects the process to take a few hours, with up to 48 hours possible if complications arise.

What this means for you: Once resync completes, previously deployed contracts, test accounts, and balances on Aptos Testnet no longer exist. You'll need to redeploy contracts and recreate test state against the new genesis.
Oct 7, 16:24 UTC
[Standard] Hyperliquid - Upgrade to nb-20261007
Completed - The scheduled maintenance has been completed.
Oct 7, 19:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 7, 16:30 UTC
Scheduled - We are upgrading our Hyperliquid Nanoreth node to nb-20261007. During the maintenance window, brief interruptions to RPC availability may occur. This release contains a bug fix for RPC compatibility.

## RPC Changes

**`eth_getLogs` — fixed**
Queries targeting future block ranges now return an 'invalid block range' error instead of an empty result, matching canonical hl-node behavior. Applications relying on empty responses for out-of-range queries will now receive an error instead.

---

https://github.com/hl-archive-node/nanoreth/releases/tag/nb-20261007
Oct 7, 16:24 UTC
Injective Mainnet – Block Height Stall
Resolved - Injective Mainnet has remained stable since block production resumed, and our nodes are fully synced and serving current data. This incident is now resolved. Thank you for your patience.
Oct 7, 13:24 UTC
Monitoring - Injective Mainnet has resumed block production and our nodes are advancing past block 186,223,485 again. Requests are returning current data and the block height stall is no longer occurring. We will continue to monitor the network to confirm stability.
Oct 7, 10:18 UTC
Identified - The Injective Foundation has confirmed the issue and will be publishing an upgrade guide shortly. Injective Mainnet remains stalled at block 186,223,485. We will apply the upgrade to our nodes as soon as it is available and share another update once the rollout is underway.
Oct 7, 08:51 UTC
Investigating - We are currently investigating a block height stall on Injective Mainnet. Nodes stopped advancing at block 186,223,485, and requests may return stale data until block production resumes. Our team is actively working on this and we will provide an update as soon as we have more information.
Oct 7, 08:39 UTC
X Layer Testnet – Network Stalled at Block 42837767
Resolved - This incident has been resolved.
Oct 7, 04:25 UTC
Monitoring - Service has been restored for X Layer Testnet, and requests are being served at the current chain head. Our engineers continue to work on the affected nodes and monitor stability.
Oct 6, 17:07 UTC
Identified - We have identified the cause of the X Layer Testnet network stall at block 42837767. Our engineers are currently upgrading our nodes to restore service. We will provide further updates as progress is made.
Oct 6, 16:59 UTC
Investigating - X Layer Testnet appears to have stalled at block 42837767 - The Quicknode team is investigating and will update with more information once it is available.
Oct 6, 15:27 UTC
[Standard] Polygon Mainnet - Upgrade Bor to v2.10.2
Completed - The scheduled maintenance has been completed.
Oct 7, 00:02 UTC
Scheduled - We are upgrading our Polygon Mainnet infrastructure to Bor v2.10.2 on 2026-10-06. This release brings WIT2 witness propagation, pipelined state root computation, sequence store and preconfirmation support, and p2p, sync, and RPC hardening fixes. No hardfork, no database schema change, or resync is required. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
- eth_sendRawTransactionForPreconf — New RPC method to submit transactions for preconfirmation (requires `[sequencer] enabled = true` to function).
- bor_getPreconfTransactionReceipt — New RPC method to retrieve receipts for preconfirmed transactions.
- bor_getInvalidPreconfBlocks — New RPC method to query invalid preconfirmation blocks.
- eth_sendRawTransactionSync — Now respects `rpc.txsync.maxconcurrent` configuration to cap concurrent calls waiting for a receipt (default 4096; 0 = no limit).

https://github.com/0xPolygon/bor/releases/tag/v2.10.2
Sep 30, 17:07 UTC
[Standard] Tempo Mainnet - Upgrade to v1.15.0
Completed - The scheduled maintenance has been completed.
Oct 7, 00:01 UTC
Scheduled - We are upgrading our Tempo Testnet & Mainnet infrastructure to v1.15.0 on 2026-10-06. This is a maintenance release focused on node reliability, sync stability, and performance.

Brief interruptions to RPC availability may occur on that date.

https://github.com/tempoxyz/tempo/releases/tag/v1.15.0
Sep 28, 20:21 UTC
[Urgent] Sei - pacific-1 - Upgrade to v6.7.0
Completed - The scheduled maintenance has been completed.
Oct 7, 00:01 UTC
Scheduled - We are upgrading our Sei pacific-1 infrastructure to seid v6.7.0 on 2026-10-06. This is a mandatory consensus-breaking hard fork that will activate at block 236450000.

Brief interruptions to RPC availability may occur on that date.

This release removes the IBC, capability, and feegrant modules entirely. It tightens pagination and request limits on several RPC and gRPC endpoints to protect against DoS attacks, and introduces a new LittDB-based block and receipt storage backend. Legacy sei_* and sei2_* JSON-RPC methods are removed in favor of standard eth_* methods, with only sei_getSeiAddress, sei_getEVMAddress, and sei_getCosmosTx remaining.

RPC Changes:
- sei_* and sei2_* legacy JSON-RPC methods — Removed entirely. Use standard eth_* methods instead.
- eth_estimateGasAfterCalls — Call count is now capped to prevent resource exhaustion.
- eth_getBlockReceipts — Fan-out and concurrent log subscriptions are capped for DoS protection.
- eth_createAccessList — Request limiter is now enforced.
- eth_getLogs — Peak memory is bounded by matched-log count and byte budgets; DB-read slots are released if a block read panics. The maxLog cap is applied during merge. Concurrent subscriptions are capped.
- eth_getProof — Removed; no longer supported.

https://github.com/sei-protocol/sei-chain/releases/tag/v6.7.0
Oct 5, 14:03 UTC
Urgent Arbitrum Mainnet - Upgrade to Nitro v3.12.1
Completed - The scheduled maintenance has been completed.
Oct 7, 00:00 UTC
Scheduled - We are upgrading our Arbitrum Mainnet infrastructure to Nitro v3.12.1 on 2026-10-06. This release introduces feed client REST backlog support, fixes crashes in debug trace and simulation methods on chains that collect tips, and changes Stylus contract activation behavior. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
debug_traceCall — Fixed crash that occurred on chains collecting tips; the method is now stable on all network configurations.
eth_simulateV1 — Fixed crash that occurred on chains collecting tips; simulation requests are now stable on all network configurations.

https://github.com/OffchainLabs/nitro/releases/tag/v3.12.1
Oct 5, 20:08 UTC

Oct 6, 2026

[Urgent] Starknet Mainnet - Upgrade to Pathfinder v0.24.1
Completed - The scheduled maintenance has been completed.
Oct 6, 23:59 UTC
Scheduled - We are upgrading our Starknet Mainnet infrastructure to Pathfinder v0.24.1 on 2026-10-05. This release includes upstream crate updates for stability and correctness.

Brief interruptions to RPC availability may occur on that date.

https://github.com/software-mansion/pathfinder/releases/tag/v0.24.1
Sep 29, 18:07 UTC

Oct 5, 2026

[Standard] World Chain Mainnet - Upgrade to v2.4.4
Completed - The scheduled maintenance has been completed.
Oct 5, 23:59 UTC
Scheduled - We are upgrading our World Chain Mainnet infrastructure to v2.4.4 on 2026-10-05. This release hardens proof validation, improves withdrawal processing, and adds operational enhancements to the fault-proof system and proof submission workflow. Brief interruptions to RPC availability may occur on that date.

https://github.com/worldcoin/world-chain/releases/tag/v2.4.4
Sep 28, 20:17 UTC
[Urgent] Zcash Testnet - Upgrade to Zebra 7.0.0-rc.0
Completed - The scheduled maintenance has been completed.
Oct 5, 23:59 UTC
Scheduled - We are upgrading our Zcash Testnet infrastructure to Zebra 7.0.0-rc.0 on 2026-10-05. This release candidate activates the NU7 network upgrade on Testnet at height 4,465,026, introducing ZIP 259 branch IDs, ZIP 218 difficulty and action-limit changes, and the ZIP 237 NSM value pool. The upgrade includes significant RPC behavior changes affecting miners and applications. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
- getblocktemplate — The advertised mutable list now contains only time; transactions and prevblock have been removed. Miners must request a new template rather than modifying transactions or parent block independently. The coinbaserxn.fee field now reports negative collected miner fees (excluding NSM contribution from NU7 onward), and the depends array reports each parent transaction once using 1-based position.
- getnetworksolps — Now returns an RPC error instead of panicking when the estimated solution rate exceeds its supported integer range. The method selects the 17- or 102-block averaging window for nonpositive block counts using the effective height in the same state snapshot, including requests above the current tip.
- getstandardfee — On Mainnet reports 5000 zatoshis per logical action until height 3,590,000, then 1000 from that height onward. Test networks report 1000 at every height.
getblocksubsidy — Now rejects heights above the consensus limit before reading state or computing subsidy.

https://github.com/ZcashFoundation/zebra/releases/tag/v7.0.0-rc.0
Oct 2, 15:04 UTC
Scheduled — Solana Testnet client upgrade (Agave v4.4.0-beta.0)
Completed - The scheduled maintenance has been completed.
Oct 5, 07:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 5, 02:30 UTC
Scheduled - Starting 2026-10-05 (UTC) we are upgrading our Solana Testnet RPC fleet to Agave v4.4.0-beta.0, the version the Solana Foundation now requires on Testnet. Nodes restart one at a time; RPC and WebSocket endpoints stay available throughout.

What changes for Testnet clients:

getLeaderSchedule called with an identity that has no slots in the epoch now returns JSON-RPC error -32022 ("Node was not in the leader schedule for specified epoch") instead of an empty result. A new keyByVoteAccount option returns the schedule keyed by vote account.

getSignatureStatuses now honours commitment in its config. A transaction below the requested commitment comes back as null. Without commitment, the default stays processed.

getSignatureStatuses and getTransaction now honour minContextSlot. They return JSON-RPC error -32016 ("Minimum context slot has not been reached") when the node has not reached that slot.

accountSubscribe and programSubscribe now apply dataSlice to base58 and base64 account data, and a zero-length slice returns empty data. Omit dataSlice to keep receiving the full account data.
Oct 5, 02:08 UTC

Oct 4, 2026

Scheduled — Solana Mainnet client upgrade (Agave v4.3.0)
Completed - The scheduled maintenance has been completed.
Oct 4, 00:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 29, 00:00 UTC
Scheduled - Starting 2026-09-29 (UTC), we are upgrading our Solana Mainnet fleet to Agave v4.3.0, the release Anza recommends for Mainnet-beta, together with the matching Yellowstone gRPC (v16) and Blazar builds. RPC, WebSocket and gRPC endpoints stay available throughout. Our staked validators are already on v4.3.0.

What changes for Mainnet clients:

- getBlock, getTransaction and blockSubscribe now reject requests that combine encoding: "base58" (or "binary") with maxSupportedTransactionVersion >= 1, returning JSON-RPC error -32602 "base58 encoding is not supported with maxSupportedTransactionVersion>= 1". Use json, jsonParsed or base64 encoding for Transaction V1 requests.

- getInflationReward now accepts at most 32 addresses per request; larger lists return JSON-RPC error -32602 "Too many inputs provided; max 32". Split larger requests into batches of 32.

- Yellowstone gRPC moves to the v16 line. Existing subscriptions keep working unchanged, including clients built from the v15 proto. The v16 additions (a bank_id field on updates, a block_footer subscription) are optional and inert on Mainnet until Alpenglow activates; regenerate your app from the v16 proto only if you want them.

No JSON-RPC method is added or removed.

Please reach out to our Support team if you are experiencing any issues during the maintenance window.
- https://quicknode.portal.usepylon.com/forms/submit-a-support-ticket
Sep 23, 23:10 UTC

Oct 3, 2026

TON Mainnet Degraded Performance
Resolved - Since September 23, many nodes that don't forward traffic have joined TON's public overlay, the peer network our nodes use to receive blocks and pass on transactions. Because our nodes were connected to some of these peers, block sync slowed and some transactions were not delivered.

For more detail, see the TON Foundation's announcement: https://t.me/tonstatus/244
Oct 3, 00:29 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Oct 2, 19:41 UTC
Update - We are continuing to work on a fix for this issue.
Oct 2, 00:52 UTC
Identified - The issue has been identified and working with the Ton Foundation to implement fixes.
Oct 1, 21:46 UTC
Investigating - The Quicknode team is investigating degraded performance of TON Mainnet - we will update this page as we acquire new information.
Oct 1, 19:37 UTC

Oct 2, 2026

[Standard] 0g - Mainnet - Upgrade to v1.0.7
Completed - The scheduled maintenance has been completed.
Oct 2, 00:00 UTC
Scheduled - We are upgrading our 0g Mainnet infrastructure to Aristotle v1.0.7 on 2026-10-01. This is an RPC-only release that fixes a critical correctness bug in eth_estimateGas and removes a CPU-amplification vector in the gas estimator. No consensus or state-transition changes are included. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
- eth_estimateGas — Fixed critical bug where gas estimates were being seeded from post-settlement gas (raising gas_used to 80% of the cap), causing the method to return cap-sized limits instead of actual usage. This resulted in gas estimates up to ~850× too large. Estimates are now seeded from pre-settlement gas, matching 0g-geth behavior. Additionally, EIP-7623 calldata floor computation has been optimized to run once per transaction instead of per frame, eliminating a CPU-amplification vector.

https://github.com/0gfoundation/0gchain-Aristotle/releases/tag/v1.0.7
Sep 24, 16:34 UTC
Incident History Powered by Atlassian Statuspage