QuickNode Outage History

QuickNode is up right now

QuickNode had 192 outages in the last 2 years totaling 711h 27m of downtime — averaging 7.9 incidents per month.

There were 192 QuickNode outages since March 6, 2026 totaling 711h 27m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.quicknode.com

Minor July 15, 2026

Blast Mainnet - Degraded Performance

Detected by Pingoru
Jul 15, 2026, 11:09 AM UTC
Resolved
Jul 15, 2026, 09:58 PM UTC
Duration
10h 48m
Affected: Mainnet — JSON-RPC APIMainnet — WebSocket APIMainnet — WebhooksMainnet — Streams
Timeline · 3 updates
  1. investigating Jul 15, 2026, 11:09 AM UTC

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

  2. monitoring Jul 15, 2026, 06:01 PM UTC

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

  3. resolved Jul 15, 2026, 09:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 14, 2026

Fuel Sepolia Network Stalled at Block 67926698

Detected by Pingoru
Jul 14, 2026, 09:00 PM UTC
Resolved
Jul 15, 2026, 01:49 AM UTC
Duration
4h 48m
Affected: Sepolia — GraphQL API
Timeline · 3 updates
  1. investigating Jul 14, 2026, 09:00 PM UTC

    Fuel Sepolia appears to have stalled at block 67926698. The Quicknode team is investigating and will update with more information once it is available.

  2. identified Jul 14, 2026, 09:28 PM UTC

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

  3. resolved Jul 15, 2026, 01:49 AM UTC

    The issue affecting Fuel Sepolia has been resolved.

Read the full incident report →

Minor July 14, 2026

Robinhood Mainnet Degraded Performance

Detected by Pingoru
Jul 14, 2026, 03:58 PM UTC
Resolved
Jul 14, 2026, 09:21 PM UTC
Duration
5h 23m
Affected: RobinHood - Mainnet - JSON RPCRobinHood - Mainnet - Websocket
Timeline · 3 updates
  1. investigating Jul 14, 2026, 03:58 PM UTC

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

  2. monitoring Jul 14, 2026, 05:45 PM UTC

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

  3. resolved Jul 14, 2026, 09:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 14, 2026

Vana Mainnet Network Stalled at Block 9228400

Detected by Pingoru
Jul 14, 2026, 03:00 AM UTC
Resolved
Jul 14, 2026, 08:50 AM UTC
Duration
5h 49m
Affected: Mainnet - JSON-RPC APIMainnet - Websockets APIMainnet — StreamsMainnet — Webhooks
Timeline · 4 updates
  1. investigating Jul 13, 2026, 08:36 PM UTC

    Vana Mainnet appears to have stalled at block 9228400. The Quicknode team is investigating and will update with more information once it is available.

  2. identified Jul 14, 2026, 06:20 AM UTC

    Our engineers are closely working with the foundation to restore the node infrastructure.

  3. monitoring Jul 14, 2026, 06:22 AM UTC

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

  4. resolved Jul 14, 2026, 08:50 AM UTC

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

Read the full incident report →

Notice July 9, 2026

BSC Testnet - 503 Errors

Detected by Pingoru
Jul 09, 2026, 02:31 PM UTC
Resolved
Jul 10, 2026, 01:36 AM UTC
Duration
11h 4m
Timeline · 4 updates
  1. investigating Jul 09, 2026, 02:31 PM UTC

    We are investigating an issue with BSC Testnet that is causing 503 errors. We will update this page as we acquire new information.

  2. identified Jul 09, 2026, 10:58 PM UTC

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

  3. monitoring Jul 10, 2026, 01:14 AM UTC

    A fix has been identified using bsc-reth v0.1.0-fix, which resolves the stuck block issue at block 118,130,132. Nodes are being upgraded and are processing normally. We are monitoring BSC Testnet for continued stability.

  4. resolved Jul 10, 2026, 01:36 AM 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.

Read the full incident report →

Minor July 9, 2026

HyperEVM NRT Region - 503 Errors

