QuickNode

Affected: Robinhood - Mainnet

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-19 09:38 UTC

   The Quicknode team is investigating degraded performance of Robinhood Mainnet - we are seeing increased latency and timeouts on select RPC methods. We will update this page as we acquire new information.

2. identified 2026-10-19 10:24 UTC

   We have identified the root cause of the increased latency and timeouts affecting Robinhood Mainnet on select methods, including debug_traceBlockByNumber, eth_getBlockReceipts, eth_getLogs, and eth_getBlockByNumber. Our engineers have disabled the affected backends and are...

3. monitoring 2026-10-19 10:44 UTC

   We have replaced the affected backend infrastructure. Latency and timeouts on select RPC methods on Robinhood Mainnet have returned to normal, and affected Streams have caught up. We are continuing to monitor.

4. resolved 2026-10-19 10:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Quicknode Streams, Quicknode Webhooks

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-13 15:23 UTC

   We are investigating an issue with our internal Quicknode API that is causing authentication failures for multiple accounts. Quicknode Streams, KV Store REST API, and Webhooks are currently affected. We will update this page as we acquire new information.

2. resolved 2026-10-13 16:16 UTC

   The issue affecting our API authentication has been resolved. The incident was limited to a small number accounts. All services, including Quicknode Streams, KV Store, and Webhooks, are operating normally.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Morph - Mainnet

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-10 08:50 UTC

   We are currently investigating this issue.

2. identified 2026-10-10 09:00 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-10-10 09:05 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-10-10 22:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Morph - Mainnet

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-10 02:00 UTC

   We are currently investigating this issue.

2. identified 2026-10-10 02:15 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-10-10 03:30 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-10-10 04:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Arbitrum Nova - Mainnet

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-09 13:21 UTC

   We're investigating an issue on Arbitrum Nova where no new blocks have been produced since block 85283638. We're in contact with the Arbitrum team to understand the cause, and we'll share an update as soon as we have more information.

2. resolved 2026-10-09 13:30 UTC

   Block production on Arbitrum Nova has resumed, and our nodes are syncing normally. Thanks for your patience.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Morph - Mainnet

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-09 06:00 UTC

   We are currently investigating this issue.

2. identified 2026-10-09 06:05 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-10-09 06:15 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-10-09 06:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Solana - Mainnet

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-08 18:50 UTC

   Solana Mainnet is currently undergoing a regenesis as part of the Alpenglow upgrade. We are monitoring the process and will provide updates as more information becomes available.

2. resolved 2026-10-11 00:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: NEAR - Mainnet

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-08 16:45 UTC

   We are currently investigating the elevated API errors being served on Near Mainnet. We will post updates as we receive further information.

2. monitoring 2026-10-08 17:17 UTC

   Service has stabilized and we are monitoring for stability.

3. resolved 2026-10-08 19:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Aptos - Testnet

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-07 16:24 UTC

   The Aptos Foundation is beginning a scheduled state reset on Aptos Testnet at 17 UTC today, per AIP-147. The reset returns Testnet to a fresh genesis and clears all prior on-chain state. The Aptos Foundation expects the process to take a few hours, with up to 48 hours possible...

2. resolved 2026-10-07 23:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Injective - Mainnet

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-07 08:39 UTC

   We are currently investigating a block height stall on Injective Mainnet. Nodes stopped advancing at block 186,223,485, and requests may return stale data until block production resumes. Our team is actively working on this and we will provide an update as soon as we have more...

2. identified 2026-10-07 08:51 UTC

   The Injective Foundation has confirmed the issue and will be publishing an upgrade guide shortly. Injective Mainnet remains stalled at block 186,223,485. We will apply the upgrade to our nodes as soon as it is available and share another update once the rollout is underway.

3. monitoring 2026-10-07 10:18 UTC

   Injective Mainnet has resumed block production and our nodes are advancing past block 186,223,485 again. Requests are returning current data and the block height stall is no longer occurring. We will continue to monitor the network to confirm stability.

4. resolved 2026-10-07 13:24 UTC

   Injective Mainnet has remained stable since block production resumed, and our nodes are fully synced and serving current data. This incident is now resolved. Thank you for your patience.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: X Layer - Testnet

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-06 15:27 UTC

   X Layer Testnet appears to have stalled at block 42837767 - The Quicknode team is investigating and will update with more information once it is available.

2. identified 2026-10-06 16:59 UTC

   We have identified the cause of the X Layer Testnet network stall at block 42837767. Our engineers are currently upgrading our nodes to restore service. We will provide further updates as progress is made.

3. monitoring 2026-10-06 17:07 UTC

   Service has been restored for X Layer Testnet, and requests are being served at the current chain head. Our engineers continue to work on the affected nodes and monitor stability.

