QuickNode Outage History

QuickNode is up right now

QuickNode had 184 outages in the last 2 years totaling 209h 46m of downtime — averaging 7.6 incidents per month.

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

Source: https://status.quicknode.com

Notice August 2, 2026

NRT Region - Connectivity Issues Affecting Multiple Chains

Detected by Pingoru
Aug 02, 2026, 03:45 PM UTC
Resolved
Aug 02, 2026, 05:51 PM UTC
Duration
2h 5m
Timeline · 2 updates
  1. investigating Aug 02, 2026, 03:45 PM UTC

    We are investigating connectivity issues affecting multiple chains in the NRT (Tokyo) region. Users in this region may experience elevated latency, timeouts, or failed requests. Traffic is being rerouted to alternate regions where possible. We will provide updates as more information becomes available.

  2. resolved Aug 02, 2026, 05:51 PM UTC

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

Read the full incident report →

Minor August 1, 2026

Sui Mainnet - Archive Degraded Performance

Detected by Pingoru
Aug 01, 2026, 02:55 PM UTC
Resolved
Aug 01, 2026, 08:56 PM UTC
Duration
6h 1m
Affected: SUI Mainnet — gRPC / JSON-RPC APISui Mainnet - gRPCSui Mainnet - GraphQL
Timeline · 3 updates
  1. investigating Aug 01, 2026, 03:09 PM UTC

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

  2. monitoring Aug 01, 2026, 03:15 PM UTC

    The degraded performance has resolved and we are monitoring for stability.

  3. resolved Aug 01, 2026, 08:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 31, 2026

BSC Mainnet - Degraded Performance

Detected by Pingoru
Jul 31, 2026, 08:29 AM UTC
Resolved
Jul 31, 2026, 05:31 PM UTC
Duration
9h 2m
Timeline · 3 updates
  1. investigating Jul 31, 2026, 08:29 AM UTC

    The Quicknode team is investigating degraded performance on BSC Mainnet following a BSC archive snapshot release — we will update this page as we acquire new information.

  2. monitoring Jul 31, 2026, 03:58 PM UTC

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

  3. resolved Jul 31, 2026, 05:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 31, 2026

World Chain Mainnet - Degraded Performance

Detected by Pingoru
Jul 31, 2026, 01:32 AM UTC
Resolved
Jul 31, 2026, 06:00 AM UTC
Duration
4h 27m
Affected: Mainnet — JSON-RPC APIMainnet — Websockets APIMainnet — StreamsMainnet — Webhooks
Timeline · 3 updates
  1. investigating Jul 31, 2026, 01:32 AM UTC

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

  2. monitoring Jul 31, 2026, 01:40 AM UTC

    The issue affecting World Chain Mainnet has been addressed and service has recovered. We are monitoring for continued stability and will provide further updates if needed.

  3. resolved Jul 31, 2026, 07:34 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 30, 2026

Robinhood Testnet : Degraded Performance

Detected by Pingoru
Jul 30, 2026, 12:06 PM UTC
Resolved
Jul 30, 2026, 04:05 PM UTC
Duration
3h 59m
Affected: Robinhood Testnet - JSON RPC APIRobinhood Testnet - WebSocket API
Timeline · 3 updates
  1. investigating Jul 30, 2026, 07:08 AM UTC

    We are currently investigating this issue.

  2. identified Jul 30, 2026, 07:14 PM UTC

    The issue has been identified and we are closely listening to the foundation for updates.

  3. resolved Jul 30, 2026, 07:16 PM 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/

Read the full incident report →

Minor July 29, 2026

Degraded Performance - Multiple Chains

Detected by Pingoru
Jul 29, 2026, 07:16 PM UTC
Resolved
Jul 29, 2026, 08:19 PM UTC
Duration
1h 2m
Timeline · 4 updates
  1. investigating Jul 29, 2026, 07:16 PM UTC

    The Quicknode team is investigating degraded performance affecting multiple chains - we will update this page as we acquire new information.

  2. investigating Jul 29, 2026, 07:30 PM UTC

    The Quicknode team is investigating degraded performance affecting multiple regions. At the moment, users may experience 503s and elevated errors on Solana archive requests in addition to multiple other affected chains. Our team is actively mitigating to restore service.

  3. monitoring Jul 29, 2026, 07:37 PM UTC

    The elevated 503 errors have been mitigated and our team is actively monitoring for stability.

  4. resolved Jul 29, 2026, 08:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 29, 2026

