We are upgrading our Aptos Mainnet infrastructure to v1.45.5 and our Aptos Testnet infrastructure to v1.46.1-rc.
The Mainnet patch includes a consensus fix to skip signing round 0 ledger info and a VM fix making MoveTypeLayout trait implementations DAG-safe.
The Testnet release candidate includes consensus and mempool improvements, BlockSTM v2 enablement on validators, storage updates (hot state promotions persisted in epilogue, KV/tree sequencing fixes), VM and compiler updates, encrypted transaction handling improvements, network peer dialing and latency pinging improvements, security fixes including iterative drop for nested Move values and PROXY protocol length-based allocation hardening, and various performance optimizations across mono-move runtime work.
During the maintenance window, customers may experience intermittent disruptions to RPC availability as nodes are rotated through the upgrade process.
RPC Changes: No customer-facing RPC changes in these releases.
We are upgrading our NEAR Mainnet infrastructure to nearcore v2.12.0.
This is a mandatory protocol upgrade from version 83 to 84. Voting begins June 10, 2026 at 00:00 UTC, and nodes must be upgraded before this time to remain in sync with the network. If voting succeeds within one epoch, the protocol upgrade is expected to take effect 7–14 hours after the voting epoch ends.
During the maintenance window, brief interruptions to RPC availability may occur.
RPC Changes:
EXPERIMENTAL_receipt_to_tx — new method that resolves a receipt ID back to the originating transaction hash and sender account. Note: requires save_receipt_to_tx config and all-shards tracking to be enabled on the node
We are upgrading our Polkadot Mainnet infrastructure from stable2603-1 (v1.22.1) to stable2603-3 (v1.22.3).
This patch jump includes new peerset notification metrics, a Snowbridge default asset claimer fix on AssetHub, a Revive gas estimation improvement using binary search for tighter eth_estimateGas results, and a runtime API version check improvement for bulletin chain compatibility.
During the maintenance window, customers may experience intermittent disruptions to RPC availability as nodes are rotated through the upgrade process.
RPC Changes: eth_estimateGas (Revive / Polkadot EVM) — gas estimation now uses binary search to find the smallest gas limit at which a transaction would succeed, producing tighter estimates closer to actual gas usage. Customers who previously received conservative over-estimates may see lower returned values.
We are upgrading our Celo Mainnet op-geth infrastructure to celo-v2.2.4.
This is a recommended bug fix release containing two targeted changes: the native MultiGasPool now correctly charges actual gas used (rather than gas limit) for forced deposits, and batch header verification is hardened against invalid parents. No fork activation or protocol changes are introduced. The release is paired with op-node celo-v2.2.1.
During the maintenance window, customers may experience intermittent disruptions to RPC availability as nodes are rotated through the upgrade process.
RPC Changes: No customer-facing RPC changes in this release.
We are upgrading our Tron Mainnet infrastructure to GreatVoyage-v4.8.1.1 (Hypatia).
This is a mandatory upgrade that optimizes the execution logic of the CREATE2 operation and the ModExp precompiled contract in edge cases.
During the maintenance window, customers may experience intermittent disruptions to RPC availability as nodes are rotated through the upgrade process.
RPC Changes: TVM CREATE2 — execution logic for edge cases has been optimized. Users calling contracts that exercise CREATE2 at deep call stacks may see different execution outcomes for affected transactions after the fork activates. TVM ModExp precompile — execution logic for edge cases has been optimized. Users calling contracts that use modular exponentiation with specific input shapes may see different execution outcomes after the fork activates.
We are upgrading our Gnosis Mainnet Nethermind infrastructure to v1.38.0. This is a post-Fusaka (Osaka) maintenance release focused on node robustness, JSON-RPC correctness, and runtime performance improvements.
During the maintenance window, brief interruptions to RPC availability may occur.
eth_call / eth_estimateGas — now correctly honors the gas cap as the default gas value; the block gas limit ceiling no longer applies to RPC calls. Custom revert bytes are also stripped from the message field for cleaner error responses
eth_feeHistory — correctness fixes to response data
trace_transaction / trace_replayTransaction — fixed HTTP 500 errors being returned incorrectly
eth_getBlockByNumber("pending") — now correctly returns non-null values for hash, nonce, and miner fields
The Cosmos Network is upgrading to gaia v27.4.0. Voting concludes on June 9 at ~9 UTC, and the upgrade is expected to activate shortly after. A brief chain halt is expected at the upgrade height while validators coordinate the transition, during which RPC availability will be interrupted. Normal service is expected to resume shortly after.
No user-facing RPC changes are included in this release.
We are upgrading our Ethereum Mainnet Nethermind infrastructure to v1.38.0. This release brings a broad set of improvements to node robustness, JSON-RPC correctness, and runtime performance.
During the maintenance window, brief interruptions to RPC availability may occur.
RPC Changes:
txpool_content / txpool_contentFrom / txpool_status — corrected response formatting and hex encoding inconsistencies eth_call / eth_estimateGas — now correctly honors the gas cap as the default gas value; the block gas limit ceiling no longer applies to RPC calls. Custom revert bytes are also stripped from the message field for cleaner error responses eth_feeHistory — correctness fixes to response data trace_transaction / trace_replayTransaction — fixed HTTP 500 errors being returned incorrectly eth_getBlockByNumber("pending") — now correctly returns non-null values for hash, nonce, and miner fields eth_simulateV1 — corrected error codes and messages for fee cap violations, insufficient funds, and intrinsic gas errors for improved compatibility
We are upgrading our Arbitrum stack infrastructure to Nitro v3.10.2. This upgrade includes support for the upcoming ArbOS 60 activation and general improvements to node stability. During the maintenance window, brief interruptions to RPC availability may occur.
No user-facing RPC changes are included in this release.
We are upgrading our Ethereum (Mainnet and Testnets) Erigon infrastructure to v3.4.3.
This is a recommended bugfix release addressing a post-reorg state inconsistency that could cause gas used mismatches, as well as an internal fix that was also present in v3.4.2 but incompletely resolved.
During the maintenance window, brief interruptions to RPC availability may occur.
RPC Changes:
debug_getModifiedAccountsByHash / debug_getModifiedAccountsByNumber — These methods now match Geth semantics: the block range uses an exclusive start boundary, contracts whose storage changed (without an account-level change) are now correctly included, and touched-but-unchanged precompiles and self-destructed accounts are excluded. Results may differ from prior Erigon versions.
Resolved -
This incident has been resolved.
Jun 6, 00:41 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jun 5, 23:16 UTC
Identified -
The issue has been identified and our engineering team is applying a fix.
Jun 5, 20:08 UTC
Investigating -
The Quicknode team is investigating degraded performance on Polygon Amoy archive nodes — we will update this page as we acquire new information.
Jun 5, 14:33 UTC
Resolved -
This incident has been resolved.
Jun 5, 16:42 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jun 5, 14:45 UTC
Investigating -
The Quicknode team is investigating degraded performance and elevated latency affecting debug_trace* and tracing requests across multiple networks in the FRA region. We will update this page as we acquire new information.
Jun 5, 14:14 UTC
Completed -
The scheduled maintenance has been completed.
Jun 5, 05:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 5, 01:01 UTC
Scheduled -
We are upgrading our Sui Testnet infrastructure to testnet-v1.73.1, bringing protocol version 126.
This release includes protocol-level changes to how insufficient funds for withdrawals are handled, along with improvements to GraphQL and node stability.
During the maintenance window, brief interruptions to RPC availability may occur.
RPC Changes:
GraphQL: checkpoint lookup by digest is now supported
GraphQL: new asTransactionObject field allowing queries on the status of an address involved as an object in a particular transaction
Completed -
The scheduled maintenance has been completed.
Jun 5, 05:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 5, 01:00 UTC
Scheduled -
We are upgrading our Monad Testnet infrastructure to monad-bft v0.14.5. This release includes improvements to RPC performance, correctness fixes, and node robustness enhancements. During the maintenance window, brief interruptions to RPC availability may occur.
RPC Changes:
eth_sendRawTransactionSync — now event-driven, returning transaction receipts immediately instead of polling. Response times are approximately 50ms faster
eth_createAccessList — fixed an issue where the access list was not returned when the call reverts
Resolved -
This incident has been resolved.
Jun 5, 02:13 UTC
Update -
We have identified the root cause of the degraded performance affecting Plasma Mainnet in the JFK region and node recovery is in progress.
As a temporary mitigation, traffic has been rerouted to nearby region while our engineers are working to recover the nodes. Some users may notice elevated latency at this time. We will continue to provide any new updates.
Jun 4, 23:00 UTC
Identified -
We have identified the root cause of the degraded performance affecting Plasma Mainnet in the JFK region. Our engineers are actively working to restore the affected nodes.
Jun 4, 21:34 UTC
Investigating -
The QuickNode team is investigating degraded performance of Plasma Mainnet nodes in the JFK region - we will update this page as we acquire new information.
Jun 4, 19:33 UTC
Completed -
The scheduled maintenance has been completed.
Jun 4, 21:30 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 4, 19:30 UTC
Scheduled -
We will be performing maintenance on our Hypercore gRPC + JSON-RPC products at this time. It will be a slow rolling upgrade, but please reach out if you have any additional questions
Jun 4, 19:21 UTC
Completed -
The scheduled maintenance has been completed.
Jun 4, 21:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 4, 13:00 UTC
Scheduled -
Injective Mainnet is undergoing the Vulcan canonical chain upgrade to v1.20.0, scheduled to activate at block height 169,334,500 (approximately 14:00 UTC / 10:00 ET on June 4, 2026). Our infrastructure will pick up the new binary automatically via Cosmovisor at the on-chain upgrade height.
During the upgrade window, customers may experience brief disruptions to RPC availability as nodes transition through the upgrade.
Resolved -
The issue with the HyperEVM Testnet archive nodes stalling at block 55,231,856 has been resolved. A patch (nb-20260604) has been applied to the affected nodes and block height is advancing normally. We will continue to monitor for stability.
Jun 4, 10:36 UTC
Investigating -
The HyperEVM Testnet (archive) appears to have stalled at block 55,231,856 - The QuickNode team is investigating and will update with more information once it is available.
Jun 3, 13:08 UTC
Resolved -
This incident has been resolved.
Jun 4, 06:14 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jun 4, 04:15 UTC
Investigating -
We are aware of elevated API errors and 503 errors on Polygon Amoy. The Quicknode team is actively investigating. We will provide updates as this progresses.
Jun 3, 23:57 UTC
Monitoring -
The Polygon Amoy nodes are recovering following the network stress test. We are monitoring for stability.
Jun 3, 20:52 UTC
Investigating -
We are aware of elevated API errors and 503 errors on Polygon Amoy. The Polygon Foundation is currently conducting a network stress test which may be contributing to degraded performance. We will provide updates as this progresses.
Jun 3, 18:12 UTC
Resolved -
This incident has been resolved.
Jun 3, 20:56 UTC
Update -
Block height is progressing across the node infrastructure. We will notify you once the nodes are in sync with the broader network.
Jun 3, 04:15 UTC
Identified -
The issue has been identified and a fix is being implemented.
Jun 2, 23:00 UTC
Investigating -
Robinhood Testnet appears to have stalled at block 63,024,491 - Our team is investigating and we are working with the foundation to resolve the stall. We will update with more information once it is available.
Jun 2, 16:15 UTC
Resolved -
This incident has been resolved.
Jun 3, 20:22 UTC
Monitoring -
A fix has been applied and we are monitoring the service for stability.
Jun 3, 18:56 UTC
Identified -
We have identified the issue affecting Starknet Mainnet performance. Our team is working closely with the Starknet Foundation to resolve the issue. We will continue to provide updates as the situation progresses.
Jun 3, 16:54 UTC
Investigating -
The QuickNode team is investigating the degraded performance of Starknet Mainnet - Users may experience elevated 503 errors and increased latency. We will update this page as we acquire new information.
Jun 3, 15:23 UTC
Completed -
The scheduled maintenance has been completed.
Jun 3, 05:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 3, 01:00 UTC
Scheduled -
We are upgrading our Celestia Mocha Testnet infrastructure to celestia-app v9.0.1-mocha and celestia-node v0.31.0-mocha.
This is a consensus-breaking v9 release that reduces block time from 6 seconds to 3 seconds. Activation occurs after 5/6 voting power has signaled for v9. The release also speeds up block sync by defaulting verify_data to false, honors min-retain-blocks below the evidence window, and deprecates the celestia-appd update-config command.
During the maintenance window, users may experience intermittent disruptions to RPC availability as nodes are rotated through the upgrade process.
RPC Changes: Block time — produced blocks now arrive at ~3 second cadence instead of ~6 seconds after v9 activates on the Mocha network. Users polling for new blocks may want to adjust polling intervals; subscription-based consumers will receive blocks at the higher rate without code changes.
Resolved -
This incident has been resolved.
Jun 3, 00:22 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jun 2, 21:59 UTC
Identified -
The issue has been identified and a fix is being implemented.
Jun 2, 21:19 UTC
Investigating -
The QuickNode team is investigating instability on the Solana Testnet. We will update this page as we acquire new information.
Jun 2, 18:13 UTC
Resolved -
This incident has been resolved.
Jun 2, 23:37 UTC
Identified -
The issue has been identified and a fix is being implemented.
Jun 2, 22:52 UTC
Investigating -
The Berachain Bepolia network appears to have stalled at block 20,782,375. The QuickNode team is investigating and will update with more information once it is available.
Jun 2, 21:55 UTC
Completed -
The scheduled maintenance has been completed.
Jun 2, 18:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 2, 13:00 UTC
Scheduled -
We will be performing scheduled maintenance on Optimism Sepolia as part of our migration to the op-reth client. During this window, Sepolia endpoints may be temporarily unavailable or experience degraded performance.
Scheduled: 2026-06-02 at 13:00 UTC, estimated duration: 5 hours.
Jun 1, 15:29 UTC
Completed -
Maintenance has been completed.
Jun 2, 13:05 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 2, 07:30 UTC
Scheduled -
We are upgrading our MegaETH Mainnet infrastructure to v2.0.21 ahead of the mandatory Rex5 hardfork.
The hardfork changes execution semantics. This release also upgrades MegaEVM to v1.5.3, adds a sequencer signature in mini-blocks, and improves WebSocket connection observability.
During the maintenance window, customers may experience intermittent disruptions to RPC availability as nodes are rotated through the upgrade process.
RPC Changes:
Mini-block format — sequencer signature has been added; clients consuming raw mini-block data may need to account for the new field.
WebSocket — observability improvements have been added to WebSocket connections; no functional behavior change for client integrations.
Completed -
The scheduled maintenance has been completed.
Jun 2, 05:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 2, 01:00 UTC
Scheduled -
We are upgrading our TON Mainnet infrastructure to v2026.05.
This release includes networking improvements (block candidates sent over a dedicated block-sync overlay), collation, validation, and block-application performance optimizations for validators and liteservers, TVM v14, and the removal of legacy code (catchain, adnl-proxy, rldp1).
During the maintenance window, customers may experience intermittent disruptions to RPC availability as nodes are rotated through the upgrade process.
RPC Changes: get_shard_client_state — new liteserver method added, exposing shard client state to clients.
Completed -
The scheduled maintenance has been completed.
Jun 2, 04:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 2, 00:00 UTC
Scheduled -
We are upgrading our Tempo Mainnet and Moderato Testnet infrastructure to v1.8.1. This release is required for the T5 network upgrade scheduled for both testnet and mainnet.
Activation schedule • Testnet: June 3rd, 4pm CEST (unix timestamp: 1780495200) • Mainnet: June 9th, 4pm CEST (unix timestamp: 1781013600)
During the maintenance window, customers may experience intermittent disruptions to RPC availability as nodes are rotated through the upgrade process.
RPC Changes: No customer-facing RPC changes in this release.
Completed -
The scheduled maintenance has been completed.
Jun 2, 03:52 UTC
Verifying -
Verification is currently underway for the maintenance items.
Jun 2, 03:30 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 2, 03:20 UTC
Scheduled -
Our engineers performed scheduled maintenance on Polkadot Mainnet Archive nodes in the US-East region. Services have been restored and are operating normally.
Jun 2, 03:15 UTC
Resolved -
The Hemi Mainnet network stall at block 4538215 has been resolved. The Hemi Foundation identified and deployed a fix, and the network is now advancing normally. All Hemi Mainnet services are fully operational.
Jun 1, 18:58 UTC
Identified -
The Hemi Foundation has identified a fix for the network stall at block 4538215. Our team is monitoring the situation as the fix is being applied. We will provide further updates as the network recovers.
Jun 1, 16:56 UTC
Investigating -
The Hemi Mainnet network appears to have stalled at block 4538215. This is a chain-wide issue and is not specific to QuickNode. Our team has raised this with the Hemi Foundation and will provide updates as more information becomes available.
Jun 1, 15:14 UTC
Completed -
The scheduled maintenance has been completed.
Jun 1, 12:35 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 1, 04:35 UTC
Scheduled -
We are currently performing maintenance on our Ethereum Hoodi Testnet archive nodes. Some nodes are being resynced. During this time, users may experience intermittent 503 responses or degraded availability.
Jun 1, 04:30 UTC
Completed -
The scheduled maintenance has been completed.
Jun 1, 08:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 1, 03:00 UTC
Scheduled -
We are upgrading our zkSync Mainnet and Testnet infra to v29.19.0. During the maintenance window, brief interruptions to RPC availability may occur. This release includes a bug fix for call trace data and prover enhancements.
## RPC Changes
**`debug_traceBlockByNumber` — fixed** Call traces were missing from block trace results. This fix ensures complete trace data is now returned for all transactions in traced blocks.
Completed -
The scheduled maintenance has been completed.
Jun 1, 07:15 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 31, 23:15 UTC
Scheduled -
We are upgrading our Story Mainnet infra to v1.8.0 (Seneca). During the maintenance window, brief interruptions to RPC availability may occur. This release implements a consensus change that reduces the active validator set from 80 to 21 validators and has no user-facing RPC changes. Operators must upgrade to v1.8.0 before block 18173000 ---
Completed -
The scheduled maintenance has been completed.
Jun 1, 05:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 1, 01:00 UTC
Scheduled -
We are upgrading our Hedera JSON-RPC Relay infrastructure from v0.76.2 to v0.77.0. This is a significant release with multiple breaking changes to default behavior, performance and reliability improvements, and EVM compatibility fixes.
During the maintenance window, customers may experience intermittent disruptions to RPC availability as nodes are rotated through the upgrade process.
RPC Changes:
eth_getBalance and other balance-returning methods — return values are now denominated in weibar instead of HBAR, aligning with Mirror Node. Applications that expected HBAR-denominated values will need to be updated.
eth_sendRawTransaction — now waits for full transaction confirmation before returning instead of returning the transaction hash immediately. Clients that rely on hash-and-go submission will see increased response latency on this method.
eth_subscribe — WebSocket subscriptions are now enabled by default. eth_feeHistory — the gasUsedRatio field is now populated in responses, improving EIP-1559 fee estimation compatibility.
WebSocket parity — all HTTP JSON-RPC methods are now available over WebSocket connections.
Concurrent submissions — a two-lock nonce sequencing mechanism resolves a race condition affecting concurrent eth_sendRawTransaction calls.
debug_traceTransaction — fixed a bug where the to field could incorrectly appear as null for contract creation transactions.
Investigating -
Sui Mainnet stopped accepting user transactions due to an issue during the epoch change beginning at ~1:30PT. Validators are up and creating system transactions, but user transactions are not currently being accepted. This is a network-wide incident announced by the Sui Core Team. We are monitoring for any changes and our engineering team will promptly act on any updates.
May 29, 21:38 UTC
Completed -
The scheduled maintenance has been completed.
May 30, 00:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 25, 21:01 UTC
Scheduled -
We will be upgrading our Solana nodes on Mainnet to v4.0 on May 26th and the upgrade is expected to last 4 days.
No downtime is expected, but customers may experience brief connection interruptions, temporary latency increase, and a small number of HTTP 503 responses as services restart and resynchronize with the cluster.
As part of the upgrade, we deliver XDP (eXpress Data Path) in Agave staked validator.
Those are RPC changes (they are already live on Devnet and Testnet): New response fields (additive, backward-compatible): • getClusterNodes — new optional client_id field identifying client software • getSignaturesForAddress — new optional transaction_index field • simulateTransaction — new loadedAccountsDataSize and replacementBlockhash fields • Block reward data — new optional commission_bps (basis points). Once the commission_rate_in_basis_points feature activates on-chain, the existing commission field will return null and commission_bps will be populated instead. If you read commission in reward data, plan to migrate to commission_bps.
Breaking changes — action may be required: • getClusterNodes — tpu and tpuForwards fields now always return null. UDP TPU addresses are no longer advertised. Use tpuQuic / tpuForwardsQuic instead. Any customer using getClusterNodes to discover TPU endpoints for direct transaction sending via UDP will get null.
May 19, 21:35 UTC
Resolved -
This incident has been resolved.
May 29, 18:33 UTC
Monitoring -
The network stall has been addressed. We are monitoring Sui Mainnet for stability following the emergency release (mainnet-v1.72.4). We will continue to update this page as we confirm full recovery.
May 29, 16:36 UTC
Update -
We are investigating 503 errors on Sui Mainnet following a network stall. The Sui Network team has issued an emergency release (mainnet-v1.72.4) and we are actively monitoring the situation. We will provide updates as more information becomes available.
May 29, 16:03 UTC
Investigating -
The Sui Mainnet appears to have stalled at block 280,912,461 - The QuickNode team is investigating and will update with more information once it is available.
May 29, 12:22 UTC
Completed -
The scheduled maintenance has been completed.
May 29, 11:00 UTC
Verifying -
Verification is currently underway for the maintenance items.
May 28, 15:11 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 28, 11:00 UTC
Scheduled -
We will perform an urgent upgrade of Base Mainnet and Sepolia node-reth infrastructure to v0.16.1 today at 11:00 UTC.
This release is required for pruned node operators and updates the base-consensus and base-reth-node dependencies to v0.9.1.
No downtime is expected, but customers may experience brief connection interruptions and a small number of HTTP 503 responses as services restart and resynchronize with the network.
Resolved -
This incident has been resolved.
May 29, 01:47 UTC
Investigating -
Flow Testnet is currently experiencing a network-wide stall at block height 112,873,473. We will provide updates as soon as they become available.
Completed -
The scheduled maintenance has been completed.
May 28, 23:10 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 28, 22:00 UTC
Scheduled -
We are upgrading our Sui mainnet infrastructure to v1.72.3. During the maintenance window, brief interruptions to RPC availability may occur. This release advances the protocol to version 125 and includes enhancements to GraphQL API functionality.
## RPC Changes
**GraphQL checkpoint queries — added** Checkpoints can now be queried by digest in addition to existing lookup methods, enabling more flexible checkpoint retrieval.
**GraphQL transaction object status — added** Queries for transaction object status are now available via GraphQL, providing better visibility into object state changes.
Resolved -
This incident has been resolved.
May 28, 23:07 UTC
Update -
Our engineers are updating nodes to the recent 1.72.3 release. Users may begin to see 503s mitigated and we will mark the incident as resolved once stability at tip has been confirmed.
May 28, 22:29 UTC
Identified -
The Sui Foundation has acknowledged the issue and is actively working on a fix. We will continue to provide updates as more information becomes available.
May 28, 16:01 UTC
Investigating -
The Sui Mainnet network appears to have stalled at block 280,692,037. The QuickNode team is investigating and has raised the issue with the Sui Foundation. We will update this page as more information becomes available.
May 28, 14:15 UTC
Completed -
The scheduled maintenance has been completed.
May 28, 10:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 27, 10:00 UTC
Scheduled -
We will perform an urgent upgrade of the Polygon Bor client to v2.8.1 across Polygon Mainnet and Polygon Amoy today at 10:00 UTC. The previous deployed version was v2.8.0.
This release includes important stability and security-related fixes for Bor node operators.
No downtime is expected, but customers may experience brief connection interruptions and a small number of HTTP 503 responses as services restart and resynchronize with the network.
Completed -
The scheduled maintenance has been completed.
May 28, 06:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 28, 01:00 UTC
Scheduled -
We are upgrading our Aptos Mainnet infrastructure to v1.45.4.
This is a major version release that includes consensus and mempool hardening, storage improvements (hot state pruning, restart recovery, KV/tree sequencing fixes), VM and compiler updates, encrypted transaction security and DoS protections, DKG stall recovery, gas metering changes, network peering improvements, and a security fix for iterative drop on nested Move values.
During the maintenance window, customers may experience intermittent disruptions to RPC availability as nodes are rotated through the upgrade process.
RPC Changes: No customer-facing RPC changes in this release.
Resolved -
This incident has been resolved.
May 27, 18:14 UTC
Monitoring -
We have brought additional nodes online and are monitoring the situation. Performance is improving, though we have not yet reached full capacity. We will continue to provide updates as the situation develops.
May 27, 14:54 UTC
Investigating -
The QuickNode team is investigating the degraded performance of Polygon Mainnet (Matic) archive nodes - we will update this page as we acquire new information.
May 27, 13:35 UTC
Completed -
The scheduled maintenance has been completed.
May 27, 09:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 27, 01:00 UTC
Scheduled -
We are upgrading our zkSync-stack chains to Core v29.17.0. During the maintenance window, brief interruptions to RPC availability may occur. This release prepares for the upcoming v31 protocol upgrade and includes bug fixes and verifier improvements.
Completed -
The scheduled maintenance has been completed.
May 27, 06:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 26, 22:00 UTC
Scheduled -
We are upgrading our Sui Testnet infra to testnet-v1.73.0. During the maintenance window, brief interruptions to RPC availability may occur. This release advances the protocol to version 125 and introduces changes to epoch advancement logic.
May 26, 21:18 UTC
Completed -
The scheduled maintenance has been completed.
May 27, 00:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 26, 12:00 UTC
Scheduled -
Following guidance from the Foundation to ensure all operators are running the latest supported software versions, we will perform an urgent upgrade of Stacks Mainnet stacks-node from v3.4.0.0.0 to v3.4.0.0.2 today at 12:00 UTC.
Current deployed versions:
* Stacks Node: v3.4.0.0.0 → v3.4.0.0.2
This release contains important stability and maintenance fixes for node operators.
No downtime is expected, but brief REST API or WebSocket interruptions may occur as services restart and resynchronize with the network.
Resolved -
This incident has been resolved.
May 26, 22:40 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
May 26, 22:15 UTC
Investigating -
Unichain Sepolia archive and flashblocks endpoints are currently experiencing degraded performance. Users may experience 503s during this time. We are actively investigating the issue and will provide an update as soon as possible.
May 26, 21:44 UTC
Completed -
The scheduled maintenance has been completed.
May 26, 10:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 26, 08:00 UTC
Scheduled -
We are performing a mandatory protocol upgrade on our NEAR Testnet infrastructure to neard 2.12.0-rc.1, required by the NEAR core team before June 1, 2026.
During this maintenance window, NEAR Testnet nodes will be upgraded in a rolling manner. Connection may experience brief request latency or intermittent connection resets as individual nodes are restarted. Service availability is maintained throughout the upgrade.
May 26, 07:46 UTC
Completed -
The scheduled maintenance has been completed.
May 26, 07:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 25, 07:00 UTC
Scheduled -
We are upgrading our Base Mainnet infrastructure to support the Base Azul network upgrade. All Base Mainnet nodes must be upgraded by May 28th; nodes not upgraded by this deadline will be incompatible with the network. This release drops support for all execution clients except base-reth-node and base-consensus. Operators running other clients must migrate before the deadline.
This release contains breaking changes and protocol updates required for network compatibility.
Completed -
The scheduled maintenance has been completed.
May 25, 07:01 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 24, 23:00 UTC
Scheduled -
We are upgrading our Sei Mainnet nodes to v6.5.1. During the maintenance window, brief interruptions to RPC availability may occur. This release is a targeted patch that restores debug_trace* RPC calls against blocks produced before the v6.5 upgrade, which were failing to decode under the new tx codec path.
Completed -
The scheduled maintenance has been completed.
May 25, 04:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 25, 00:00 UTC
Scheduled -
We are upgrading our Arc Testnet infrastructure to v0.7.1 ahead of the Zero5/Zero6 hardfork activation, scheduled for May 27, 2026 15:08:37 UTC (timestamp 1779894517).
This release also tightens default EL RPC connection limits and includes fixes for CREATE2 initCode hashing and fork-id compatibility across mixed-version peers. During the maintenance window, customers may experience intermittent disruptions to RPC availability as nodes are rotated through the upgrade process.
Resolved -
This incident has been resolved.
May 24, 02:55 UTC
Monitoring -
Some nodes have recovered, and 503s have been mitigated. Quicknode teams are continuing to work to recover full capacity and monitor performance to ensure stability.
May 24, 02:45 UTC
Investigating -
We are investigating intermittent 503 errors affecting the Abstract Testnet. Some customers may experience temporary request failures or degraded performance.
Our team is actively working to mitigate the issue and will provide an update as more information becomes available.
May 24, 02:30 UTC
Resolved -
This incident has been resolved.
May 23, 20:46 UTC
Investigating -
Blast Sepolia appears to have stalled. The Quicknode team is investigating and will update this page as more information becomes available.
May 23, 20:45 UTC
Resolved -
The incident has been resolved. The Billing Dashboard Metrics are now operating normally. We will continue to monitor the situation and apologize for any inconvenience caused.
May 23, 20:31 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
May 23, 19:20 UTC
Investigating -
We are investigating an issue causing billing metrics on the dashboard to appear delayed. We will provide updates as more information becomes available.
May 23, 15:57 UTC