4. resolved 2026-10-07 04:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: World Chain - Mainnet

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-05 12:17 UTC

   World Chain Mainnet requests may intermittently return 503 errors. We've identified the cause as an issue in the node client affecting some of our backend nodes, and we're working with the World Chain team to resolve it. We're monitoring closely and will share updates as they...

2. identified 2026-10-05 13:32 UTC

   The World Chain team has confirmed the root cause of the intermittent 503 errors and is preparing a new node client release with a fix. We'll deploy it across our World Chain Mainnet nodes as soon as it's available. In the meantime, we're continuing to monitor closely, and some...

3. resolved 2026-10-08 18:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Blast - Sepolia

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-01 22:40 UTC

   Blast Sepolia appears to have stalled at block 43,081,817. The Quicknode team is investigating and will update with more information once it is available.

2. resolved 2026-10-01 22:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: TON - Mainnet

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-01 19:37 UTC

   The Quicknode team is investigating degraded performance of TON Mainnet - we will update this page as we acquire new information.

2. identified 2026-10-01 21:46 UTC

   The issue has been identified and working with the Ton Foundation to implement fixes.

3. identified 2026-10-02 00:52 UTC

   We are continuing to work on a fix for this issue.

4. monitoring 2026-10-02 19:41 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2026-10-03 00:29 UTC

   Since September 23, many nodes that don't forward traffic have joined TON's public overlay, the peer network our nodes use to receive blocks and pass on transactions. Because our nodes were connected to some of these peers, block sync slowed and some transactions were not...

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Injective - Mainnet

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-01 16:18 UTC

   The Quicknode team is investigating the degraded performance of Injective Mainnet - we will update this page as we acquire new information.

2. identified 2026-10-01 17:27 UTC

   We have identified the root cause of the degraded performance affecting Injective Mainnet. We will continue to monitor and provide updates as the situation improves.

3. resolved 2026-10-01 21:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-09-30 14:29 UTC

   We are investigating an elevated level of 503 errors on Hyperliquid Mainnet. We will update this page as we acquire more information.

2. resolved 2026-09-30 15:09 UTC

   The 503 errors affecting Hyperliquid Mainnet have been resolved. All backends are healthy and operating normally. We will continue to monitor the situation.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Vana - Moksha Testnet

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-09-30 12:18 UTC

   We're investigating an issue affecting Vana Moksha testnet endpoints. Our nodes have stopped syncing at block 9,268,235, so requests may return stale data. Our team is looking into the cause and we'll share an update as soon as we have more information.

2. monitoring 2026-10-01 22:03 UTC

   We're working with the foundation to recover our nodes. A fix has been applied, and our nodes are now syncing back up. We're continuing to monitor closely to ensure stability.

3. resolved 2026-10-01 23:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Stellar - Mainnet, Stellar - Testnet

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-29 18:26 UTC

   The Quicknode team is investigating the degraded performance of Stellar Mainnet and Testnet - we will update this page as we acquire new information.

2. resolved 2026-09-29 19:03 UTC

   The issue affecting Stellar Mainnet and Testnet during the v29 upgrade has been resolved. All systems are operating normally.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Zora - Mainnet

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-29 00:19 UTC

   Zora Mainnet appears to have stalled at block 51,972,862. The Quicknode team is investigating and will update with more information once it is available.

2. resolved 2026-09-29 01:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-09-28 15:11 UTC

   We are currently investigating an issue causing elevated latency and timeouts in the JFK region. We will update this page as we acquire further information.

2. identified 2026-09-28 19:03 UTC

   We have identified a network-routing issue affecting connectivity to our JFK edge location from certain network ranges. Our edge infrastructure remains healthy, but some customers may experience connection timeouts, interrupted responses, or elevated latency. We are actively...

3. resolved 2026-09-29 01:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: NEAR - Testnet

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-27 04:02 UTC

   Near Testnet appears to have stalled at block 270,420,304 - The Quicknode team is investigating and will update with more information once it is available.

2. monitoring 2026-09-27 04:42 UTC

   Block progression has resumed on Near Testnet. We are keeping a close eye on the network.

3. resolved 2026-09-27 04:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: World Chain - Mainnet

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-26 15:50 UTC

   The Quicknode team is investigating elevated 503 errors on World Chain Mainnet. Users may experience failed or degraded requests. We will update this page as we acquire new information.

2. monitoring 2026-09-26 16:10 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-09-27 04:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Fuel - Mainnet

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-09-25 18:23 UTC

   The Quicknode team is investigating the degraded performance of Fuel Mainnet - we will update this page as we acquire new information.

2. monitoring 2026-09-25 20:58 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-09-25 22:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Celestia - Mocha Testnet

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-09-24 20:43 UTC

   Celestia Mocha Testnet appears to have stalled at block 1,082,619. The Quicknode team is investigating and will update with more information once it is available.

