QuickNode Outage History

QuickNode degraded · 1 active incident View live status →

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

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

Source: https://status.quicknode.com

Notice August 17, 2026

Hyperliquid EVM Testnet, Service Disruption

Detected by Pingoru
Aug 17, 2026, 10:40 AM UTC
Resolved
Aug 17, 2026, 11:18 AM UTC
Duration
37m
Affected: HyperEVM - Testnet
Timeline · 2 updates
  1. investigating Aug 17, 2026, 10:40 AM UTC

    We've identified an outage affecting Hyperliquid EVM Testnet. The root cause is an upstream stall on Hyperliquid's testnet network infrastructure, unrelated to QuickNode services. Users may experience failed or timed-out RPC requests until the upstream network resumes. We will continue monitoring and provide updates as they become available.

  2. resolved Aug 17, 2026, 11:18 AM UTC

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

Read the full incident report →

Notice August 16, 2026

Stacks mainnet (STX) , Degraded Performance

Detected by Pingoru
Aug 16, 2026, 11:05 AM UTC
Resolved
Aug 16, 2026, 12:16 PM UTC
Duration
1h 10m
Affected: Stacks - MainnetMainnet — Websockets API
Timeline · 3 updates
  1. investigating Aug 16, 2026, 11:05 AM UTC

    We are currently investigating a degradation affecting Stacks mainnet. Users may experience elevated response times and intermittent 503 errors. Our team is actively investigating and will provide updates as more information becomes available.

  2. identified Aug 16, 2026, 11:27 AM UTC

    We identified what appears to have been an upstream issue on the Stacks network side that caused a temporary halt in block production. Block production has since resumed, and we are no longer observing degradation at this time. We will continue investigating and will share more information as it becomes available.

  3. resolved Aug 16, 2026, 12:16 PM UTC

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

Read the full incident report →

Minor August 14, 2026

Arbitrum Mainnet Degraded Performance - SIN Region

Detected by Pingoru
Aug 14, 2026, 05:30 PM UTC
Resolved
Aug 14, 2026, 11:14 PM UTC
Duration
5h 44m
Affected: Arbitrum - Mainnet NitroMainnet Nitro — WebSocket APIMainnet — WebhooksMainnet — Streams
Timeline · 3 updates
  1. investigating Aug 14, 2026, 05:39 PM UTC

    The Quicknode team is investigating the degraded performance of Arbitrum Mainnet in the Singapore (SIN) region - users may experience intermittent 503 errors. We will update this page as we acquire new information.

  2. monitoring Aug 14, 2026, 05:59 PM UTC

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

  3. resolved Aug 14, 2026, 11:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 12, 2026

Flare Mainnet Degraded Performance - Sporadic 503 Errors

Detected by Pingoru
Aug 12, 2026, 03:42 PM UTC
Resolved
Aug 13, 2026, 01:08 AM UTC
Duration
9h 25m
Affected: Flare - Mainnet
Timeline · 4 updates
  1. investigating Aug 12, 2026, 03:42 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 Aug 12, 2026, 08:35 PM UTC

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

  3. monitoring Aug 12, 2026, 08:35 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Aug 13, 2026, 01:08 AM UTC

    This incident has been resolved.

Read the full incident report →

Major August 12, 2026

Performance degradation affecting several chains in the EU region

Detected by Pingoru
Aug 12, 2026, 04:00 AM UTC
Resolved
Aug 12, 2026, 08:35 PM UTC
Duration
16h 35m
Timeline · 4 updates
  1. investigating Aug 12, 2026, 04:13 AM UTC

    We are currently investigating this issue.

  2. identified Aug 12, 2026, 04:31 AM UTC

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

  3. monitoring Aug 12, 2026, 05:09 AM UTC

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

  4. resolved Aug 12, 2026, 08:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 11, 2026

Sui Mainnet Degraded Performance - FRA Region

