QuickNode

Affected: Robinhood - Mainnet

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

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: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: 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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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.

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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

   We are currently investigating degraded performance on Solana Mainnet. Customers may experience increased latency and 503 errors. Streams and Webhooks are also affected and may see delayed deliveries.

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

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

3. monitoring 2026-10-01 02:06 UTC

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

4. resolved 2026-10-01 02:27 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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with high confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: Security incident or emergency response to a vulnerability. Root cause: An external attack. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: 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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with high confidence (taxonomy v0.2).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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.