Update - We've identified an issue in the latest Polygon client release where the finalized block height is stuck, even as the latest block height continues to advance. We're currently working on next steps to mitigate the problem.
Jul 03, 2025 - 20:38 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 03, 2025 - 19:01 UTC
Update - We will be undergoing scheduled maintenance during this time.
Jul 3, 202519:00 - Jul 4, 202519:00 UTC
Scheduled - Team upgrading to Bor v2.2.4 and Heimdall v1.6.0 to address Bhilai Hard Fork issues and prepare for the upcoming Heimdall v2 migration. No downtime expected over maintenance window.
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 03, 2025 - 15:01 UTC
Scheduled - Solana Devnet will undergo scheduled maintenance on July 3, 2025, at 15:00 UTC as part of a coordinated halt and restart drill led by the validator team. This is a planned disruption to simulate cluster recovery procedures. During this time, users may experience delayed data and 503 errors.
Jul 3, 202515:00 - Jul 6, 202515:00 UTC
Completed -
The scheduled maintenance has been completed.
Jul 3, 20:59 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 2, 15:00 UTC
Scheduled -
Solana Testnet will undergo scheduled maintenance on July 2, 2025, at 15:00 UTC as part of a coordinated halt and restart drill led by the validator team. This is a planned disruption to simulate cluster recovery procedures. During this time, users may experience delayed data and 503 errors.
Jul 1, 20:04 UTC
Completed -
The scheduled maintenance has been completed.
Jul 3, 15:38 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 3, 12:00 UTC
Scheduled -
We will be upgrading our Stacks Blockchain API nodes on both Mainnet and Testnet to version v8.11.2 on 2025-07-03 at 12:00 UTC.
This is a minor version upgrade from v8.11.1, and includes performance optimizations, improved endpoint stability, and small bug fixes to improve API consistency and data integrity across block indexing and transaction resolution.
No downtime is expected. However, short-lived API indexing delays may occur immediately following the upgrade.
⸻
📦 Key changes in this release include: • Improved API response caching and pagination consistency • Better handling of pending transactions in mempool endpoints • Minor performance improvements in address-based queries
Completed -
The scheduled maintenance has been completed.
Jul 3, 15:37 UTC
Verifying -
Verification is currently underway for the maintenance items.
Jul 3, 11:58 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 3, 11:30 UTC
Scheduled -
We are proceeding with an urgent upgrade of our NEAR Testnet nodes to version 2.7.0-rc.2 on 2025-07-01 at 11:30 UTC (revised from previously scheduled v2.7.0-rc.1).
This release addresses a critical compatibility issue introduced in v2.7.0-rc.1, which broke backward access to state changes involving the BandwidthSchedulerStateUpdate enum. It also resolves a CPU performance regression affecting nodes that sync from scratch using epoch sync.
No protocol upgrade, database change, or security patch is involved. This is a non-breaking but mandatory hotfix for Testnet stability.
⸻
📦 Key changes in this release include: • Fix: Restores missing StateChangeCause enum variant to preserve compatibility with historical queries • Fix: Reduces CPU overhead during header sync for freshly started nodes • No protocol or DB upgrade required
Resolved -
This incident has been resolved.
Jul 3, 09:20 UTC
Investigating -
The NEAR Testnet appears to have stalled at block 203,886,184 - The QuickNode team is investigating and will update with more information once it is available.
Jul 3, 02:40 UTC
Resolved -
This incident has been resolved.
Jul 2, 19:13 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jul 2, 18:41 UTC
Identified -
This was local to APAC region Solana Infrastructure only. We identified a potential cause and are implementing measures to mitigate the issue.
Jul 2, 18:31 UTC
Investigating -
The QuickNode team is investigating the degraded performance of Solana Mainnet- we will update this page as we acquire new information.
Jul 2, 18:22 UTC
Completed -
The scheduled maintenance has been completed.
Jul 2, 15:35 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 2, 12:00 UTC
Scheduled -
We will be upgrading our rippled nodes on both XRPL Mainnet and Testnet to version v2.5.0 on 2025-07-02 at 12:00 UTC.
This release includes performance improvements, internal consensus optimizations, and prepares the network for upcoming amendments. It is a routine update for stability and protocol alignment.
No downtime is expected during the rollout. Clients may observe brief RPC latency fluctuations during sync finalization.
⸻
📦 Key changes in this release include: • Improvements to validation logic and ledger replay behavior • Enhanced support for upcoming XRPL amendments • Internal tuning of consensus timeouts and transaction propagation
Resolved -
This incident has been resolved.
Jul 1, 20:04 UTC
Investigating -
The Solana Testnet will undergo scheduled maintenance on July 2, 2025, at 15:00 UTC as part of a coordinated halt and restart drill led by the validator team. This is a planned disruption to simulate cluster recovery procedures. During this time, users may experience delayed data and 503 errors. The network will be restarted shortly after the halt, and updates will be provided as progress continues.
Jul 1, 19:58 UTC
Resolved -
This incident has been resolved.
Jul 1, 18:23 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jul 1, 16:05 UTC
Investigating -
The QuickNode team is investigating the degraded performance of Tron in APAC region - we will update this page as we acquire new information.
Jul 1, 15:05 UTC
Completed -
The scheduled maintenance has been completed.
Jul 1, 13:53 UTC
Verifying -
Verification is currently underway for the maintenance items.
Jul 1, 12:46 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 1, 12:00 UTC
Scheduled -
We will be performing a critical upgrade of our NEAR Testnet nodes to version 2.7.0-rc.1 on 2025-07-01 at 12:00 UTC.
⚠️ This upgrade is mandatory to prepare for the upcoming protocol version 78 vote scheduled for 2025-07-02 at 03:00 UTC. Nodes that do not upgrade before the voting epoch will be kicked out and may experience database corruption. We are upgrading from v2.6.3.
📦 Key changes in this release: Network Resharding: Addition of a 9th shard (from 8 to 9) to increase network capacity Performance Optimization: Reduced block production delay from 100ms to 10ms Mandatory Validator Compliance: Non-upgraded validators will be automatically removed after voting epoch Gas Optimization: Implementation of NEP-536 to reduce refund receipts
⚠️ Important Notes: No Rollback After Voting: Once voting begins, downgrade to 2.6.x will not be possible Expected Impact: Brief syncing delays and potential RPC indexing lag during resharding (7-14 hours after voting)
🗓️ Timeline: July 2, 03:00 UTC: Protocol v78 voting begins July 2, 10:00-17:00 UTC: Protocol upgrade and resharding execution
Resolved -
This incident has been resolved.
Jul 1, 10:23 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jul 1, 09:54 UTC
Identified -
The issue has been identified and a fix is being implemented.
Jul 1, 09:43 UTC
Investigating -
The Polygon mainnet, hosted on Erigon nodes, is currently experiencing a network-wide stall at block 73,440,256. Our team is actively collaborating with the Polygon Foundation to resolve this issue.
User Impact: * 503 errors * Request timeouts
We will provide updates as the situation develops.
Jul 1, 09:07 UTC
Resolved -
This incident has been resolved.
Jun 30, 04:59 UTC
Investigating -
The Stacks Mainnet appears to have stalled at block 1,934,394 - The QuickNode team is investigating and will update with more information once it is available.
Jun 30, 04:33 UTC
Completed -
The scheduled maintenance has been completed.
Jun 30, 01:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 30, 00:00 UTC
Scheduled -
We will be upgrading our op-geth/op-node nodes on Celo Mainnet to celo-v2.1.0 on 2025-06-30 at 00:00 UTC
This updates includes the following Highlighted Changes: - This release adds support for the Holocene and Isthmus upgrades on Celo scheduled for Wed Jul 09 2025 15:00:00 UTC
Resolved -
This incident has been resolved.
Jun 27, 10:14 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jun 27, 09:28 UTC
Investigating -
We detected a network-wide stall on the Matic Amoy network: all Bor nodes halted at block height 23,238,363. We are actively investigating the root cause and have begun implementing an alternative solution to restore block production as quickly as possible. Please stay tuned for further updates.
Jun 27, 09:04 UTC
Resolved -
We observed degraded performance on the Cosmos Mainnet due to a hardware fault, which caused some users to experience intermittent 503 (Service Unavailable) errors. The issue has now been identified and fully mitigated, and service has returned to normal. We will continue to monitor network behavior closely and will provide updates if anything else arises.
Jun 27, 10:00 UTC
Completed -
The scheduled maintenance has been completed.
Jun 26, 12:56 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 26, 12:00 UTC
Scheduled -
We will be upgrading our story-geth clients on both the Story Mainnet and Aeneid to version v1.1.1 on 2025-06-26 at 12:00 UTC.
This upgrade is mandatory to enable support for the upcoming Prague fork, which introduces consensus and EVM-level changes that are not backward compatible. All nodes must be upgraded prior to fork activation to remain in sync with the network.
We are upgrading: • Mainnet: from v1.0.2 → v1.1.1 • Aeneid: from v1.1.0 → v1.1.1
Failure to upgrade will result in the node falling out of consensus and becoming incompatible with the post-fork network.
⸻
📦 Key changes in this release include: • Full support for the Prague hard fork • Updates to protocol rules and transaction processing • Unified versioning across Mainnet and Aeneid
Resolved -
This incident has been resolved.
Jun 26, 11:49 UTC
Monitoring -
Our engineering team has deployed the urgent upgrade, and chain activity has resumed. We will continue to monitor the situation
Jun 26, 11:06 UTC
Identified -
Our engineers are closely listening to updates from the foundation.
Jun 26, 06:23 UTC
Investigating -
We are currently investigating this issue.
Jun 26, 03:01 UTC
Resolved -
This incident has been resolved.
Jun 25, 23:50 UTC
Investigating -
Our Hemi Mainnet nodes appear to have stalled at block 2,083,724 - The QuickNode team is investigating with the Hemi chain team and will update with more information once it is available.
Jun 25, 18:33 UTC
Resolved -
This incident has been resolved.
Jun 25, 18:53 UTC
Identified -
The height stall is related to the recent Heimdall v2 Migration. Our engineers are working towards a resolution in collaboration with the foundation.
Jun 25, 03:45 UTC
Investigating -
We are currently investigating this issue.
Jun 25, 03:29 UTC
Completed -
The scheduled maintenance has been completed.
Jun 25, 00:15 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 24, 20:15 UTC
Scheduled -
We will upgrade Heimdall to v2 on Amoy Testnet on June 24, 2025. A block height stall is expected on the network during the upgrade process. However, the exact duration of the stall is uncertain.
Jun 24, 20:13 UTC
Completed -
The scheduled maintenance has been completed.
Jun 25, 00:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 24, 12:00 UTC
Update -
Following the recent release of Agave v2.3.1, now officially recommended for Testnet, we will upgrade directly to v2.3.1 instead of the previously planned v2.3.0.
The upgrade remains scheduled for 2025-06-24 at 12:00 UTC, pending validator stake conditions (less than 5% delinquent).
We are upgrading from version v2.2.16 → v2.3.1.
⸻
📦 Key changes across this upgrade include: • Improved consensus performance and slot vote timing • Enhanced RPC behavior, including: • simulateTransaction now reports loadedAccountsDataSize • More consistent behavior for account data limits • Banking stage and proof verification refinements • Stability fixes from recent beta regressions
Scheduled -
We will be upgrading our Agave and Jito clients on the Solana Testnet to version v2.3.0 on 2025-06-24 at 12:00 UTC.
This upgrade delivers runtime and consensus refinements, improves RPC throughput, and prepares the network for forward compatibility with upcoming protocol developments.
We are upgrading from version v2.2.16 of both clients.
No downtime is expected, but brief RPC delays or ledger replay lag may be observed during rollout.
Notable RPC update in this release: simulateTransaction now includes loadedAccountsDataSize in its result — representing the total number of bytes loaded across all accounts involved in the simulated transaction. 🔗 See changelog section
Completed -
The scheduled maintenance has been completed.
Jun 24, 20:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 24, 14:00 UTC
Scheduled -
We will upgrade Heimdall to v2 on Amoy Testnet on June 24, 2025. A block height stall is expected on the network during the upgrade process. However, the exact duration of the stall is uncertain.
Jun 23, 23:07 UTC
Resolved -
This incident has been resolved.
Jun 23, 19:28 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jun 23, 18:44 UTC
Identified -
The issue has been identified and a fix is being implemented.
Jun 23, 17:06 UTC
Update -
The issue mainly affects trace calls, we are still actively investigating the cause of the increased response time and timeouts.
Jun 23, 16:19 UTC
Investigating -
The QuickNode team is investigating the degraded performance of SEI Pacific - we will update this page as we acquire new information.
Jun 23, 14:42 UTC
Completed -
The scheduled maintenance has been completed.
Jun 21, 13:57 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 21, 12:00 UTC
Update -
We will be undergoing scheduled maintenance during this time.
Jun 19, 09:01 UTC
Scheduled -
We will be upgrading our Hedera Relay and Mirror nodes on both Mainnet and Testnet to versions v0.69.0 and v0.132.0 respectively on 2025-06-21 at 12:00 UTC.
This upgrade introduces performance improvements, enhanced cross-chain token bridging capabilities, and several bug fixes to ensure better RPC stability and reliability.
In particular, Relay v0.69.0 includes: • LayerZero-based cross-chain bridging for WHBAR and HTS tokens • Redis-backed rate limiting and cache-layer optimizations • Improved RPC response handling and resilience to malformed transactions
We are upgrading from Relay v0.68.0 and Mirror v0.132.0.
No downtime is expected, though minor RPC inconsistencies or sync delays may occur shortly after deployment.
Completed -
The scheduled maintenance has been completed.
Jun 20, 18:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 20, 16:00 UTC
Update -
There is a mandatory upgrade, v6.1.0, which will take place at height 152891992 which is roughly at 2025-06-20 16:00:00 UTC. There will be short downtime (a few minutes) during the upgrade.
We'll skip the upgrade to v6.0.7 and directly to v6.1.0.
Resolved -
This incident has been resolved.
Jun 20, 10:34 UTC
Monitoring -
This issue has been identified and mitigated. Users should no longer experience latency or 503 errors. We continue to monitor the situation to ensure stable service.
Jun 20, 09:39 UTC
Investigating -
We are currently experiencing degraded performance on Solana mainnet. Our engineering team is actively investigating the issue. During this time, users may encounter increased latency and intermittent 503 errors. We will provide updates as we work to resolve this matter and appreciate your patience.
Jun 20, 09:18 UTC
Completed -
The scheduled maintenance has been completed.
Jun 20, 02:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 20, 00:00 UTC
Scheduled -
We will be upgrading our bor nodes on Matic Mainnet/Amoy to v2.1.1 on 2025-06-20 at 00:00 UTC
This updates includes the following Highlighted Changes: - This release schedules the Bhilai Hard Fork for Mainnet on July-1-2025 at 9:10 AM UTC (2:40 pm IST)