Detected by Pingoru
Aug 11, 2026, 04:32 PM UTC
Resolved
Aug 12, 2026, 01:25 AM UTC
Duration
8h 53m
Affected: Sui - MainnetSui Mainnet - gRPCSui Mainnet - GraphQL
Timeline · 3 updates
  1. investigating Aug 11, 2026, 04:32 PM UTC

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

  2. monitoring Aug 11, 2026, 05:06 PM UTC

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

  3. resolved Aug 12, 2026, 01:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 10, 2026

Story mainnet : Block height stalled at 20,818,218

Detected by Pingoru
Aug 10, 2026, 12:12 PM UTC
Resolved
Aug 10, 2026, 07:00 PM UTC
Duration
6h 47m
Affected: Story - MainnetMainnet — Websockets APIMainnet — StreamsMainnet — Webhooks
Timeline · 3 updates
  1. investigating Aug 10, 2026, 12:12 PM UTC

    We are currently investigating an issue where Story mainnet has stalled at block height 20,818,218. We'll provide an update as soon as we have more information.

  2. monitoring Aug 10, 2026, 06:48 PM UTC

    A fix has been implemented for the Story mainnet block height stall at block 20,818,218, and we are monitoring the results. We will provide another update once we confirm the network is stable.

  3. resolved Aug 11, 2026, 12:14 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 8, 2026

Solana Mainnet - Intermittent 503 Errors

Detected by Pingoru
Aug 08, 2026, 02:14 PM UTC
Resolved
Aug 08, 2026, 04:49 PM UTC
Duration
2h 34m
Affected: Solana - MainnetMainnet — Websockets APIMainnet — StreamsMainnet — Webhooks
Timeline · 3 updates
  1. investigating Aug 08, 2026, 02:14 PM UTC

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

  2. monitoring Aug 08, 2026, 02:35 PM UTC

    The intermittent 503s on Solana Mainnet have resolved. The AMS, FRA, SIN, and NRT regions observed the intermittent 503s. We are monitoring for stability.

  3. resolved Aug 08, 2026, 04:49 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 8, 2026

Stellar mainnet : Horizon API degraded performance

Detected by Pingoru
Aug 08, 2026, 06:30 AM UTC
Resolved
Aug 08, 2026, 07:00 AM UTC
Duration
29m
Affected: Mainnet - REST APIStellar - Mainnet
Timeline · 4 updates
  1. investigating Aug 08, 2026, 06:45 AM UTC

    We are currently investigating this issue.

  2. identified Aug 08, 2026, 08:08 AM UTC

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

  3. monitoring Aug 08, 2026, 08:08 AM UTC

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

  4. resolved Aug 08, 2026, 08:08 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 7, 2026

Robinhood Mainnet - Degraded

Detected by Pingoru
Aug 07, 2026, 12:41 AM UTC
Resolved
Aug 07, 2026, 01:35 AM UTC
Duration
53m
Affected: Robinhood - MainnetRobinHood - Mainnet - Websocket
Timeline · 5 updates
  1. investigating Aug 07, 2026, 12:41 AM UTC

    The Quicknode team is currently investigating degraded performance on Robinhood Mainnet in the JFK/EWR region.

  2. monitoring Aug 07, 2026, 12:48 AM UTC

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

  3. monitoring Aug 07, 2026, 12:49 AM UTC

    All regions remain healthy and will continue to monitor.

  4. monitoring Aug 07, 2026, 12:54 AM UTC

    All regions remain healthy and will continue to monitor.

  5. resolved Aug 07, 2026, 01:35 AM UTC

    This issue has been resolved.

Read the full incident report →

Minor August 6, 2026

Solana Mainnet - gRPC Degraded Performance (JFK)

