Resolved -
The issue affecting Solana Devnet has been fully resolved. Devnet nodes that had forked due to running the outdated v3.0.12 version have been successfully upgraded to v3.1 and are now operating normally.
The Solana Devnet DAS API has recovered and is fully operational.
Mainnet and all other networks were unaffected throughout the incident.
Jan 16, 20:23 UTC
Investigating -
Solana Devnet nodes forked off due to running outdated v3.0.12. An upgrade to v3.1 is in progress to resolve the issue. Solana Devnet DAS API is temporarily affected, with fix expected today. Mainnet and other networks remain unaffected and operational.
Jan 16, 15:04 UTC
Completed -
The scheduled maintenance has been completed.
Jan 16, 11:30 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 16, 09:30 UTC
Scheduled -
Scroll Mainnet and Testnet will be upgraded to l2geth v5.10.2 to include the security fixes from upstream geth for the peering module.
Jan 16, 09:26 UTC
Completed -
The scheduled maintenance has been completed.
Jan 15, 23:58 UTC
Verifying -
Verification is currently underway for the maintenance items.
Jan 15, 23:37 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 15, 00:20 UTC
Scheduled -
Story Mainnet is undergoing scheduled maintenance to complete Fusaka compatible protocol upgrade. Network is expected to be unavailable for the next 24-48 hours. During this time, all on-chain transactions will be paused and intermittent block stalls will occur.
Jan 15, 00:19 UTC
Completed -
The scheduled maintenance has been completed.
Jan 15, 11:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 14, 11:00 UTC
Scheduled -
Following a security advisory from Polygon Labs, we will perform an urgent security upgrade across Polygon Mainnet and Polygon Amoy on January 14, 2026, at 11:00 UTC.
This is not a hard fork, but a required security update for node operators. Per Polygon’s guidance, details about the nature or severity of the issue are intentionally limited to ensure a safe rollout.
Scope of the upgrade • Bor → v2.5.7 • Erigon → v3.3.7 • Heimdall → v0.5.6
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 cluster.
Completed -
The scheduled maintenance has been completed.
Jan 15, 00:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 14, 12:00 UTC
Scheduled -
We will perform a mandatory security upgrade across Optimism Mainnet and Optimism Sepolia on January 14, 2026, at 12:00 UTC. This upgrade is required for OP Stack networks and includes mandatory updates to op-node and op-geth. The update addresses a security issue; details are intentionally limited per upstream guidance.
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.
Jan 15, 00:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 14, 22:00 UTC
Scheduled -
Update op-geth to v1.101605.0 and op-node to v1.16.5 The releasea includes security fixes and an upstream merge of go-ethereum v1.16.5.
Jan 14, 21:55 UTC
Resolved -
This incident has been resolved.
Jan 14, 21:30 UTC
Identified -
The underlying issue has been identified and a mitigation is in place. Users should see better responses while ongoing work to resolve the underlying issue while our engineers work on a full solution.
Jan 14, 16:12 UTC
Investigating -
We are currently investigating an issue affecting Ink network. Block production is stalled at block height 34,900,022.
Our engineering team is actively working to restore service.
We will provide updates as we have more information.
Jan 14, 14:15 UTC
Resolved -
This incident has been resolved.
Jan 14, 21:11 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jan 14, 20:45 UTC
Investigating -
Sui Mainnet appears to have stalled at block 234,608,191 The QuickNode team is investigating with the SUI Chain Team and will update with more information once it is available.
Jan 14, 14:43 UTC
Completed -
The scheduled maintenance has been completed.
Jan 14, 20:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 13, 20:00 UTC
Scheduled -
Kaia v2.1.0 introduces an experimental implementation of an efficient statedb implementation, FlatTrie. It is an adaptation of Erigon’s state scheme where accounts and contract variables are efficiently organized. In an experiment, the disk space of a Kairos archive node at 12 million blocks was about 1600 GB in default settings and 600 GB in FlatTrie setting.
Jan 13, 17:44 UTC
Resolved -
This incident has been resolved.
Jan 14, 16:00 UTC
Update -
We are continuing to work on a fix for this issue.
Jan 14, 14:08 UTC
Update -
We are continuing to work on a fix for this issue.
Jan 14, 13:30 UTC
Identified -
We are performing a mandatory security upgrade across all Ethereum networks. The update addresses a security issue on the peering networking on the Geth client.
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.
Jan 14, 15:27 UTC
Investigating -
Scroll Mainnet appears to have stalled at block 28,074,287 - The Quicknode team is investigating and will update with more information once it is available.
Jan 14, 15:16 UTC
Completed -
The scheduled maintenance has been completed.
Jan 14, 14:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 10, 14:00 UTC
Scheduled -
The Solana Foundation has requested an emergency upgrade for all Solana Mainnet Agave and Jito clients to v3.0.14 on January 10, 2026, at 6:27 UTC.
This release contains a critical set of patches that should be applied to staked and unstaked Solana Mainnet validators.
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 cluster.
Resolved -
This incident has been resolved.
Jan 14, 00:12 UTC
Monitoring -
Blocks are syncing on the Blast Sepolia Network. We are monitoring performance to ensure stability and will provide an update upon confirmation or if further action is required within 10 minutes.
Jan 13, 23:58 UTC
Investigating -
The Blast Sepolia Network is experiencing intermittent block stalls - The Quicknode team is investigating and will update with more information once it is available.
Jan 13, 16:18 UTC
Completed -
The scheduled maintenance has been completed.
Jan 13, 23:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 13, 22:00 UTC
Scheduled -
During the maintenance window, 2 small pauses in Streams/Webhooks delivery are expected, each pause is expected to be < 10 minutes in duration. No action is required - Streams and webhooks will resume automatically where they left off.
Jan 7, 18:12 UTC
Completed -
The scheduled maintenance has been completed.
Jan 13, 22:45 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 13, 14:45 UTC
Scheduled -
The Solana Foundation has requested an emergency upgrade for all Solana Testnet and Devnet Agave and Jito clients to v3.1.16 on January 11, 2026, at 11:36 UTC.
This release contains a critical set of patches that should be applied to staked and unstaked Solana Testnet and Devnet validators.
Resolved -
This incident has been resolved.
Jan 13, 06:42 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jan 13, 06:28 UTC
Identified -
As per the foundation recommendation, our engineers are deploying the fix version across the Polygon mainnet archive node infrastructure. As our engineers work towards a resolution, please find the next update on or before 6:00 UTC
Jan 13, 03:30 UTC
Investigating -
Our team is working alongside the Polygon Foundation to address a network-wide issue affecting archive nodes.
Customers may experience increased error rates, including 503 responses, along with failed or timing-out requests when querying historical (archive) data. This behavior is expected until a solution is provided by the Foundation.
Standard (non-archive) Polygon endpoints are not affected at this time, and our team is actively working to restore archive capacity and mitigate customer impact.
The Quicknode Support team will update this status by 3:00 UTC.
Jan 12, 16:28 UTC
Resolved -
This incident has been resolved.
Jan 12, 17:42 UTC
Investigating -
Cyber Sepolia appears to have stalled at block 5,776,486 - The Quicknode team is investigating and will update with more information once it is available.
Jan 12, 16:53 UTC
Resolved -
This incident has been resolved.
Jan 11, 20:15 UTC
Monitoring -
The Polygon archive nodes have recovered, we continue to monitor them for performance.
Jan 11, 19:31 UTC
Investigating -
The Quicknode team is investigating the degraded performance of Polygon Mainnet Archive Nodes.
Customers may experience increased error rates, including 503 responses, along with failed or timing-out requests when querying historical (archive) data.
Standard (non-archive) Polygon endpoints are not affected at this time, and our team is actively working to restore archive capacity and mitigate customer impact.
We will update this page as we acquire new information.
Jan 11, 19:15 UTC
Resolved -
This incident has been resolved.
Jan 11, 02:43 UTC
Investigating -
We are currently investigating an issue affecting Tempo Testnet nodes. Block height is stalled at 301,478 and nodes are not progressing to the current tip.
Our engineering team is actively investigating the root cause and working toward a resolution. We will provide the next update on or before 03:00 1/11 UTC.
Jan 10, 13:09 UTC
Completed -
The scheduled maintenance has been completed.
Jan 10, 19:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 9, 19:00 UTC
Scheduled -
Story-Geth v1.2.0 (Yasunari) binaries were released on 2026-12-23. This required upgrade includes Fusaka upgrade to remain compatible with Ethereum, and EIP-7702 wallet compatibility enhancements.
Jan 8, 22:21 UTC
Resolved -
Tempo Testnet has been migrated to Moderato.
New chain ID: 42431
Redeploy contracts: If you have deployed contracts, those will need to be redeployed on the new testnet. Reset databases / indexers: if you have anything that depends on data from the old testnet, that data will not be relevant to the new testnet.
Jan 9, 18:55 UTC
Completed -
The scheduled maintenance has been completed.
Jan 9, 12:45 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 7, 12:00 UTC
Update -
We will be undergoing scheduled maintenance during this time.
Dec 30, 10:32 UTC
Scheduled -
We will upgrade our BSC Mainnet and Chapel clients — Geth to v1.6.5 and Erigon to v1.4.3 — on January 7, 2026, at 12:00 UTC. This release prepares the network for the upcoming protocol upgrade and includes stability and performance improvements across execution clients.
In addition, please note that the BSC network will undergo the Fermi hardfork on January 14, 2026. As part of the Fermi upgrade, block time will be reduced from approximately ~0.75 seconds to ~0.45 seconds, improving transaction throughput and network responsiveness.
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 cluster.
Resolved -
This incident has been resolved.
Jan 9, 02:26 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jan 8, 22:17 UTC
Identified -
We have identified the cause of the ongoing degradation affecting Polygon archive endpoints. Mitigation efforts are underway to reduce error rates while we continue investigating a longer-term resolution.
Non-archive Polygon endpoints remain unaffected. We will continue to provide updates as recovery progresses.
Jan 8, 21:41 UTC
Investigating -
The Quicknode team is investigating the degraded performance of Polygon Mainnet Archive Nodes.
Customers may experience increased error rates, including 503 responses, along with failed or timing-out requests when querying historical (archive) data.
Standard (non-archive) Polygon endpoints are not affected at this time, and our team is actively working to restore archive capacity and mitigate customer impact.
We will update this page as we acquire new information.
Jan 8, 20:46 UTC
Completed -
The scheduled maintenance has been completed.
Jan 8, 19:30 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 8, 16:30 UTC
Scheduled -
Polygon has released Bor v2.5.6 and Erigon v3.3.6, which defines the block number for the Dandeli hardfork on Mainnet, at block height 81424000 . The expected times for the hardfork is on Wed, Jan 09, 2026, 02:00 PM UTC .
Jan 8, 16:06 UTC
Completed -
The scheduled maintenance has been completed.
Jan 7, 22:01 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 7, 14:00 UTC
Scheduled -
Following the Solana Foundation’s recommendation, we will upgrade our Solana Testnet Agave and Jito clients to v3.1.5 on January 7, 2026, at 14:00 UTC.
This release enhances streamer and TPU client reliability and removes a legacy SVM assertion.
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 cluster.
Completed -
The scheduled maintenance has been completed.
Jan 7, 22:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 7, 14:00 UTC
Scheduled -
Following the Solana Foundation’s recommendation, we will upgrade our Solana Devnet Agave client to v3.1.5 on January 7, 2026, at 14:00 UTC.
This release enhances streamer and TPU client reliability and removes a legacy SVM assertion.
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 cluster.
Resolved -
This incident has been resolved.
Jan 7, 17:50 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jan 7, 16:57 UTC
Identified -
We have identified a possible root cause for Flow Testnet EVM - Our engineers are working on a fix.
The Support Team will provide an update by 17:30 UTC.
Jan 7, 16:33 UTC
Investigating -
The Quicknode team is investigating the degraded performance of Flow Testnet EVM. No action needed from users at this time but you may see an increase in error rates during this incident.
The Support Team will provide an update by 17:00 UTC.
Jan 7, 16:22 UTC
Resolved -
This incident has been resolved.
Jan 6, 16:27 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jan 6, 16:02 UTC
Identified -
We have identified a cause for Eth Mainnet 503s being served - Our engineers are working on a fix now. The Quicknode Support team will update this status by 16:30 UTC.
Jan 6, 15:52 UTC
Resolved -
Block production has resumed on Starknet mainnet. The issue has been resolved by the Starknet team.
All QuickNode Starknet endpoints are operating normally and processing transactions.
Jan 5, 14:49 UTC
Investigating -
Block production remains halted on Starknet mainnet.
Update from Starknet team (10:42 UTC): They are debugging a discrepancy between block execution and proving logic. Specific transactions and differences have been identified.
QuickNode is in contact with the Starknet team and monitoring for resolution.