2. monitoring 2026-09-24 21:53 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-09-24 22:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Polygon - Amoy Testnet

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-09-24 17:38 UTC

   We're experiencing an elevated level of API errors on Polygon Amoy Testnet due to an ongoing stress test by the foundation. We will update this page with further details once they become available.

2. monitoring 2026-09-24 19:39 UTC

   The Polygon Amoy Testnet stress test has concluded. We are monitoring the network for stability and will continue to update this page as needed.

3. resolved 2026-09-24 20:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Vana - Moksha Testnet

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-23 17:59 UTC

   Vana Moksha appears to have stalled at block 9,170,953 — The Quicknode team is investigating and will update with more information once it is available.

2. monitoring 2026-09-23 18:20 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-09-23 22:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Cosmos - Mainnet

Failure mode: Network, DNS, routing or connectivity failure. Root cause: An external attack. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-09-22 11:42 UTC

   Cosmos Mainnet appears to have stalled at block 33,086,740. This appears to be a chain-wide issue. The Quicknode team is investigating and will update this page as more information becomes available.

2. identified 2026-09-22 13:51 UTC

   We have identified the cause of the Cosmos Mainnet network stall at block 33,086,740. This is a chain-wide halt resulting from a network governance attack, as reported by the Cosmos Foundation. We are actively monitoring the situation and will provide further updates as more...

3. identified 2026-09-23 14:20 UTC

   Cosmos Mainnet has resumed block production following the network-wide halt. Our infrastructure is completing synchronization before resuming full service. We do not have an ETA at this time and will update this page as soon as we have more information.

4. monitoring 2026-09-23 16:24 UTC

   Cosmos Mainnet full nodes are fully operational and serving the latest blocks. Our team is continuing to restore archive availability and we are monitoring our Cosmos nodes for stability. We will provide further updates as they become available.

5. resolved 2026-09-24 16:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Arc - Testnet

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-09-21 21:43 UTC

   The Quicknode team is investigating the degraded performance of Arc Testnet. Users may experience 503 errors at this time. We will update this page as we acquire new information.

2. investigating 2026-09-22 00:49 UTC

   We are continuing to investigate on the issue.

3. monitoring 2026-09-22 01:24 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-09-22 02:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Cosmos - Mainnet

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-09-21 13:39 UTC

   Cosmos Mainnet nodes have halted at block height 33,073,000 pending a required v28.2.0 upgrade. We have reached out to the Cosmos Foundation team for the release artifacts and are working to deploy the fix as soon as it is available. We will provide further updates as the...

2. identified 2026-09-21 15:00 UTC

   The source of the issue has been determined. We are actively engaged with the Foundation to bring block progression back to normal, and additional updates will follow.

3. monitoring 2026-09-22 00:30 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-09-22 00:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-09-16 19:03 UTC

   We are investigating increased latency of Hyperliquid Mainnet - we will update this page as we acquire new information.

2. resolved 2026-09-16 19:12 UTC

   The elevated latency issue affecting Hyperliquid Mainnet has been resolved. All systems are operating normally. We will continue to monitor for any recurrence.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Base - Mainnet

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-15 20:30 UTC

   The Quicknode team is investigating the degraded performance of Base Mainnet - we will update this page as we acquire new information.

2. monitoring 2026-09-15 22:48 UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring 2026-09-15 22:48 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-09-15 23:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-09-12 21:08 UTC

   We are currently investigating intermittent packet loss in the NRT region. Users may experience 503s/ timeouts.

2. identified 2026-09-12 21:20 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-09-12 22:39 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-09-12 23:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: HyperEVM - Mainnet, Hypercore - Mainnet

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-11 14:18 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. resolved 2026-09-11 17:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Robinhood - Mainnet

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-09-10 19:18 UTC

   The Quicknode team is investigating degraded performance of RobinHood Mainnet - we will update this page as we acquire new information.

2. monitoring 2026-09-10 20:17 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-09-11 00:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Solana - Mainnet

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-10 01:31 UTC

   The Quicknode team is investigating degraded performance on Solana Mainnet. Users may be experiencing elevated 503 errors at this time. We will update this page as we acquire new information.

2. identified 2026-09-10 01:52 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-09-10 02:00 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-09-10 02:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Solana - Mainnet

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-09 20:19 UTC

   The Quicknode team is investigating the degraded performance of Solana Mainnet. Users may experience 503s at this time. We will update this page as we acquire new information.

2. monitoring 2026-09-09 20:44 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-09-09 23:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Polygon - Amoy Testnet

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-09-09 17:44 UTC

   A network stress test is scheduled by the foundation at 18 UTC, and customers may experience degraded performance and elevated API errors during this time. We will update this page as we acquire new information.

2. resolved 2026-09-09 23:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-08 23:37 UTC

   The Quicknode team is investigating degraded performance of BSC Mainnet in the FRA region. We will update this page as we acquire new information.