Detected by Pingoru
Jul 09, 2026, 02:25 PM UTC
Resolved
Jul 11, 2026, 02:24 PM UTC
Duration
1d 23h
Affected: HyperEVM - JSON-RPC APIHyperEVM - Websockets APIHyperEVM - StreamsHyperEVM - Webhooks
Timeline · 3 updates
  1. investigating Jul 09, 2026, 02:25 PM UTC

    We are investigating an increase in 503 errors affecting HyperEVM in the NRT (Tokyo) region. Users in this region may experience failed or degraded requests. We will provide updates as our investigation progresses.

  2. monitoring Jul 09, 2026, 02:26 PM UTC

    Additional backend nodes have been added to the NRT region. We are monitoring the situation to confirm stability and will provide further updates as needed.

  3. resolved Jul 11, 2026, 02:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 8, 2026

Berachain Mainnet Network Stalled at Block 23,259,488

Detected by Pingoru
Jul 08, 2026, 07:03 PM UTC
Resolved
Jul 09, 2026, 05:34 AM UTC
Duration
10h 31m
Affected: Mainnet — JSON-RPC APIMainnet — WebSocket APIMainnet — StreamsMainnet — Webhooks
Timeline · 3 updates
  1. investigating Jul 08, 2026, 07:03 PM UTC

    Berachain Mainnet appears to have stalled at block 23,259,488. The QuickNode team is investigating and will update with more information once it is available.

  2. monitoring Jul 08, 2026, 08:32 PM UTC

    Our engineers have successfully unwound the affected nodes past the stalled block and syncing has resumed. We are monitoring Berachain Mainnet for continued stability and will provide further updates as needed.

  3. resolved Jul 09, 2026, 05:34 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 8, 2026

Elevated 503 Errors - US-East Region

Detected by Pingoru
Jul 08, 2026, 06:11 PM UTC
Resolved
Jul 09, 2026, 05:30 AM UTC
Duration
11h 19m
Timeline · 4 updates
  1. investigating Jul 08, 2026, 05:22 PM UTC

    We are investigating elevated 503 errors affecting our US-East region. Multiple chains may be impacted. Our team is actively investigating and will provide updates as more information becomes available.

  2. identified Jul 08, 2026, 06:11 PM UTC

    We have identified the root cause of the elevated 503 errors in the US-East region. Our engineers are actively working on recovery. We will continue to monitor and provide updates as the situation progresses.

  3. monitoring Jul 08, 2026, 06:37 PM UTC

    The elevated errors affecting chains in the US-Region has been addressed. Our team is monitoring for stability.

  4. resolved Jul 09, 2026, 05:30 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 7, 2026

Optimism Mainnet Network Stalled at Block 153924191

Detected by Pingoru
Jul 07, 2026, 06:11 PM UTC
Resolved
Jul 07, 2026, 09:31 PM UTC
Duration
3h 19m
Affected: Mainnet — JSON-RPC APIMainnet — Websockets APIMainnet — WebhooksMainnet — Streams
Timeline · 3 updates
  1. investigating Jul 07, 2026, 06:11 PM UTC

    Optimism Mainnet appears to have stalled at block 153924191. The QuickNode team is investigating and will update this page as more information becomes available.

  2. monitoring Jul 07, 2026, 06:27 PM UTC

    Optimism Mainnet block height is advancing again. We are monitoring the network for continued stability and will provide further updates if needed.

  3. resolved Jul 07, 2026, 09:31 PM UTC

    The Optimism Mainnet network stall at block 153924191 has been resolved. The network is advancing normally. We will continue to monitor for stability.

Read the full incident report →

Notice July 7, 2026

Degraded Performance on US-EAST region

Detected by Pingoru
Jul 07, 2026, 05:59 AM UTC
Resolved
Jul 07, 2026, 06:39 PM UTC
Duration
12h 40m
Timeline · 4 updates
  1. investigating Jul 07, 2026, 05:59 AM UTC

    The Quicknode team is investigating the degraded performance in the US-EAST region. You may see increased error rates, response times, or timeouts while we work to resolve this. We will provide an update as more information becomes available.

  2. identified Jul 07, 2026, 06:32 AM UTC

    The Quicknode team has identified the issue is realted to the upstream provider network upgrade. Our US-EAST degraded performance issue should be mitigated. We are actively monitoring this and will provide an update as we acquire new information.

  3. monitoring Jul 07, 2026, 08:10 AM UTC

    The degraded performance issue has been mitigated. The Quicknode team is continuing to monitor performance to ensure stability.

  4. resolved Jul 07, 2026, 06:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 3, 2026

