Update - The Flow EVM Gateway for transactions is currently unavailable but is expected to be back online within the next 24-48 hours, according to the Flow Foundation team.
Next update by 04:00 UTC, January 1, 2025, or sooner as information becomes available.
Dec 30, 2025 - 07:23 UTC
Monitoring - The Flow Mainnet network upgrade is now complete, and Flow mainnet is back online on Mainnet-28.
The block start height is: 137390146. The Flow EVM Gateway for transactions is not yet available, but should be back online in the next 24-48 hours according to the Flow chain team.
Update - We are continuing to experience service disruptions on Flow due to an upstream network issue. While there is no significant change in status, we remain in close coordination with the Flow Foundation as they work to resolve this matter.
The Flow Foundation is investigating a potential security incident and halted the network to ensure user assets remain safe. All Flow RPC endpoints are currently unavailable due to this network halt, and transactions cannot be processed until the Flow network resumes operations. The QuickNode team is actively collaborating with the Foundation and following their instructions to upgrade nodes in preparation for network resumption.
Next update by 20:00 UTC, December 29, 2025, or sooner as information becomes available.
Dec 29, 2025 - 14:25 UTC
Identified - We are currently experiencing service disruptions on Flow due to an upstream issue with the Flow network. The Flow Foundation is investigating a potential security incident and has halted the network to ensure user assets remain safe.
All Flow RPC endpoints are currently unavailable due to the upstream network halt. Transactions cannot be processed until the Flow network resumes.
The quicknode team is actively collaborating and following the instructions from the foundation team to upgrade nodes.
Next update: by 15:00, 12/29 UTC or sooner as information becomes available.
Dec 28, 2025 - 06:50 UTC
Investigating - We are currently experiencing service disruptions on Flow due to an upstream issue with the Flow network. The Flow Foundation is investigating a potential security incident and has halted the network to ensure user assets remain safe.
All Flow RPC endpoints are currently unavailable due to the upstream network halt. Transactions cannot be processed until the Flow network resumes.
The Flow Foundation is actively collaborating with network partners and relevant authorities to address the issue. We will provide further updates as soon as verified information becomes available from the Flow Foundation.
Update -
We will be undergoing scheduled maintenance during this time.
Dec 30, 2025 - 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.
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.
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.
Resolved -
This incident has been resolved.
Dec 22, 21:31 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Dec 22, 20:37 UTC
Identified -
The issue has been identified and a fix is being implemented.
Dec 22, 17:39 UTC
Investigating -
The QuickNode team is investigating the degraded performance of Gnosis - we will update this page as we acquire new information. No user action is needed at this time, you may see heightened error rates on some methods during this incident.
Dec 22, 16:28 UTC
Completed -
The scheduled maintenance has been completed.
Dec 22, 02:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 22, 00:00 UTC
Scheduled -
Scheduled maintenance will be performed during the maintenance window.
**Client Updates:** • Hiero Mirror Node: Upgrading to v0.144.0 • Hiero Relay: Upgrading to v0.73.1
**Release Notes Summary:**
**Hiero JSON-RPC Relay v0.73.0:**
*RPC API Updates* - **`eth_sendRawTransaction`**: Now includes nonce prechecks via new transaction pool functionality to prevent nonce calculation errors - **`eth_getTransactionCount`**: Returns accurate pending transaction counts when using "pending" block tag - **`eth_getBlockReceipts`**: Enhanced validation - **`eth_getTransactionByHash`**: Now returns `to = null` for contract deployment transactions (previously returned address) - **`debug_traceBlockByNumber`**: Fixed CREATE2 opcode handling in trace responses - **`eth_gasPrice`**: Removed caching to provide real-time gas price data
*Features* - Jumbo transaction support enabled for larger transaction payloads
**Hiero JSON-RPC Relay v0.73.1:** Standard maintenance release with various improvements and bug fixes.
**Hiero Mirror Node v0.144.0:**
*New REST API Endpoint* - New `/api/v1/accounts/{id}/hooks/{hookId}/storage` endpoint added for querying hook storage state (HIP-1195)
*Protocol Updates* - Support for consensus node 0.68 protobuf changes including `BlockFooter`, `BlockEnd`, multiple `BlockProof` items, and block items without transaction results (HIP-1056)
*API Changes* - REST Java network fees API now enabled by default - RFC5988 Link header support added to REST API responses
**Hiero Mirror Node v0.143.0:**
*Breaking Changes* - `/api/v1/network/exchangerate` endpoint has been migrated to a new implementation
*API Changes* - New endpoint: `/api/v1/network/accounts/{id}/hooks` - retrieve hooks owned by an account - `/api/v1/network/fees` endpoint rewritten with improved performance
*Protocol Support* - Support added for HIP-1195 (Hooks) transactions including `LambdaSStoreTransaction` - Updated to support consensus node 0.68 block stream specification changes
Resolved -
This incident has been resolved.
Dec 21, 16:49 UTC
Investigating -
The QuickNode team is investigating the degraded performance of our Flow Mainnet nodes in the EU and APAC regions - we will update this page as we acquire new information. No customer action is required at this time, though you may see an increase in error rates for Flow-EVM requests during this incident.
Dec 21, 16:04 UTC
Resolved -
This incident has been resolved.
Dec 21, 16:33 UTC
Monitoring -
Blast Seploia nodes are progressing and are in sync with the network's tip. We are monitoring performance to ensure stability and will provide an update upon confirmation or if further action is required within 10 minutes.
Dec 21, 16:22 UTC
Investigating -
The Blast Sepolia Testnet appears to have stalled at block 30798659 - The QuickNode team is investigating with the chain team and will update with more information once it is available.
Dec 21, 15:24 UTC
Resolved -
This incident has been resolved.
Dec 21, 00:30 UTC
Investigating -
Our team is actively investigating a network-wide stall at block 30756515. https://testnet.blastscan.io/ Data for blocks after the specified height will not be available until the stall is resolved. We will share another update by 00:30 UTC
Dec 20, 15:54 UTC
Resolved -
This incident has been resolved.
Dec 19, 06:24 UTC
Update -
We are continuing to monitor for any further issues.
Dec 19, 06:24 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Dec 19, 03:30 UTC
Identified -
The issue has been identified and a fix is being implemented.
Dec 19, 03:00 UTC
Investigating -
Our team recently identified an increase in 503 errors on Gnosis Mainnet. The errors appear to be associated with archive requests specifically. Some users may experience an increased rate of 503s while we work towards a resolution. We will provide another update by 3:30 UTC.
Dec 19, 01:17 UTC
Resolved -
This incident has been resolved.
Dec 19, 00:19 UTC
Monitoring -
B3 Mainnet nodes are processing blocks and have synchronized with the tip of the network. We are monitoring performance to ensure stability and will provide an update upon confirmation or if further action is required within 10 minutes.
Dec 18, 23:40 UTC
Investigating -
The B3 Mainnet appears to have stalled at block 43,713,197 - The QuickNode team is investigating and will update with more information once it is available.
Dec 18, 19:54 UTC
Resolved -
This incident has been resolved.
Dec 18, 19:53 UTC
Update -
We are continuing to monitor for any further issues.
Dec 18, 19:28 UTC
Monitoring -
Engineers have applied updates and nodes are beginning to progress as normal. Errors should now resolve and normal activity should continue without issue.
We continue to monitor for performance.
Dec 18, 18:45 UTC
Identified -
We are currently upgrading our XRPL Mainnet `rippled` to 3.0.0 and `clio` to 2.6.0 following an amendment activation earlier today.
Users may experience "Amendment blocked, need upgrade" errors until the upgrade is complete. We are actively working on this and will provide updates as we progress through the upgrade.
Dec 18, 17:38 UTC
Investigating -
We are currently upgrading our XRPL Mainnet nodes to version 2.6.2 following an amendment activation earlier today. Users may experience "Amendment blocked, need upgrade" errors until the upgrade is complete. We are actively working on this and will provide updates as we progress through the upgrade.
Dec 18, 15:48 UTC
Completed -
The scheduled maintenance has been completed.
Dec 18, 15:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 18, 13:30 UTC
Scheduled -
Scheduled maintenance will be performed during the maintenance window.
**Client Updates:** • injectived: Upgrading to v1.17.2
**Upgrade Details:** • Upgrade Height: 146,295,000, approximately at 14:00 UTC on December 18th, 2025 • There will be short downtime during the upgrade
Resolved -
This incident has been resolved.
Dec 18, 00:48 UTC
Monitoring -
Our team has deployed the latest release from the Polygon Foundation, and our nodes are now processing blocks and have synchronized with the network's tip. We are monitoring performance to ensure stability and will provide an update upon confirmation or if further action is required within 15 minutes.
Dec 18, 00:35 UTC
Update -
The Polygon Foundation has recently released an update to address this issue. Our team is actively working to deploy this change and will continue to share updates as we progress towards a full recovery. Customers may see a reduction in error rate at this time; however, some degraded performance is still expected.
We will share another update by 00:30 UTC
Dec 17, 22:46 UTC
Identified -
A solution has been identified by the Polygon team and will be applied ASAP by our team once it becomes available.
No user action is required at this time, although you may see heightened errors rates and no new blocks being created during this incident.
Update -
The QuickNode team is investigating the halt of Polygon Mainnet with the Polygon chain team No user action is required at this time, although you may see heightened errors rates and no new blocks being created during this incident.
Investigating -
The QuickNode team is investigating the degraded performance of our Polygon Mainnet infrastructure - we will update this page as we acquire new information.
No user action is required at this time, although you may see heightened errors rates during this incident. We will update this status by 19:30 UTC.
Dec 17, 18:35 UTC