2. monitoring 2026-09-09 00:49 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-09-09 18:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Cosmos - Mainnet

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-09-08 18:12 UTC

   Cosmos Mainnet appears to have stalled at block 32,878,318 - The Quicknode team is investigating and will update with more information once it is available.

2. identified 2026-09-09 05:48 UTC

   The underlying issue has been identified. We are working with the Foundation to restore normal block progression. Further updates will be provided as the situation develops.

3. monitoring 2026-09-09 14:26 UTC

   Our nodes have recovered and are back at the chain tip. We are continuing to monitor the situation and will provide further updates as needed.

4. resolved 2026-09-12 00:24 UTC

   This incident has been resolved with direct communication with Cosmos Labs. Please see the Cosmos Lab's post for additional information on their binary package used to resolve this incident: https://x.com/cosmoslabs_io/status/2097986609433960711

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Solana - Testnet

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-09-08 11:28 UTC

   Solana Testnet appears to have stalled at block 440004508 — This is a chain wide stall. We are following up with the Foundation channel and working toward restoring normal block progression. Further updates will be provided as the situation develops.

2. resolved 2026-09-16 06:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-07 01:13 UTC

   Gravity Mainnet appears to have stalled at block 41,384,106. The Quicknode team is investigating and will update with more information once it is available.

2. identified 2026-09-07 07:51 UTC

   The underlying issue has been identified. We are working with the Foundation to restore normal block progression. Further updates will be provided as the situation develops.

3. resolved 2026-09-07 14:00 UTC

   This incident has been resolved. Gravity Mainnet has resumed normal block progression past block 41,384,106.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Robinhood - Mainnet

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-09-04 13:10 UTC

   We are investigating increased latency on RobinHood Mainnet. The Quicknode team has notified the foundation and will update this page as we acquire new information.

2. investigating 2026-09-04 13:23 UTC

   The RobinHood foundation team has been notified and is actively investigating, this appears to be unrelated to Quicknode. We will provide further updates as more information becomes available.

3. investigating 2026-09-04 13:53 UTC

   The RobinHood foundation team has confirmed everything has returned back to normality. Our engineering team is actively monitoring performance.

4. identified 2026-09-04 16:20 UTC

   Users may continue to experience degraded performance and issues with transaction landing on Robinhood Mainnet. We are currently investigating connection issues regarding the sequencer feed and are closely listening to updates from the foundation.

5. monitoring 2026-09-04 17:15 UTC

   The upstream feed connection issues have stabilized and we are monitoring for stability.

6. resolved 2026-09-05 01:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Injective - Mainnet

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-09-02 18:03 UTC

   The Quicknode team is investigating degraded performance of Injective Mainnet — we will update this page as we acquire new information.

2. investigating 2026-09-02 18:06 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-09-02 18:12 UTC

   The issue causing elevated errors and 503 responses on Injective Mainnet has been resolved. All systems are operating normally. We are monitoring for stability

4. resolved 2026-09-02 18:26 UTC

   The elevated errors and degraded performance affecting Injective Mainnet have been resolved. All systems are operating normally.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-08-31 15:57 UTC

   Injective Mainnet appears to have stalled chain wide at block 181,027,000. The team is investigating and will update with more information once it is available.

2. identified 2026-08-31 18:40 UTC

   We have identified a possible root cause for the Injective Mainnet block height stall. A high priority patch is being deployed, and a network-wide upgrade may be in progress. We will continue to monitor and provide updates as more information becomes available.

3. identified 2026-08-31 23:03 UTC

   Our nodes are starting to recover following the patch deployment. We'll post another update once the system is fully operational.

4. resolved 2026-09-01 00:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-08-31 07:08 UTC

   Gravity Mainnet appears to have stalled at block 39,007,386 - The Quicknode team is investigating and will update with more information once it is available.

2. identified 2026-08-31 07:26 UTC

   The underlying issue has been identified. We are working with the Foundation to restore normal block progression. Further updates will be provided as the situation develops.

3. monitoring 2026-08-31 13:41 UTC

   This continues to be an upstream issue on the Gravity network, not related to our infrastructure. Block production has partially resumed, with some nodes still catching up. We'll keep watching closely and update as the situation develops.

4. resolved 2026-08-31 14:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: ZKsync - Testnet

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-08-29 21:59 UTC

   We are currently investigating a network wide stall at block height 8,335,793.

2. investigating 2026-08-30 13:57 UTC

   We are continuing to investigate a network-wide stall at block height 8,335,793. As this is affecting the entire network, we're currently waiting on guidance from the foundation before proceeding. We'll provide updates as soon as more information becomes available.

3. resolved 2026-08-30 21:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: ZKsync - Testnet

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-08-27 13:24 UTC

   We are currently investigating degraded performance on zkSync Era Testnet, with timeouts and 503 errors. We will provide updates as more information becomes available.