Intermittent Bitcoin Blockbook Stale Data Served

Detected by Pingoru
Jul 03, 2026, 04:33 PM UTC
Resolved
Jul 04, 2026, 01:21 AM UTC
Duration
8h 48m
Affected: Mainnet — Blockbook RPC Add-On
Timeline · 3 updates
  1. investigating Jul 03, 2026, 08:33 PM UTC

    We are investigating stale block data being served from the Blockbook service, specifically for `bb_getblock`. Our team will update this page as more information becomes available to us.

  2. monitoring Jul 03, 2026, 09:19 PM UTC

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

  3. resolved Jul 04, 2026, 01:21 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 3, 2026

Aleo Mainnet Degraded Performance

Detected by Pingoru
Jul 03, 2026, 04:20 PM UTC
Resolved
Jul 03, 2026, 06:29 PM UTC
Duration
2h 9m
Timeline · 1 update
  1. investigating Jul 03, 2026, 04:20 PM UTC

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

Read the full incident report →

Minor July 3, 2026

Abstract Testnet Network Stalled at Block 18,145,825

Detected by Pingoru
Jul 03, 2026, 03:28 PM UTC
Resolved
Jul 03, 2026, 03:30 PM UTC
Duration
2m
Affected: Testnet — JSON-RPC APITestnet — WebSocket APITestnet — Webhooks
Timeline · 2 updates
  1. investigating Jul 03, 2026, 03:28 PM UTC

    Abstract Testnet appears to have stalled at block 18,145,825. The QuickNode team is investigating and will update with more information once it is available.

  2. resolved Jul 03, 2026, 03:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 3, 2026

Abstract Mainnet Network Stalled at Block 72,953,577

Detected by Pingoru
Jul 03, 2026, 02:14 PM UTC
Resolved
Jul 03, 2026, 02:39 PM UTC
Duration
24m
Timeline · 2 updates
  1. investigating Jul 03, 2026, 02:14 PM UTC

    Abstract Mainnet appears to have stalled at block 72,953,577. Matter Labs is currently performing database maintenance. The Quicknode team will update with more information once it is available.

  2. resolved Jul 03, 2026, 02:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 3, 2026

Mantle Sepolia Network Stalled at Block 40763249

Detected by Pingoru
Jul 03, 2026, 09:54 AM UTC
Resolved
Jul 03, 2026, 10:30 AM UTC
Duration
36m
Affected: Sepolia — JSON-RPC APISepolia — Websockets APISepolia — StreamsSepolia — Webhooks
Timeline · 2 updates
  1. investigating Jul 03, 2026, 09:54 AM UTC

    Mantle Sepolia appears to have stalled at block 40763249. The QuickNode team is investigating and has notified the Mantle Foundation. We will update this page as we acquire new information.

  2. resolved Jul 03, 2026, 10:30 AM 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.

Read the full incident report →

Minor June 30, 2026

Tempo Testnet - Degraded Performance

Detected by Pingoru
Jun 30, 2026, 02:53 PM UTC
Resolved
Jul 01, 2026, 12:58 AM UTC
Duration
10h 4m
Affected: Testnet - JSON-RPC APITestnet - Websockets API
Timeline · 4 updates
  1. investigating Jun 30, 2026, 02:53 PM UTC

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

  2. identified Jun 30, 2026, 03:40 PM UTC

    We have identified the root cause of the degraded performance on Tempo Testnet. All affected nodes are being recovered via a cross-region copy. We will post another update once recovery is complete.

  3. monitoring Jun 30, 2026, 04:31 PM UTC

    All affected nodes have been recovered and services are operating normally. We are monitoring Tempo Testnet for stability ahead of a planned stress test at 22:00 UTC. We will continue to provide updates as needed.

  4. resolved Jul 01, 2026, 12:58 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 30, 2026