Flare Mainnet Degraded Performance

Detected by Pingoru
Jul 29, 2026, 03:15 PM UTC
Resolved
Jul 29, 2026, 05:09 PM UTC
Duration
1h 53m
Affected: Mainnet
Timeline · 3 updates
  1. investigating Jul 29, 2026, 03:15 PM UTC

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

  2. monitoring Jul 29, 2026, 03:23 PM UTC

    The 503 errors on Flare Mainnet have been resolved. We are monitoring the service for continued stability and will provide further updates as needed.

  3. resolved Jul 29, 2026, 05:09 PM UTC

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

Read the full incident report →

Minor July 28, 2026

JOC Mainnet - Elevated 503 Errors

Detected by Pingoru
Jul 28, 2026, 05:10 PM UTC
Resolved
Jul 28, 2026, 08:16 PM UTC
Duration
3h 6m
Affected: Mainnet — JSON-RPC APIMainnet — Websockets APIMainnet — StreamsMainnet — Webhooks
Timeline · 3 updates
  1. investigating Jul 28, 2026, 05:10 PM UTC

    The Quicknode team is investigating elevated 503 errors on JOC Mainnet - we will update this page as we acquire new information.

  2. monitoring Jul 28, 2026, 05:22 PM UTC

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

  3. resolved Jul 28, 2026, 08:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 27, 2026

Celo Mainnet 503 Errors

Detected by Pingoru
Jul 27, 2026, 03:02 PM UTC
Resolved
Jul 27, 2026, 04:00 PM UTC
Duration
58m
Affected: Mainnet — JSON-RPC APIMainnet — WebSocket APIMainnet — WebhooksMainnet — Streams
Timeline · 3 updates
  1. identified Jul 27, 2026, 03:02 PM UTC

    We’re currently investigating intermittent `503` errors impacting Celo Mainnet requests. Our team has identified the issue and is working to restore normal service as quickly as possible. We’ll continue monitoring and provide updates as soon as more information is available. Thank you for your patience.

  2. monitoring Jul 27, 2026, 03:41 PM UTC

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

  3. resolved Jul 27, 2026, 06:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 26, 2026

Mantle Mainnet Degraded Performance

Detected by Pingoru
Jul 26, 2026, 10:23 AM UTC
Resolved
Jul 26, 2026, 02:48 PM UTC
Duration
4h 24m
Affected: Mainnet — JSON-RPC APIMainnet — Websockets APIMainnet — StreamsMainnet — Webhooks
Timeline · 3 updates
  1. investigating Jul 26, 2026, 10:23 AM UTC

    We are investigating an issue causing 503 errors and degraded performance for Mantle Mainnet in the IAD region. Some requests may fail or experience elevated latency during this time. We will share updates as we have more information.

  2. monitoring Jul 26, 2026, 11:22 AM UTC

    The issue affecting Mantle Mainnet nodes in the IAD region has been resolved and services have returned to normal. We are continuing to monitor to ensure full stability.

  3. resolved Jul 26, 2026, 02:48 PM UTC

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

Read the full incident report →

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: Sepolia - JSON RPCSepolia - 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: Testnet — JSON-RPC APITestnet — 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: Mainnet — JSON-RPC APIMainnet — 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 - Mainnet - JSON RPCRobinHood - 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: Mainnet — JSON-RPC APIMainnet — JSON-RPC APIMainnet — Websockets APIMainnet — WebSocket APIMainnet —WebhooksMainnet — WebhooksMainnet — StreamsMainnet — StreamsSepolia - JSON RPCSepolia - JSON-RPC APISepolia - 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 Testnet - JSON RPC APIXRPL 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: 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 →