Identified - We're currently seeing degraded performance on Ethereum Sepolia in the APAC region. Our engineering team is actively working to restore node health.
Mar 12, 2026 - 21:59 UTC
Investigating - The Quicknode team is investigating the degraded performance of the gRPC API on Solana Mainnet affecting all regions - we will update this page as we acquire new information.
Users may experience 503 errors, and timeouts during this time.
Mar 12, 2026 - 17:23 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 10, 2026 - 15:00 UTC
Scheduled - The Solana Foundation has requested an emergency upgrade for all Solana Mainnet Agave and Jito clients to v3.1.10.
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.
Completed -
The scheduled maintenance has been completed.
Mar 11, 15:30 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 11, 13:30 UTC
Scheduled -
Scheduled maintenance will be performed on the Cosmos Mainnet during the scheduled maintenance window.
**Client Updates:** - Gaiad: Upgrading to v27.0.0
**Upgrade Details:** - Governance upgrade via proposal: https://www.mintscan.io/cosmos/proposals/1025 - Upgrade Height: 30,151,300 (Roughly at Mar 11th 2026, 14:10:00 UTC) - There will be a short period of downtime (a few minutes) during the upgrade.
**Release Notes Summary:** - **Multi-send transaction behavior change:** Transactions using multi-send messages now incur a gas surcharge and are subject to a limit on the number of recipients.
Resolved -
The issue affecting Cyber mainnet has been resolved. The network has resumed producing blocks and is operating normally. All Cyber mainnet RPC endpoints are now fully operational. If you continue to experience any issues, please contact our support team.
Mar 11, 10:48 UTC
Investigating -
We are currently investigating an issue with Cyber mainnet. The network is stalled at block 29,896,269. All Cyber mainnet RPC endpoints are currently affected. New blocks are not being produced until the network resumes. Our engineering team is actively investigating and working to resolve this issue. We will provide the next update by 11am UTC or sooner.
Mar 11, 09:51 UTC
Completed -
The scheduled maintenance has been completed.
Mar 10, 16:30 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 10, 14:30 UTC
Scheduled -
Scheduled maintenance will be performed on the Ault Testnet during the scheduled maintenance window.
**Client Updates:** • aultd: Upgrading to v1.0.1 • Upgrade Target Height : 7,847,200 • Estimated Upgrade Time: Mar 10, 2026 15:00 UTC • There will be a short period of downtime (a few minutes) during the upgrade.
Mar 10, 00:26 UTC
- **Missing RPC fields fixed** — A bug causing certain RPC response fields to be absent has been resolved - **WebSocket subscriptions fixed** — A race condition affecting WebSocket subscription delivery has been corrected
Resolved -
This incident has been resolved.
Mar 10, 00:45 UTC
Investigating -
We are currently investigating an upstream issue with Abstract testnet. The network is stalled at block 16,773,987. The Abstract Foundation has been notified and is investigating. All Abstract testnet RPC endpoints are currently affected by the upstream network stall. New blocks are not being produced until the network resumes. We will provide the next update by 2PM UTC or sooner as information becomes available.
Mar 9, 12:26 UTC
Resolved -
The Injective mainnet upgrade to v1.18.2 has been completed successfully. INJ endpoints are fully operational.
Mar 9, 16:48 UTC
Investigating -
INJ endpoints may experience brief disruptions due to an upcoming mandatory Injective mainnet upgrade to v1.18.2. We are actively tracking the upgrade block height and will provide timing details as soon as they are confirmed.
Mar 9, 14:04 UTC
Completed -
The scheduled maintenance has been completed.
Mar 9, 04:30 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 9, 03:30 UTC
Scheduled -
Scheduled maintenance will be performed on Monad Testnet infrastructure during the scheduled maintenance window.
**Client Updates:** - Monad: Upgrading to v0.13.0
---
**Upgrade Highlights:**
RPC changes in the RPC after the v0.13.0 upgrade:
- `latest` block tag now maps to **Proposed** blocks, instead of Voted - `newHeads` and `logs` WebSocket subscriptions now stream **Voted** blocks, instead of Finalized - `eth_sendRawTransactionSync` now returns the receipt from **Proposed** blocks, instead of Voted
These changes improve the RPC polling and streaming rate by one block (~400 ms) and enhance developer and end-user experience.
Completed -
The scheduled maintenance has been completed.
Mar 9, 02:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 9, 00:00 UTC
Scheduled -
Scheduled maintenance will be performed during the maintenance window to upgrade the Tempo client and apply the T1C network upgrade.
**Client Updates:** - tempo: Upgrading to v1.4.0
---
**Release Notes Summary:**
**T1C Network Upgrade Activation** - **Moderato (testnet):** Monday, March 9 at 16:00 CET - **Mainnet:** Thursday, March 12 at 16:00 CET
**Breaking Changes After T1C Activation**
- **Keychain signature format change:** Only V2 keychain signatures (`type 0x04`) are accepted post-T1C. Transactions using legacy V1 signatures will be rejected. Pre-T1C keys remain accessible — only the signature type and hash calculation have changed. - **Key authorization `chain_id` wildcard removed:** `chain_id=0` is no longer valid. Key authorizations must specify the exact Tempo chain ID. - **Precompile set updated:** Precompiles transition from Prague to Osaka at T1C activation.
Completed -
The scheduled maintenance has been completed.
Mar 8, 19:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 8, 13:00 UTC
Scheduled -
A scheduled maintenance window has been planned for our Frankfurt (FRA) region on March 8, 2026 between 13:00 and 19:00 UTC. During this time, some users may experience brief intermittent packet loss or increased latency on the affected networks listed above. We will be actively monitoring throughout and will take all necessary measures to minimize impact. All other regions remain fully operational.
Mar 5, 14:28 UTC
Resolved -
After monitoring, latency on Sei Pacific has returned to normal levels. The issue has been fully resolved.
Customers should no longer experience slower response times on RPC requests. If you continue to experience any issues, please contact our support team.
Mar 7, 14:47 UTC
Monitoring -
A fix has been applied and our engineering team is actively monitoring to ensure the issue is fully resolved. Customers may still experience some residual slower response times on RPC requests.
We will provide the next update by 2PM UTC or sooner.
Mar 7, 13:06 UTC
Investigating -
We are currently experiencing elevated latency on Sei Pacific. Customers may experience slower response times on RPC requests. Endpoints remain operational but performance is degraded.
Our teams are actively investigating and working to restore normal performance levels. We will provide the next update by 2PM UTC or sooner.
Mar 7, 12:31 UTC
Resolved -
This incident has been resolved.
Mar 6, 22:19 UTC
Monitoring -
The Hedera Testnet network has resumed. Our team is monitoring for stability.
Mar 6, 21:51 UTC
Update -
We are continuing to investigate this issue.
Mar 6, 21:51 UTC
Investigating -
The Hedera Testnet network appears to have stalled at block 32392072 - The Quicknode team is investigating and will update with more information once it is available.
Mar 6, 21:42 UTC
Monitoring -
Foundation has confirmed block production has resumed without flashblocks and actively working on recovery.
Mar 6, 00:00 UTC
Investigating -
Unichain Sepolia has stalled network-wide at block 45,897,373. We are currently investigating and will work closely with the foundation on resolution.
Completed -
The scheduled maintenance has been completed.
Mar 5, 13:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 5, 12:00 UTC
Scheduled -
Scheduled maintenance will be performed on Fuel Mainnet during the scheduled maintenance window. These are simple gas configuration changes as directed by the Fuel chain team without changes to RPC.
Mar 4, 18:05 UTC
Resolved -
This incident has been resolved.
Mar 4, 23:55 UTC
Monitoring -
Network movement has resumed and our nodes are serving tip data. We will monitor performance closely and mark the incident as resolved as soon as possible.
Mar 4, 23:29 UTC
Investigating -
Optimism Mainnet has stalled network-wide at block 148,533,323. We are currently investigating and will work closely with the foundation on resolution.
Completed -
The scheduled maintenance has been completed.
Mar 4, 18:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 4, 14:00 UTC
Scheduled -
We will be upgrading our Ethereum consensus (Lighthouse) nodes to the latest stable version (v8.1.1) to incorporate a mandatory security fix along with networking and validator client bug fixes.
Notable changes: --- - Security: Critical security vulnerability fix affecting all prior Lighthouse versions — further details to be disclosed by the Lighthouse team in the coming days
- Bug Fixes: Validator Client — Fixed a regression from `v8.1.0` where the VC head monitoring stream would continuously time out, causing repeated Head service failed warnings. Networking — Fixed duplicate data columns in `DataColumnsByRange` responses caused by skip slots, which was causing peers to downscore nodes with `DuplicatedData` errors. Networking — Snappy decoding errors are now correctly classified as `InvalidData` instead of `IoError`, fixing improper error handling in RPC message decoding. Memory — Fixed a slow memory leak on long-running nodes caused by missing prune calls for the `observed_column_sidecars` cache during finalization Sync — Fixed head chain processing to correctly sort by peer count in descending order, improving sync peer selection
- Networking Improvements: Peers sending invalid RPC requests that result in decoding errors are now penalized and disconnected ---
Resolved -
This incident has been resolved.
Mar 4, 04:00 UTC
Investigating -
The Fuel Sepolia network appears to have stalled at block 56,428,550 - The Quicknode team is investigating and will update with more information once it is available.
Mar 3, 18:18 UTC
Completed -
The scheduled maintenance has been completed.
Mar 2, 18:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 2, 15:45 UTC
Scheduled -
We are upgrading our Injective Testnet nodes in preparation for a chain-level upgrade that with take place at block height 115505000.
Mar 2, 15:20 UTC
Resolved -
The issue affecting the XRPL EVM network, which caused the chain to stall at block 4,748,999, has been fully resolved. The network is now operating normally and blocks are progressing as expected.
Our team has confirmed stability and will continue to monitor the network closely.
We appreciate your patience while we worked to resolve this incident.
Mar 2, 17:01 UTC
Investigating -
We are currently investigating an incident affecting the XRPL EVM network. Our team is actively working on identifying the root cause and implementing a resolution. Further updates will be shared as soon as more information becomes available.
Mar 2, 13:33 UTC
Resolved -
This incident has been resolved.
Mar 2, 16:22 UTC
Update -
We are continuing to investigate this issue.
Mar 2, 16:22 UTC
Investigating -
Injective Testnet nodes are currently undergoing a network upgrade to v1.18.1 at block height 115,505,000. This upgrade was recently released and is now being applied. During this process, testnet services may be temporarily unavailable. Our team is actively completing the upgrade and will provide updates as progress continues.
Mar 2, 16:19 UTC
Completed -
The scheduled maintenance has been completed.
Feb 27, 00:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 16, 00:00 UTC
Scheduled -
In effort to ensure quick and reliable performance, we’re initiating a client migration on Binance Smart Chain from the Erigon client to the Reth client. This is expected to completed by February 27.
BSC Testnet has already been migrated, allowing your team to test and observe for any potential issues. While such issues are unlikely, there are a few minor differences to note.
Minor: - `eth_getBlockByNumber`: size field is 1 byte smaller in Reth (may affect some archive assumptions) - Minor formatting differences:`debug_traceBlock` / `trace_block`: error message capitalization (“Out of gas” vs “out of gas”) - eth_feeHistory: returns 0 instead of 0.0
Important: - This migration deprecates all erigon_* methods on BNB Smart Chain, as they are not supported by Reth.
Feb 9, 15:46 UTC