QuickNode Outage History

QuickNode degraded · 1 active incident View live status →

QuickNode had 248 outages in the last 2 years totaling 1029h 17m of downtime — averaging 10 incidents per month.

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

Source: https://status.quicknode.com

Minor July 25, 2026

Arbitrum Sepolia - Elevated 503 Errors

Detected by Pingoru
Jul 25, 2026, 05:58 PM UTC
Resolved
Jul 26, 2026, 06:09 AM UTC
Duration
12h 11m
Affected: Arbitrum - SepoliaSepolia - WebSocket APISepolia — WebhooksSepolia — Streams
Timeline · 3 updates
  1. investigating Jul 25, 2026, 05:58 PM UTC

    We're experiencing an elevated level of 503 errors and our team is currently investigating. We will update this page as more information becomes available.

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

    The elevated 503 errors on Arbitrum Sepolia have been resolved. We are monitoring the service for stability and will provide further updates if the issue recurs.

  3. resolved Jul 26, 2026, 06:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 24, 2026

Multi-Chain Disruption - AWS US-WEST-2 Upstream Issue

Detected by Pingoru
Jul 24, 2026, 12:20 PM UTC
Resolved
Jul 24, 2026, 01:07 PM UTC
Duration
47m
Timeline · 3 updates
  1. investigating Jul 24, 2026, 12:20 PM UTC

    We are aware of an ongoing issue with AWS US-WEST-2 that may be causing degraded performance or connectivity issues for customers on multiple chains in the US-WEST region. Our team is actively monitoring the situation. For reference, please see the AWS Service Health Dashboard for upstream status: https://health.aws.amazon.com/health/status We will continue to provide updates as more information becomes available.

  2. monitoring Jul 24, 2026, 12:29 PM UTC

    QuickNode's services remain fully operational. We've confirmed no impact to QuickNode-hosted infrastructure from the AWS US-WEST-2 issue. We'll continue monitoring and will update this page once AWS resolves the underlying issue.

  3. resolved Jul 24, 2026, 01:07 PM 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.

Read the full incident report →

Notice July 22, 2026

Solana Testnet — Block Height Stalled

Detected by Pingoru
Jul 22, 2026, 02:42 AM UTC
Resolved
Jul 23, 2026, 07:56 AM UTC
Duration
1d 5h
Affected: Solana - TestnetTestnet — Websockets APITestnet — StreamsTestnet — Webhooks
Timeline · 3 updates
  1. investigating Jul 22, 2026, 02:42 AM UTC

    Solana Testnet appears to have stalled at block 423,534,724 - The Quicknode team is investigating and will update with more information once it is available.

  2. identified Jul 22, 2026, 03:24 AM UTC

    This is a chain wide stalled. We are following up with the Foundation channel and working toward restoring normal block progression. Further updates will be provided as the situation develops.

  3. resolved Jul 23, 2026, 07:56 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 20, 2026

Tron-Mainnet: Degraded Performance

Detected by Pingoru
Jul 20, 2026, 05:50 PM UTC
Resolved
Jul 20, 2026, 07:22 PM UTC
Duration
1h 31m
Affected: Tron - MainnetMainnet — REST API
Timeline · 4 updates
  1. investigating Jul 20, 2026, 06:27 PM UTC

    Our team is investigating the degraded performance of Tron-Mainnet. Some users may experience 503 errors at this time. We will update this page as we acquire new information.

  2. identified Jul 20, 2026, 06:50 PM UTC

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

  3. monitoring Jul 20, 2026, 07:02 PM UTC

    Our team has deployed a fix to address the increase in 503s associated with our US-East cluster. Customers should now be seeing typical responses from their Tron endpoints. We are working to fully deploy our fix across the cluster and will continue to monitor the network. Our team will provide an update upon confirmation of stability or if further action is required within 15 minutes.

  4. resolved Jul 20, 2026, 07:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 18, 2026

Robinhood Mainnet - 503 Errors on Archive Requests

Detected by Pingoru
Jul 18, 2026, 12:00 PM UTC
Resolved
Jul 18, 2026, 06:06 PM UTC
Duration
6h 5m
Affected: Robinhood - MainnetRobinHood - Mainnet - Websocket
Timeline · 3 updates
  1. investigating Jul 18, 2026, 01:17 PM UTC

    We are investigating an issue with Robinhood Mainnet where archive requests are returning 503 errors. Our team is actively looking into the cause and will provide updates as more information becomes available.

  2. monitoring Jul 18, 2026, 01:41 PM UTC

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

  3. resolved Jul 18, 2026, 06:06 PM UTC

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