Detected by Pingoru
Aug 06, 2026, 09:19 PM UTC
Resolved
Aug 07, 2026, 12:17 AM UTC
Duration
2h 57m
Affected: Solana - MainnetMainnet — Websockets APIMainnet — StreamsMainnet — Webhooks
Timeline · 3 updates
  1. investigating Aug 06, 2026, 09:19 PM UTC

    The Quicknode team is investigating the degraded performance of Solana Mainnet gRPC in the JFK region - we will update this page as we acquire new information.

  2. monitoring Aug 06, 2026, 09:57 PM UTC

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

  3. resolved Aug 07, 2026, 12:17 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 6, 2026

Sui Mainnet - Archive Degradation

Detected by Pingoru
Aug 06, 2026, 06:39 PM UTC
Resolved
Aug 06, 2026, 07:39 PM UTC
Duration
59m
Affected: Sui - MainnetSui Mainnet - gRPCSui Mainnet - GraphQL
Timeline · 4 updates
  1. investigating Aug 06, 2026, 06:39 PM UTC

    Our team is investigating degradation on Sui Mainnet archive nodes.

  2. identified Aug 06, 2026, 07:01 PM UTC

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

  3. monitoring Aug 06, 2026, 07:20 PM UTC

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

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

    This incident has been resolved.

Read the full incident report →

Minor August 6, 2026

Polygon Amoy Testnet , Elevated Network Load (Scheduled Stress Test)

Detected by Pingoru
Aug 06, 2026, 12:59 PM UTC
Resolved
Aug 07, 2026, 02:00 AM UTC
Duration
13h 1m
Affected: Polygon - Amoy TestnetAmoy — Websockets APIAmoy — WebhooksAmoy — Streams
Timeline · 4 updates
  1. investigating Aug 06, 2026, 12:42 PM UTC

    Polygon Labs is running load/stress testing on Amoy Testnet starting at 12:00 PM UTC today. You may experience higher-than-usual latency or elevated network load during this window. No action is needed on your end, we're monitoring and will update this page if anything requires attention.

  2. investigating Aug 06, 2026, 02:33 PM UTC

    We're currently investigating prolonged 503s on Polygon Amoy Testnet following the conclusion of Polygon's scheduled stress test. You may continue to experience 503 errors and timeouts. We will provide updates as more information becomes available.

  3. investigating Aug 06, 2026, 06:09 PM UTC

    Our team is actively in discussion with the foundation to address the prolonged 503s on Polygon Amoy Testnet. You may continue to experience 503 errors and timeouts. We will provide updates as more information becomes available.

  4. resolved Aug 07, 2026, 03:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 4, 2026

Hyperliquid Testnet Network Stalled

Detected by Pingoru
Aug 04, 2026, 10:19 AM UTC
Resolved
Aug 04, 2026, 11:36 AM UTC
Duration
1h 16m
Affected: HyperEVM - Testnet
Timeline · 2 updates
  1. investigating Aug 04, 2026, 10:19 AM UTC

    We've identified this as an upstream issue with Hyperliquid Testnet and are waiting on a fix from the Hyperliquid team. We'll update this page as soon as we have more information.

  2. resolved Aug 04, 2026, 11:36 AM UTC

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

Read the full incident report →

Notice August 3, 2026

Zora Mainnet Network Stalled at Block 49527702

Detected by Pingoru
Aug 03, 2026, 10:03 AM UTC
Resolved
Aug 03, 2026, 01:28 PM UTC
Duration
3h 25m
Affected: Zora - MainnetMainnet — Websockets APIMainnet — StreamsMainnet — Webhooks
Timeline · 2 updates
  1. investigating Aug 03, 2026, 10:03 AM UTC

    Zora Mainnet is stalled at block 49,527,702. We are currently investigating and will update with more information once it is available.

  2. resolved Aug 03, 2026, 01:28 PM UTC

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

Read the full incident report →

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 - MainnetSui 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: World Chain - MainnetMainnet — 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 - TestnetRobinhood 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: Flare - 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: JOC - MainnetMainnet — 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: Celo - MainnetMainnet — 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: Mantle - MainnetMainnet — 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 →