tag:status.quicknode.com,2005:/history Quicknode Status - Incident History 2026-03-17T03:13:54Z Quicknode tag:status.quicknode.com,2005:Incident/29030175 2026-03-17T12:00:00Z 2026-03-16T10:36:54Z [Urgent] Scheduled: BSC Testnet - Upgrade BSC Client to v1.7.1 <p><strong>THIS IS A SCHEDULED EVENT Mar <var data-var='date'>17</var>, <var data-var='time'>12:00</var> - <var data-var='time'>14:00</var> UTC</strong></p><p><small>Mar <var data-var='date'>16</var>, <var data-var='time'>10:36</var> UTC</small><br><strong>Scheduled</strong> - Urgent maintenance will be performed during the scheduled maintenance window to upgrade the BSC client software.<br /><br />**Client Updates:**<br />- BSC: Upgrading to v1.7.1<br /><br />---<br /><br />**Release Notes Summary:**<br /><br />**BSC Chapel Testnet — Osaka/Mendel Hardfork Upgrade**<br /><br />- **Hard Fork Deadline:** BSC Chapel testnet Osaka/Mendel hardfork activates at **2026-03-24 02:30:00 UTC**<br />- **Security Fix:** CVE-2026-24051 patched via OpenTelemetry dependency upgrade<br />- **RPC Fix:** Gas limit check corrected in the trace API (`debug_traceTransaction` and related trace methods)<br />- **RPC Fix:** Fee history response accuracy corrected (`eth_feeHistory`)<br /><br />---<br /><br />**Additional Information:**<br />- Full release notes:<br /> - https://github.com/bnb-chain/bsc/releases/tag/v1.7.1</p> tag:status.quicknode.com,2005:Incident/29044868 2026-03-17T02:15:07Z 2026-03-17T02:15:07Z [Urgent] Tempo Node Upgrade to v1.4.2 <p><small>Mar <var data-var='date'>17</var>, <var data-var='time'>02:15</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'>17</var>, <var data-var='time'>00:15</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'>17</var>, <var data-var='time'>00:03</var> UTC</small><br><strong>Scheduled</strong> - We are upgrading our Tempo node to v1.4.2. During the maintenance window, brief interruptions may occur.<br />This is a maintenance release with transaction pool hardening and contract type improvements/fixes.<br />RPC Changes<br />eth_estimateGas — modified Now hardfork-aware. Gas estimates may differ from previous behavior when called near or across a fork boundary.<br />AA transaction serialization — fixed Corrects broken roundtrip conversion for account abstraction transactions. AA transaction handling via RPC will now return accurate results. This release also contains transaction pool stability improvements and has no additional user-facing RPC changes.<br /><br />https://github.com/tempoxyz/tempo/releases/tag/v1.4.2</p> tag:status.quicknode.com,2005:Incident/29014728 2026-03-17T01:00:07Z 2026-03-17T01:00:07Z [Standard] Scheduled: Monad Mainnet - Upgrade to v0.13.0 <p><small>Mar <var data-var='date'>17</var>, <var data-var='time'>01:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'>15</var>, <var data-var='time'>18:20</var> UTC</small><br><strong>Scheduled</strong> - Scheduled maintenance will be performed on Monad Mainnet infrastructure during the scheduled maintenance window.<br /><br />**Client Updates:**<br />- Monad: Upgrading to v0.13.0<br /><br />---<br /><br />**Upgrade Highlights:**<br /><br />RPC changes in the RPC after the v0.13.0 upgrade:<br /><br />- `latest` block tag now maps to **Proposed** blocks, instead of Voted<br />- `newHeads` and `logs` WebSocket subscriptions now stream **Voted** blocks, instead of Finalized<br />- `eth_sendRawTransactionSync` now returns the receipt from **Proposed** blocks, instead of Voted<br /><br />These changes improve the RPC polling and streaming rate by one block (~400 ms) and enhance developer and end-user experience.<br /><br />---<br /><br />**Additional Information:**<br />- Full release notes & upgrade instructions:<br /> - https://docs.monad.xyz/node-ops/upgrade-instructions/v0.13.0</p> tag:status.quicknode.com,2005:Incident/28973112 2026-03-16T23:00:07Z 2026-03-16T23:00:07Z [Standard] XRP / `rippled` Upgrade to 3.1.2 <p><small>Mar <var data-var='date'>16</var>, <var data-var='time'>23:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'>16</var>, <var data-var='time'>15:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>19:36</var> UTC</small><br><strong>Scheduled</strong> - We are upgrading our rippled node to v3.1.2. During the maintenance window, brief interruptions to RPC availability may occur. This release contains security fixes and has no user-facing RPC changes.<br /><br />Full Release Notes:<br />3.1.1: https://github.com/XRPLF/rippled/releases/tag/3.1.1<br />3.1.2: https://github.com/XRPLF/rippled/releases/tag/3.1.2</p> tag:status.quicknode.com,2005:Incident/29033190 2026-03-16T22:00:07Z 2026-03-16T22:00:07Z [Standard] XRP / rippled Upgrade to 3.1.2 <p><small>Mar <var data-var='date'>16</var>, <var data-var='time'>22:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'>16</var>, <var data-var='time'>14:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'>16</var>, <var data-var='time'>13:27</var> UTC</small><br><strong>Scheduled</strong> - We are upgrading our rippled node to 3.1.2. During the maintenance window, brief interruptions to RPC availability may occur. This release contains security fixes and has no user-facing RPC changes.<br /><br />Full release notes: https://github.com/XRPLF/rippled/releases/tag/3.1.2</p> tag:status.quicknode.com,2005:Incident/28951429 2026-03-16T20:34:38Z 2026-03-16T20:34:38Z Ethereum Sepolia (APAC region): Degraded Performance <p><small>Mar <var data-var='date'>16</var>, <var data-var='time'>20:34</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'>12</var>, <var data-var='time'>21:59</var> UTC</small><br><strong>Identified</strong> - We're currently seeing degraded performance on Ethereum Sepolia in the APAC region. Our engineering team is actively working to restore node health.</p> tag:status.quicknode.com,2005:Incident/29035333 2026-03-16T18:00:07Z 2026-03-16T18:00:07Z Hypercore gRPC version upgrade <p><small>Mar <var data-var='date'>16</var>, <var data-var='time'>18:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'>16</var>, <var data-var='time'>17:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'>16</var>, <var data-var='time'>15:19</var> UTC</small><br><strong>Scheduled</strong> - We will be performing a small upgrade to our hypercore gRPC nodes, which may cause some connection breaks. Please note that we are making a small change to filtering, which should not cause any breaking changes, just performance improvements. Please reach out to our support team for any questions.</p> tag:status.quicknode.com,2005:Incident/28946984 2026-03-15T18:23:30Z 2026-03-15T18:23:30Z Solana Mainnet - gRPC Degraded Performance <p><small>Mar <var data-var='date'>15</var>, <var data-var='time'>18:23</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'>12</var>, <var data-var='time'>17:23</var> UTC</small><br><strong>Investigating</strong> - 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.<br /><br />Users may experience 503 errors, and timeouts during this time.</p> tag:status.quicknode.com,2005:Incident/28901924 2026-03-14T15:00:07Z 2026-03-14T15:00:07Z [Urgent] Emergency Upgrade: Solana Mainnet, Devnet, and Testnet – Upgrade Agave & Jito to 3.1.10 <p><small>Mar <var data-var='date'>14</var>, <var data-var='time'>15:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'>10</var>, <var data-var='time'>15:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'>10</var>, <var data-var='time'>14:49</var> UTC</small><br><strong>Scheduled</strong> - The Solana Foundation has requested an emergency upgrade for all Solana Mainnet Agave and Jito clients to v3.1.10.<br /><br />This release contains a critical set of patches that should be applied to staked and unstaked Solana Mainnet validators.<br /><br />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.<br /><br />Release links:<br /> • 📦 Agave: https://github.com/anza-xyz/agave/releases/tag/v3.1.10<br /> • 📦 Jito: https://github.com/jito-foundation/jito-solana/releases/tag/v3.1.10-jito<br /> • 🔄 Compare (Agave): https://github.com/anza-xyz/agave/compare/v3.1.8…v3.1.10<br /> • 🔄 Compare (Jito): https://github.com/jito-foundation/jito-solana/compare/v3.1.8-jito…v3.1.10-jito</p> tag:status.quicknode.com,2005:Incident/28796197 2026-03-11T15:30:07Z 2026-03-11T15:30:07Z [Standard] Scheduled: Cosmos Mainnet - Upgrade Gaiad to v27.0.0 <p><small>Mar <var data-var='date'>11</var>, <var data-var='time'>15:30</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'>11</var>, <var data-var='time'>13:30</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>02:50</var> UTC</small><br><strong>Scheduled</strong> - Scheduled maintenance will be performed on the Cosmos Mainnet during the scheduled maintenance window.<br /><br />**Client Updates:**<br />- Gaiad: Upgrading to v27.0.0<br /><br />**Upgrade Details:**<br />- Governance upgrade via proposal: https://www.mintscan.io/cosmos/proposals/1025<br />- Upgrade Height: 30,151,300 (Roughly at Mar 11th 2026, 14:10:00 UTC)<br />- There will be a short period of downtime (a few minutes) during the upgrade.<br /><br />**Release Notes Summary:**<br />- **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.<br /><br />**Additional Information:**<br />- Full release notes: https://github.com/cosmos/gaia/releases/tag/v27.0.0</p> tag:status.quicknode.com,2005:Incident/28918051 2026-03-11T10:48:34Z 2026-03-11T10:48:34Z Cyber Mainnet - Network Stall <p><small>Mar <var data-var='date'>11</var>, <var data-var='time'>10:48</var> UTC</small><br><strong>Resolved</strong> - The issue affecting Cyber mainnet has been resolved. The network has resumed producing blocks and is operating normally.<br />All Cyber mainnet RPC endpoints are now fully operational. If you continue to experience any issues, please contact our support team.</p><p><small>Mar <var data-var='date'>11</var>, <var data-var='time'>09:51</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating an issue with Cyber mainnet. The network is stalled at block 29,896,269.<br />All Cyber mainnet RPC endpoints are currently affected. New blocks are not being produced until the network resumes.<br />Our engineering team is actively investigating and working to resolve this issue. We will provide the next update by 11am UTC or sooner.</p> tag:status.quicknode.com,2005:Incident/28903687 2026-03-11T01:00:07Z 2026-03-11T01:00:07Z [Urgent] Update ETH - Lighthouse to v8.1.2 <p><small>Mar <var data-var='date'>11</var>, <var data-var='time'>01:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'>10</var>, <var data-var='time'>17:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'>10</var>, <var data-var='time'>16:26</var> UTC</small><br><strong>Scheduled</strong> - Lighthouse v8.1.2 is a high-priority patch release with further security-critical fixes atop v8.1.1.<br /><br />This is a mandatory upgrade for all users running any prior version.</p> tag:status.quicknode.com,2005:Incident/28889647 2026-03-10T16:30:07Z 2026-03-10T16:30:07Z Scheduled: Ault Testnet - Upgrade aultd to v1.0.1 <p><small>Mar <var data-var='date'>10</var>, <var data-var='time'>16:30</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'>10</var>, <var data-var='time'>14:30</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'>10</var>, <var data-var='time'>00:26</var> UTC</small><br><strong>Scheduled</strong> - Scheduled maintenance will be performed on the Ault Testnet during the scheduled maintenance window.<br /><br />**Client Updates:**<br />• aultd: Upgrading to v1.0.1<br />• Upgrade Target Height : 7,847,200<br />• Estimated Upgrade Time: Mar 10, 2026 15:00 UTC<br />• There will be a short period of downtime (a few minutes) during the upgrade.</p> tag:status.quicknode.com,2005:Incident/28878892 2026-03-10T02:00:07Z 2026-03-10T02:00:07Z Scheduled: Base Mainnet - Upgrade base-node to v0.14.8 <p><small>Mar <var data-var='date'>10</var>, <var data-var='time'>02:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'>10</var>, <var data-var='time'>00:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>12:22</var> UTC</small><br><strong>Scheduled</strong> - Scheduled maintenance will be performed on the Base Mainnet node during the scheduled maintenance window.<br /><br />**Client Updates:**<br />- base-node: Upgrading to v0.14.8<br /><br />---<br /><br />**Release Notes Summary:**<br />**Base Node Update — RPC-Relevant Changes**<br /><br />- **Missing RPC fields fixed** — A bug causing certain RPC response fields to be absent has been resolved<br />- **WebSocket subscriptions fixed** — A race condition affecting WebSocket subscription delivery has been corrected<br /><br />---<br /><br />**Additional Information:**<br />- Full release notes: https://github.com/base/node/releases/tag/v0.14.8</p> tag:status.quicknode.com,2005:Incident/28878972 2026-03-10T00:45:56Z 2026-03-10T00:45:56Z Abstract Testnet - Network Stall <p><small>Mar <var data-var='date'>10</var>, <var data-var='time'>00:45</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>12:26</var> UTC</small><br><strong>Investigating</strong> - 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.<br />All Abstract testnet RPC endpoints are currently affected by the upstream network stall. New blocks are not being produced until the network resumes.<br />We will provide the next update by 2PM UTC or sooner as information becomes available.</p> tag:status.quicknode.com,2005:Incident/28880536 2026-03-09T16:48:11Z 2026-03-09T16:48:11Z Injective Mainnet- Network Upgrade v1.18.2 <p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>16:48</var> UTC</small><br><strong>Resolved</strong> - The Injective mainnet upgrade to v1.18.2 has been completed successfully. INJ endpoints are fully operational.</p><p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>14:04</var> UTC</small><br><strong>Investigating</strong> - 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.</p> tag:status.quicknode.com,2005:Incident/28870765 2026-03-09T04:30:07Z 2026-03-09T04:30:07Z [Standard] Scheduled: Monad Testnet - Upgrade to v0.13.0 <p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>04:30</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>03:30</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>03:02</var> UTC</small><br><strong>Scheduled</strong> - Scheduled maintenance will be performed on Monad Testnet infrastructure during the scheduled maintenance window.<br /><br />**Client Updates:**<br />- Monad: Upgrading to v0.13.0<br /><br />---<br /><br />**Upgrade Highlights:**<br /><br />RPC changes in the RPC after the v0.13.0 upgrade:<br /><br />- `latest` block tag now maps to **Proposed** blocks, instead of Voted<br />- `newHeads` and `logs` WebSocket subscriptions now stream **Voted** blocks, instead of Finalized<br />- `eth_sendRawTransactionSync` now returns the receipt from **Proposed** blocks, instead of Voted<br /><br />These changes improve the RPC polling and streaming rate by one block (~400 ms) and enhance developer and end-user experience.<br /><br />---<br /><br />**Additional Information:**<br />- Full release notes & upgrade instructions:<br /> - https://docs.monad.xyz/node-ops/upgrade-instructions/v0.13.0</p> tag:status.quicknode.com,2005:Incident/28822563 2026-03-09T02:00:07Z 2026-03-09T02:00:07Z Scheduled: Tempo Mainnet & Testnet — Upgrade Tempo to v1.4.0 <p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>02:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>00:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>08:57</var> UTC</small><br><strong>Scheduled</strong> - Scheduled maintenance will be performed during the maintenance window to upgrade the Tempo client and apply the T1C network upgrade.<br /><br />**Client Updates:**<br />- tempo: Upgrading to v1.4.0<br /><br />---<br /><br />**Release Notes Summary:**<br /><br />**T1C Network Upgrade Activation**<br />- **Moderato (testnet):** Monday, March 9 at 16:00 CET<br />- **Mainnet:** Thursday, March 12 at 16:00 CET<br /><br />**Breaking Changes After T1C Activation**<br /><br />- **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.<br />- **Key authorization `chain_id` wildcard removed:** `chain_id=0` is no longer valid. Key authorizations must specify the exact Tempo chain ID.<br />- **Precompile set updated:** Precompiles transition from Prague to Osaka at T1C activation.<br /><br />---<br /><br />**Additional Information:**<br />- Full release notes: https://github.com/tempoxyz/tempo/releases/tag/v1.4.0</p> tag:status.quicknode.com,2005:Incident/28806326 2026-03-08T19:00:07Z 2026-03-08T19:00:07Z Scheduled Maintenance — Frankfurt (FRA) Region <p><small>Mar <var data-var='date'> 8</var>, <var data-var='time'>19:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'> 8</var>, <var data-var='time'>13:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>14:28</var> UTC</small><br><strong>Scheduled</strong> - 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.</p> tag:status.quicknode.com,2005:Incident/28845611 2026-03-07T14:47:28Z 2026-03-07T14:47:28Z Sei Pacific - Elevated Latency <p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>14:47</var> UTC</small><br><strong>Resolved</strong> - After monitoring, latency on Sei Pacific has returned to normal levels. The issue has been fully resolved.<br /><br />Customers should no longer experience slower response times on RPC requests. If you continue to experience any issues, please contact our support team.</p><p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>13:06</var> UTC</small><br><strong>Monitoring</strong> - 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.<br /><br />We will provide the next update by 2PM UTC or sooner.</p><p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>12:31</var> UTC</small><br><strong>Investigating</strong> - 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.<br /><br />Our teams are actively investigating and working to restore normal performance levels. We will provide the next update by 2PM UTC or sooner.</p> tag:status.quicknode.com,2005:Incident/28833847 2026-03-06T22:19:05Z 2026-03-06T22:19:05Z Stuck Network - Hedera Testnet <p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>22:19</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>21:51</var> UTC</small><br><strong>Monitoring</strong> - The Hedera Testnet network has resumed. Our team is monitoring for stability.</p><p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>21:51</var> UTC</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>21:42</var> UTC</small><br><strong>Investigating</strong> - 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.</p> tag:status.quicknode.com,2005:Incident/28813805 2026-03-06T18:08:31Z 2026-03-06T18:08:31Z Unichain Sepolia: Network-wide stall at 45897373 <p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>18:08</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>09:21</var> UTC</small><br><strong>Update</strong> - Our engineers are closely listening to updates from the foundation on recovering flashblocks.<br /><br /><br />https://status.unichain.org/cmme2j9vf000l11emh0k10rlf</p><p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>00:00</var> UTC</small><br><strong>Monitoring</strong> - Foundation has confirmed block production has resumed without flashblocks and actively working on recovery.</p><p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>22:43</var> UTC</small><br><strong>Investigating</strong> - Unichain Sepolia has stalled network-wide at block 45,897,373. We are currently investigating and will work closely with the foundation on resolution.<br /><br />Network Explorer: https://unichain-sepolia.blockscout.com/</p> tag:status.quicknode.com,2005:Incident/28785274 2026-03-05T21:51:07Z 2026-03-05T21:51:07Z Fluent Testnet Upgrade <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>21:51</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>13:51</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>13:52</var> UTC</small><br><strong>Scheduled</strong> - We are coordinating a client upgrade for Fluent Testnet with the Fluent team.</p> tag:status.quicknode.com,2005:Incident/28786808 2026-03-05T14:00:07Z 2026-03-05T14:00:07Z Aptos upgrade to v1.41.8-hotfix (Mainnet and Testnet) <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>14:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>12:01</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>15:31</var> UTC</small><br><strong>Scheduled</strong> - We will be performing maintenance on Aptos Mainnet and Testnet<br /><br />Hotfixes include:<br />(i) Ensure consistent cache flushes within the VM (#18884)<br />(ii) Implement bounds and recursion limits (#18887)<br /><br />Configuration changes Include: <br />(i) A configuration update to set the bounds and recursion limits to appropriate values for production environments.<br /><br />See more in the official release notes: https://github.com/aptos-labs/aptos-core/releases</p> tag:status.quicknode.com,2005:Incident/28789418 2026-03-05T13:00:07Z 2026-03-05T13:00:07Z [Standard] Scheduled Maintenance: Fuel Mainnet - Gas Configuration adjustment <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>13:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>12:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>18:05</var> UTC</small><br><strong>Scheduled</strong> - Scheduled maintenance will be performed on Fuel Mainnet during the scheduled maintenance window.<br />These are simple gas configuration changes as directed by the Fuel chain team without changes to RPC.</p>