2. resolved 2026-08-27 14:58 UTC

   This incident has been resolved. zkSync Sepolia is operating normally.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: HyperEVM - Testnet

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-08-27 11:42 UTC

   We've identified an upstream issue causing timeouts and 503 errors on HyperLiquid Testnet. Updates to follow.

2. resolved 2026-08-27 12:06 UTC

   This incident has been resolved. HyperLiquid - HyperEVM-Testnet is operating normally.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Affected: Stellar - Mainnet

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-08-26 14:13 UTC

   The Quicknode team is investigating the degraded performance of Stellar Mainnet JSON-RPC - we will update this page as we acquire new information.

2. monitoring 2026-08-26 14:33 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-08-27 00:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-24 12:30 UTC

   We are upgraded our Moca Testnet infrastructure to v1.4.0. This is a coordinated network upgrade that bundles a broad set of fixes across the storage, payment, and permission modules, along with a scheduled hardfork handler. During the maintenance window, brief interruptions to...

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-08-24 13:15 UTC

   This incident has been resolved. Moca Testnet is operating normally.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-08-24 13:24 UTC

   This incident has been resolved. Stacks Mainnet is operating normally.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-24 01:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-22 03:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-21 17:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-20 18:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-08-21 00:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-20 15:15 UTC

   This incident has been resolved. Archive RPC methods are operating normally across all regions. We will continue to monitor for any recurrence.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-18 16:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-23 14:10 UTC

   The issue has been resolved and Base Sepolia services are operating normally.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-17 11:18 UTC

   This incident has been resolved. Block production on Hyperliquid's testnet network has resumed and service is back to normal.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-16 12:16 UTC

   This incident has been resolved. Block production and network performance have returned to normal levels across all services.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-14 23:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-13 01:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-12 20:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-12 01:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-10 19:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-08 16:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-08 07:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-08-07 01:35 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-07 00:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-06 19:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-07 02:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-04 11:36 UTC

   This incident has been resolved. Hyperliquid Testnet is operating normally.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-03 13:28 UTC

   This incident has been resolved. Zora Mainnet is producing blocks normally.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-02 17:51 UTC

   The connectivity issues affecting the NRT region have been resolved. All systems are operating normally. We will continue to monitor for stability.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-01 20:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-31 20:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-31 17:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-31 06:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-30 16:05 UTC

   This incident has been resolved. There was a divergence in the feed for Robinhood Testnet. The Offchain team provided guidance to resolve our nodes to restore service. Additional details can be found at Robinhood Chain Status Page: https://status.robinhoodchain.offchain.io/

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-29 20:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-29 17:09 UTC

   The 503 errors affecting Flare Mainnet have been resolved and all systems are operating as expected. We will continue to monitor for stability.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-28 20:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-27 16:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-26 14:48 UTC

   This incident has been resolved and Mantle Mainnet nodes in the IAD region are fully operational. Thank you for your patience.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-26 06:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

Names an upstream provider: AWS.