TON Mainnet - Degraded Performance

Detected by Pingoru
Jun 30, 2026, 01:28 AM UTC
Resolved
Jun 30, 2026, 02:05 AM UTC
Duration
37m
Affected: Mainnet — REST API
Timeline · 2 updates
  1. investigating Jun 30, 2026, 01:28 AM UTC

    The QuickNode team is investigating the degraded performance of TON Mainnet API. Some users many experience 503s at this time. We will update this page as we acquire new information.

  2. resolved Jun 30, 2026, 02:05 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 29, 2026

Flow Testnet: EVM Block Height stalled at 118,361,371

Detected by Pingoru
Jun 29, 2026, 07:58 PM UTC
Resolved
Jun 29, 2026, 09:26 PM UTC
Duration
1h 27m
Affected: Testnet — REST APITestnet — WebhooksTestnet — Streams
Timeline · 2 updates
  1. investigating Jun 29, 2026, 07:58 PM UTC

    Flow Testnet EVM (JSON-RPC API) nodes stalled at block height 118,361,371. Our team is actively investigating and will provide an update once more information becomes available.

  2. resolved Jun 29, 2026, 09:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 28, 2026

Ethereum Hoodi Testnet - Degraded Performance

Detected by Pingoru
Jun 28, 2026, 10:04 PM UTC
Resolved
Jul 21, 2026, 06:15 PM UTC
Duration
22d 20h
Affected: Hoodi - JSON-RPC APIHoodi - Websockets APIHoodi — WebhooksHoodi - Beacon REST APIHoodi - Streams
Timeline · 4 updates
  1. investigating Jun 28, 2026, 10:04 PM UTC

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

  2. identified Jun 29, 2026, 06:53 AM UTC

    The Quicknode team has identified the root cause of the recent degradation affecting the Ethereum Hoodi nodes. Currently, the historical blob data for Ethereum Hoodi nodes is limited to slots >= 3,375,000. Requests for blob data prior to this slot may be temporarily unavailable. We are working on restoring complete historical blob coverage and will keep this page updated as the work progresses.

  3. monitoring Jul 21, 2026, 12:57 PM UTC

    Historical blob data for Ethereum Hoodi nodes prior to slot 3,375,000 is now being served correctly, resolving the previous limitation. Full historical blob coverage has been restored. A fix has been implemented and we are monitoring the results to confirm full stability.

  4. resolved Jul 21, 2026, 06:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 26, 2026

Hedera Testnet - Elevated 503 Errors

Detected by Pingoru
Jun 26, 2026, 05:34 PM UTC
Resolved
Jun 26, 2026, 06:39 PM UTC
Duration
1h 4m
Affected: Testnet - JSON-RPC APITestnet - REST APITestnet — StreamsTestnet — Webhooks
Timeline · 3 updates
  1. investigating Jun 26, 2026, 05:34 PM UTC

    We are investigating an issue with Hedera Testnet resulting in elevated 503 errors. Users may experience failed or interrupted requests. Our team is actively investigating and will provide updates as more information becomes available.

  2. monitoring Jun 26, 2026, 05:53 PM UTC

    We have identified the root cause of the elevated 503 errors on Hedera Testnet. The issue was caused by rate limiting (429s) on an upstream node. The affected node has been addressed and service has been restored. We are monitoring for continued stability.

  3. resolved Jun 26, 2026, 06:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 26, 2026

Base Mainnet Chain-Wide Stall

Detected by Pingoru
Jun 26, 2026, 03:37 PM UTC
Resolved
Jun 26, 2026, 06:38 PM UTC
Duration
3h
Affected: Mainnet — JSON-RPC APIMainnet — JSON-RPC APIMainnet — WebSocket APIMainnet — WebSocket APIMainnet —WebhooksMainnet — StreamsMainnet — StreamsMainnet — Webhooks
Timeline · 3 updates
  1. investigating Jun 26, 2026, 03:37 PM UTC

    Base Mainnet is experiencing a chain-wide stall. The Quicknode team is investigating and will update this page as more information becomes available. For reference, please see the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

  2. monitoring Jun 26, 2026, 04:03 PM UTC

    Nodes have been restarted and the chain stall has been resolved. 503 errors are no longer observed. We are monitoring the service for continued stability as backfill requests normalize.

  3. resolved Jun 26, 2026, 06:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 25, 2026