Read the full incident report →

Minor July 17, 2026

SIN Disruption - Multiple Chains Affected

Detected by Pingoru
Jul 17, 2026, 11:48 PM UTC
Resolved
Jul 18, 2026, 02:55 AM UTC
Duration
3h 6m
Affected: Optimism - MainnetBase - MainnetMainnet — Websockets APIMainnet — WebSocket APIMainnet —WebhooksMainnet — WebhooksMainnet — StreamsMainnet — StreamsOptimism - SepoliaBase - SepoliaSepolia - Websockets APISepolia - WebSocket APISepolia —WebhooksSepolia — WebhooksSepolia — StreamsSepolia — Streams
Timeline · 4 updates
  1. investigating Jul 17, 2026, 11:48 PM UTC

    We are investigating a regional outage affecting multiple chains in our Singapore (SIN) region. Users in this region may experience 503 errors or request failures. Traffic is being rerouted to alternate regions while we work to resolve the issue. We will provide updates as more information becomes available.

  2. identified Jul 18, 2026, 12:14 AM UTC

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

  3. monitoring Jul 18, 2026, 02:00 AM UTC

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

  4. resolved Jul 18, 2026, 02:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 15, 2026

XRPL EVM Testnet Network Stalled at Block 7,724,999

Detected by Pingoru
Jul 15, 2026, 01:33 PM UTC
Resolved
Jul 16, 2026, 01:35 AM UTC
Duration
12h 2m
Affected: XRPL EVM - TestnetXRPL EVM Testnet - Websockets API
Timeline · 5 updates
  1. investigating Jul 15, 2026, 01:33 PM UTC

    XRPL EVM Testnet appears to have stalled at block 7,725,000. This is an upstream issue and our team is monitoring the situation. We will provide updates as more information becomes available.

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

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

  3. investigating Jul 15, 2026, 06:21 PM UTC

    XRPL EVM Testnet appears to have stalled at block 7,724,999. Our team is investigating and we will provide updates as more information becomes available.

  4. monitoring Jul 15, 2026, 07:32 PM UTC

    Our testnet nodes have been upgraded and XRPL EVM Testnet is moving again. We are monitoring the network for continued stability.

  5. resolved Jul 16, 2026, 01:35 AM UTC

    This incident has been resolved.

Read the full incident report →

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: Blast - MainnetMainnet — 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: Fuel - Sepolia
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 - MainnetRobinHood - 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: Vana - MainnetMainnet - 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 - MainnetHyperEVM - 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: Berachain - MainnetMainnet — 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: Optimism - MainnetMainnet — 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

Sui Mainnet - JSON-RPC API Deprecation Notice

Detected by Pingoru
Jul 07, 2026, 01:29 PM UTC
Resolved
Aug 10, 2026, 03:20 PM UTC
Duration
34d 1h
Affected: Sui - Mainnet
Timeline · 2 updates
  1. monitoring Jul 07, 2026, 01:29 PM 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 https://docs.sui.io/develop/accessing-data/json-rpc-migration The good news: Quicknode has you covered with support of both gRPC and GraphQL for Sui, and we've just made gRPC even more accessible with two new additions: - gRPC-web transport support - enabling browser-based clients to connect seamlessly over port 443 - gRPC traffic now served over port 443 - simplifying firewall and infrastructure configuration If you need help getting started with gRPC or GraphQL on Quicknode, please check out our docs: https://www.quicknode.com/docs/sui

  2. resolved Aug 10, 2026, 03:20 PM 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 https://docs.sui.io/develop/accessing-data/json-rpc-migration The good news: Quicknode has you covered with support of both gRPC and GraphQL for Sui, and we've just made gRPC even more accessible with two new additions: - gRPC-web transport support - enabling browser-based clients to connect seamlessly over port 443 - gRPC traffic now served over port 443 - simplifying firewall and infrastructure configuration If you need help getting started with gRPC or GraphQL on Quicknode, please check out our docs: https://www.quicknode.com/docs/sui

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: Abstract - TestnetTestnet — 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: Mantle - SepoliaSepolia — 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: Tempo - TestnetTestnet - 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: TON - Mainnet
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 →