1. resolved 2026-07-24 13:07 UTC

   AWS has confirmed the US-WEST-2 connectivity issue has been resolved. QuickNode services remained fully operational throughout this event, with no impact to QuickNode-hosted infrastructure. We will continue to monitor and are closing this incident.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-23 07:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-20 19:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-18 18:06 UTC

   The 503 errors affecting Robinhood Mainnet archive nodes have been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-18 02:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-18 20:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-16 01:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-15 21:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-15 01:49 UTC

   The issue affecting Fuel Sepolia has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-14 21:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-14 08:50 UTC

   Vana Mainnet is fully recovered and producing blocks normally. All affected services are operational. We'll continue to monitor for stability.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-11 15:13 UTC

   The degraded performance affecting Blast Mainnet has been resolved. All systems are operating normally.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-10 01:36 UTC

   The issue affecting BSC Testnet has been resolved. A fix was deployed using the updated bsc-reth v0.1.0-fix image, which addressed the stuck block at 118,130,133. All nodes are processing normally. We will continue to monitor for stability.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-11 14:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-09 05:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-09 05:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-07 21:31 UTC

   The Optimism Mainnet network stall at block 153924191 has been resolved. The network is advancing normally. We will continue to monitor for stability. https://status.optimism.io/cmrazrvph0am30rns9tzwb2oa

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-10 15:20 UTC

   Sui has officially marked JSON-RPC as deprecated and is requiring developers to migrate to either gRPC or GraphQL RPC by July 2026. You can read more in Sui's blogs below: https://docs.sui.io/develop/accessing-data/data-serving...

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-07 18:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-04 01:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-03 15:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-03 14:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-03 10:30 UTC

   The Mantle Sepolia network stall has been resolved. Block production has resumed and the network is operating normally. We will continue to monitor for stability.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-01 00:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-06-30 02:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-06-29 21:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-21 18:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-06-26 18:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-06-26 18:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-06-25 19:59 UTC

   The HyperEVM and Hypercore maintenance / upgrade has been completed. All systems are operating normally.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-06-25 19:33 UTC

   B3 Mainnet block production has resumed and the network stall at block 60028954 has been resolved. This incident was related to a chain-wide stall on Base Mainnet. All systems are now operating normally.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-06-25 20:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-06-25 08:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-23 02:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-19 21:07 UTC

   The QuickNode Dashboard has been restored and is operating normally.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-20 13:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-23 18:34 UTC

   The issue affecting Aleo Mainnet has been resolved. All mainnet nodes have been updated to the latest release and are fully synced with the network tip. Services are operating normally.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-18 10:47 UTC

   The upstream network maintenance affecting HyperEVM Testnet has concluded. Block production has resumed and the network is operating normally.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-18 03:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-19 08:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-15 06:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-13 17:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-13 17:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-13 17:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-11 09:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-10 16:26 UTC

   The issue with Cyber Mainnet has been resolved. Pods have fully recovered and the network is operating normally. We appreciate your patience during this time.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-10 08:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-10 16:36 UTC

   The block height stall on Ault Mainnet has been resolved. All nodes are now up to tip and operating normally.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-10 01:20 UTC

   The issue affecting HyperEVM Testnet has been resolved. 503 errors have cleared and all systems are operating normally. We will continue to monitor for any recurrence.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-09 22:32 UTC

   The 503 errors affecting Injective Mainnet have been resolved. Additional regions were added to mitigate the issue and affected nodes have been brought back online. All systems are operating normally.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-08 22:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-09 01:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-07 21:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-06 00:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-05 16:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-05 02:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-04 20:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-04 06:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-03 20:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-04 10:36 UTC

   The issue with the HyperEVM Testnet archive nodes stalling at block 55,231,856 has been resolved. A patch (nb-20260604) has been applied to the affected nodes and block height is advancing normally. We will continue to monitor for stability.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-03 19:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-02 23:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-03 00:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-03 20:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-03 06:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-06-01 18:58 UTC

   The Hemi Mainnet network stall at block 4538215 has been resolved. The Hemi Foundation identified and deployed a fix, and the network is now advancing normally. All Hemi Mainnet services are fully operational.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-30 07:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-29 18:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-29 01:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-28 23:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-28 08:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-27 18:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-26 22:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-24 02:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-23 20:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-23 20:31 UTC

   The incident has been resolved. The Billing Dashboard Metrics are now operating normally. We will continue to monitor the situation and apologize for any inconvenience caused.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-22 23:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-21 15:48 UTC

   The Injective Testnet network has resumed producing blocks. Our nodes have reconnected to peers and are advancing normally. This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-20 22:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-20 20:29 UTC

   The elevated 503 errors on Polygon Amoy Testnet observed during the scheduled load testing window (19:00–20:00 UTC) have subsided. The incident has been resolved and all systems are operating normally.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-20 19:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-20 14:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-19 18:14 UTC

   The issue causing 503 errors on HyperLiquid HyperEVM Testnet has been resolved. All systems are operating normally.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-19 16:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-18 19:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-17 03:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-16 01:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-15 17:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-20 13:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-14 16:35 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-14 18:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-14 18:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-14 07:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-13 23:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-13 02:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-19 15:21 UTC

   Service has stabilized, and 503s are back down significantly. We are still coordinating with the TON Foundation on an upstream release that provides a permanent fix, and we will roll it out once available. We will continue to monitor closely and will post a new update if impact...

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-11 19:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-11 00:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-10 14:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-10 00:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-09 22:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-09 00:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-08 22:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-08 09:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-08 09:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-08 04:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-07 23:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-07 21:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-07 21:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-05 00:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-04 03:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-09 08:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-02 01:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-01 09:01 UTC

   The issue affecting Worldchain Mainnet has been resolved. The block stall was caused by nodes requiring updates for the Jovian Hardfork that activated on May 1, 2026 at 00:00 UTC. All nodes have been updated and have caught up to the current block height. All Worldchain Mainnet...

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-29 17:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-29 19:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-29 00:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-27 23:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-28 07:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-26 17:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-24 05:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-05-02 08:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-23 08:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-22 21:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-22 21:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-21 22:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-21 04:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-21 08:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-30 18:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-19 22:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-17 23:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-16 21:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-15 15:34 UTC

   The service disruption affecting Dashboard, Streams, Webhooks, and KV REST APIs has been resolved. All platform services are fully operational. We apologize for any inconvenience this may have caused and thank you for your patience.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-14 15:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-12 16:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-10 20:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-09 22:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-09 21:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-08 12:51 UTC

   Block production on Morph Mainnet has fully resumed and nodes are synced. The issue was caused by a sequencer problem acknowledged by the Morph Foundation, who have since resolved it on their end. We will continue to monitor to confirm stability.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-08 06:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-08 00:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-05 08:00 UTC

   The HyperCore events WebSocket stream experienced intermittent interruptions due to unusually large hourly funding rate blocks, which caused the stream to stall for some consumers. Engineering deployed a fix to handle these large blocks more safely, and the stream is now stable.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-07 00:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-03 01:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-03 08:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-01 20:47 UTC

   The 0G Galileo testnet network stall has been resolved, and the chain is progressing normally again. The issue was network wide and not isolated to QuickNode. We will continue monitoring for stability.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-01 17:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-04-01 16:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-31 12:38 UTC

   The issue affecting Ink Sepolia testnet has been resolved. Backend nodes have returned to normal operation and are now passing health checks. All Ink Sepolia testnet RPC endpoints are now fully operational. If you continue to experience any issues, please contact our support...

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-30 21:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-30 13:30 UTC

   Bitcoin Cash (BCH) mainnet block production has resumed and the network is producing new blocks again. We will continue monitoring for stability.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-27 00:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-27 11:24 UTC

   The issue affecting Sonic mainnet RPC endpoints has been resolved. Our engineering team successfully completed the Sonic client upgrades to v2.1.6 and database resyncing at 00:00 UTC on 27 March. All Sonic mainnet RPC endpoints are now fully operational. If you continue to...

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-24 20:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-25 01:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-24 03:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-25 00:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-23 22:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-23 22:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-23 18:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-23 18:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-23 02:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-23 21:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-22 17:45 UTC

   This incident has now been resolved, and nodes have recovered.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-20 22:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-19 20:33 UTC

   Network block production has resumed and our nodes are operating at tip.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-19 16:53 UTC

   This incident has been resolved. A problematic block triggered degradation across affected nodes. The root cause has been identified and addressed, and all nodes are now fully synced and operating normally.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-19 06:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-18 12:13 UTC

   Block production has resumed on both Abstract Mainnet/Testnet and zkSync Era. Endpoints are operating normally and requests should be processing as expected. We will continue to monitor for any residual impact or instability.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-18 05:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-18 00:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-16 20:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-15 18:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-11 10:48 UTC

   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.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-09 16:48 UTC

   The Injective mainnet upgrade to v1.18.2 has been completed successfully. INJ endpoints are fully operational.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-10 00:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-07 14:47 UTC

   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.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-06 22:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-06 18:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-04 23:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-04 04:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-03 09:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-02 17:01 UTC

   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....

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-26 20:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-26 14:26 UTC

   After performing an upgrade, our XRP Ledger EVM infrastructure has successfully synced past block 4,688,680. Service is now operational and customers should be able to query the latest blocks and submit transactions normally. We will continue to monitor for stability.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-26 19:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-03-04 19:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-25 00:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-24 17:06 UTC

   The QuickNode team has completed the investigation and the performance has now returned to normal. We will continue to monitor for any performance issues. Please let us know if you experience any further issues.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-24 13:16 UTC

   Blockchain has caught up to tip and is functioning correctly. Our team will continue to monitor and optimize.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-24 05:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-24 00:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-24 00:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-23 17:00 UTC

   This incident has been resolved. Base Sepolia nodes are fully operational and block production has returned to normal. We appreciate your patience throughout this process and will continue to monitor the network to ensure stability is maintained.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-20 21:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-21 04:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-18 08:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-18 09:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-17 20:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-25 19:59 UTC

   Nomina (Omni Core) has been officially decommissioned and is no longer available via QuickNode RPC endpoints. All related infrastructure has been shut down.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-18 13:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-15 16:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-15 16:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-16 07:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-12 22:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-12 16:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-12 21:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-12 03:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-11 17:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-11 14:33 UTC

   The Starknet Sepolia network has resumed block production. Blocks are now progressing normally and customers should be able to query new blocks and submit transactions. We will continue to monitor for stability.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-09 22:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-24 03:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-05 15:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-05 01:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-04 20:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-01 15:06 UTC

   All affected nodes are now operational and performing as expected. Thank you for your patience during this incident.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-02-01 02:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-30 19:52 UTC

   This issue has been resolved. Solana Streams and Webhooks are now operating normally, and stream delivery is no longer experiencing delays behind the tip of the chain. We will continue to monitor to ensure ongoing stability.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-30 01:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-29 18:16 UTC

   This incident has been resolved. Tempo testnet block production has resumed and the chain is advancing normally following investigation by the Tempo foundation. We’ll continue monitoring to ensure stability.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-31 00:56 UTC

   Block 151,960,880 will remain the earliest available block until our standard pruning policy reaches its threshold at a distance of 1,832,727 blocks. Once standard pruning resumes, we will continue to retain the most recent 1,832,727 blocks as detailed in our "Node Type"...

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-28 16:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-27 06:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-26 19:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-26 00:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-23 21:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-22 04:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-22 04:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-21 23:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-21 03:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-20 23:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-18 05:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-16 20:23 UTC

   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...

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-14 15:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-14 21:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-14 21:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-14 00:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-12 17:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-13 06:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-11 20:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-11 02:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-10 07:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-09 18:55 UTC

   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...

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-09 11:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-09 02:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-07 17:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-06 16:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-05 14:49 UTC

   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.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-02 12:16 UTC

   After performing a minor update, Tempo Testnet is not operating as per usual.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-02 02:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2026-01-02 19:45 UTC

   QuickNode validator operations on Flow have been fully restored. Throughout the incident, our infrastructure team worked closely with the Flow Foundation and other network validators to safely upgrade nodes and restore services following the upstream network halt. These actions...

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-22 21:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-21 16:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-21 16:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-21 00:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-19 10:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-19 06:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-19 00:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-18 19:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-18 00:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-16 21:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-16 13:31 UTC

   No incident, made in error.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-16 15:33 UTC

   The Blast Sepolia network has resumed normal operations and block production is progressing as expected. We apologize for any inconvenience this may have caused. If you continue to experience any issues, please contact our support team.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-15 22:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-15 18:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-15 20:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-14 05:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-12 19:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-13 08:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-11 16:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-11 12:01 UTC

   The issue is now resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-12 07:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-11 09:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-10 02:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-09 13:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-09 01:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-08 15:24 UTC

   The infrastructure deployment to Ethereum mainnet has been completed successfully. All services are again operating normally. Thank you for your patience.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-07 17:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-06 05:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-06 07:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-05 12:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-05 02:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-05 00:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-04 16:12 UTC

   Polygon zkEVM stability has been restored. The client-level bug introduced by yesterday's migration update has been resolved and all services are operating normally. We continue to monitor closely to ensure the issue does not persist.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-03 16:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-02 00:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-02 01:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-12-01 14:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-30 08:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-26 22:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-26 20:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-26 19:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-26 18:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-25 13:44 UTC

   Block production has resumed on Starknet Sepolia. The network is now operating normally and processing transactions. We are monitoring the network to ensure stability.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-22 15:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-20 00:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-18 19:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-18 20:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-20 05:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-17 08:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-17 15:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-16 16:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-16 19:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-15 09:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-15 08:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-15 19:47 UTC

   Polygon Amoy has been updated with the foundation provided fix, this incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-14 05:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-13 18:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-13 00:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-12 17:00 UTC

   Over duration of maintenance period, users may experience 503 errors when using the Stacks testnet API. We will provide another update 21:00 UTC.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-10 17:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-10 15:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-08 14:16 UTC

   The Bitcoin Testnet4 Blockbook service has been fully restored. Our backends have successfully resynced and all endpoints are now operational. We apologize for the disruption and thank you for your patience.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-08 11:58 UTC

   The network has returned to normal operations. Our engineers have confirmed stability, and the issue has been fully resolved. If you continue to experience any problems, please don't hesitate to reach out.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-06 22:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-06 20:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-04 05:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-05 19:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-04 20:24 UTC

   The foundation has provided a fix, and it has been deployed across QuickNode's Berachain-Mainnet infrastructure. All nodes have synced to the tip of the network and are progressing as expected. No further customer impact is expected. Please get in touch with support for any...

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-11-03 03:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-31 07:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-30 04:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-28 12:12 UTC

   Linea mainnet new block production is restored

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-28 02:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-28 02:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-27 16:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-24 18:43 UTC

   The incident has been fully resolved, and all systems are operational. The network is stable, and block production has resumed as expected. We’ll keep light monitoring in place, but no additional impact is anticipated.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-23 04:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-22 21:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-21 09:48 UTC

   Block production on Injective Testnet has been fully restored. The Injective Foundation identified and resolved a peering issue that was preventing validators from communicating properly.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-21 09:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-20 10:04 UTC

   The issue affecting block production on Fuel Mainnet and Sepolia networks has been resolved. Both chains are now back to producing blocks normally. We apologize for any inconvenience this may have caused. If you continue to experience any issues, please don't hesitate to reach...

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-20 20:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-15 22:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-14 21:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-14 12:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-15 02:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-14 10:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-12 15:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-12 02:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-11 01:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-10 23:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-10 22:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-10 18:25 UTC

   The Solana Mainnet network has stabilized and all affected nodes are healthy and synced to the tip. The issue has been fully resolved. We’ll continue to monitor to ensure continued stability.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-08 17:00 UTC

   The cause of the service degradation was found and mitigated.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-07 19:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-07 19:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-05 22:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-05 21:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-05 06:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-03 22:40 UTC

   Uniswap foundation has marked this incident as resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-02 14:41 UTC

   The network layer connectivity issue with our upstream cloud provider affecting the APAC region has been fully resolved. All services have been restored to normal operation. We will continue to monitor closely to ensure continued stability.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-10-01 06:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-09-30 02:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.

1. resolved 2025-09-28 21:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on QuickNode's status page.