HyperEVM & Hypercore gRPC Maintenance / Upgrade

Detected by Pingoru
Jun 25, 2026, 04:54 PM UTC
Resolved
Jun 25, 2026, 07:59 PM UTC
Duration
3h 4m
Affected: HyperEVM - JSON-RPC APIHyperEVM - Websockets APIHyperEVM - StreamsHyperEVM - WebhooksHyperEVM-Testnet - JSON-RPC APIHypercore - JSON-RPC APIHypercore - Websockets APIHypercore - StreamsHypercore - WebhooksHypercore - gRPC
Timeline · 2 updates
  1. investigating Jun 25, 2026, 04:54 PM UTC

    We are currently performing maintenance and an upgrade on HyperEVM and Hypercore gRPC. Users may experience disruptions during this time. We will provide updates as the work progresses.

  2. resolved Jun 25, 2026, 07:59 PM UTC

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

Read the full incident report →

Notice June 25, 2026

B3 Mainnet Network Stalled at Block 60028954

Detected by Pingoru
Jun 25, 2026, 04:42 PM UTC
Resolved
Jun 25, 2026, 07:33 PM UTC
Duration
2h 50m
Affected: Mainnet — JSON-RPC APIMainnet — WebSocket APIMainnet — StreamsMainnet — Webhooks
Timeline · 2 updates
  1. investigating Jun 25, 2026, 04:42 PM UTC

    B3 Mainnet appears to have stalled at block 60028954 due to a chain-wide stall on Base Mainnet, which B3 depends on. The QuickNode team is investigating and will update this page as more information becomes available. For Base Mainnet status, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

  2. resolved Jun 25, 2026, 07:33 PM 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.

Read the full incident report →

Minor June 25, 2026

Base Mainnet Block Production Disruption

Detected by Pingoru
Jun 25, 2026, 04:07 PM UTC
Resolved
Jun 25, 2026, 08:36 PM UTC
Duration
4h 29m
Affected: Mainnet — JSON-RPC APIMainnet — WebSocket APIMainnet —WebhooksMainnet — Streams
Timeline · 5 updates
  1. investigating Jun 25, 2026, 04:07 PM UTC

    Base Mainnet block production is currently unhealthy during the activation of the Beryl Upgrade. For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

  2. identified Jun 25, 2026, 05:04 PM UTC

    The Base Team has identified the issue with a problematic block interfering with subsequent block building. Their team is working on several threads to remediate. We will provide further updates as the situation develops. For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

  3. identified Jun 25, 2026, 05:28 PM UTC

    The Base team is continuing to debug and have isolated a consensus problem that caused an invalid block to be sequenced. This prevented new blocks from being created following block 47806542. The Base team is working on a fix to resume block propagation to the network while further isolating the root cause of the problematic block. For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

  4. monitoring Jun 25, 2026, 06:46 PM UTC

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

  5. resolved Jun 25, 2026, 08:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 25, 2026

Degraded Performance - Ethereum Mainnet Archived Request

Detected by Pingoru
Jun 25, 2026, 07:49 AM UTC
Resolved
Jun 25, 2026, 08:41 AM UTC
Duration
51m
Affected: Mainnet — JSON-RPC APIMainnet — Websockets API
Timeline · 3 updates
  1. investigating Jun 25, 2026, 07:49 AM UTC

    The Quicknode team is investigating the degraded performance of Ethereum mainnet archived nodes. Customers may experience increased error rates, including 503 responses, when querying archive data. We will update this page as we acquire new information.

  2. identified Jun 25, 2026, 08:14 AM UTC

    The underlying issue has been identified, and a mitigation is in place. Some nodes have recovered, and 503s have been mitigated. Quicknode teams are continuing to work to recover full capacity and monitor performance to ensure stability.

  3. resolved Jun 25, 2026, 08:41 AM UTC

    This incident has been resolved.

Read the full incident report →