QuickNode Outage History

QuickNode is up right now

QuickNode had 195 outages in the last 2 years totaling 382h 27m of downtime — averaging 8 incidents per month.

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

Source: https://status.quicknode.com

Minor May 20, 2026

Hedera Mainnet Network Stalled

Detected by Pingoru
May 20, 2026, 05:24 PM UTC
Resolved
May 20, 2026, 07:07 PM UTC
Duration
1h 42m
Affected: Mainnet - JSON-RPC APIMainnet - REST APIMainnet — StreamsMainnet — Webhooks
Timeline · 3 updates
  1. investigating May 20, 2026, 05:24 PM UTC

    The Hedera Mainnet appears to have stalled at block 95,291,380 - The QuickNode team is investigating and will update with more information once it is available.

  2. identified May 20, 2026, 06:02 PM UTC

    Hedera Mainnet appears to have stalled at block 95,291,380. This is due to on-going maintenance by the foundation. You can find more details from the Foundation's Status Page here: https://status.hedera.com/incidents/6558j95l840y

  3. resolved May 20, 2026, 07:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 20, 2026

Quicknode Dashboard - Degraded Performance

Detected by Pingoru
May 20, 2026, 01:27 PM UTC
Resolved
May 20, 2026, 02:04 PM UTC
Duration
36m
Affected: QuickNode Dashboard
Timeline · 3 updates
  1. investigating May 20, 2026, 01:27 PM UTC

    We are investigating the degraded performance of the Quicknode dashboard. Users may have issues accessing the Dashboard page at this time. We will update this page as we acquire more information.

  2. monitoring May 20, 2026, 02:02 PM UTC

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

  3. resolved May 20, 2026, 02:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 19, 2026

HyperLiquid HyperEVM Testnet — 503 Errors

Detected by Pingoru
May 19, 2026, 03:05 PM UTC
Resolved
May 19, 2026, 06:14 PM UTC
Duration
3h 9m
Affected: HyperEVM-Testnet - JSON-RPC API
Timeline · 6 updates
  1. investigating May 19, 2026, 03:05 PM UTC

    We are investigating an issue with HyperLiquid HyperEVM Testnet where users may be experiencing 503 errors. Our team is actively working to resolve the issue and will provide updates as more information becomes available.

  2. monitoring May 19, 2026, 03:21 PM UTC

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

  3. investigating May 19, 2026, 03:51 PM UTC

    We are continuing to investigate 503 errors affecting HyperLiquid HyperEVM Testnet. Nodes appeared to recover briefly but the issue has resumed. Our team is actively investigating.

  4. identified May 19, 2026, 03:54 PM UTC

    We are continuing to work on addressing the 503 errors affecting HyperLiquid HyperEVM Testnet. Nodes appeared to recover briefly but the issue had resumed. This issue originally began following a Hyperliquid Testnet hardfork at height 570610500. We will update this page as we acquire new information.

  5. monitoring May 19, 2026, 05:46 PM UTC

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

  6. resolved May 19, 2026, 06:14 PM UTC

    The issue causing 503 errors on HyperLiquid HyperEVM Testnet has been resolved. All systems are operating normally.

Read the full incident report →

Minor May 19, 2026

Polygon Amoy — Archive Requests Returning 503 Errors

Detected by Pingoru
May 19, 2026, 02:13 PM UTC
Resolved
May 19, 2026, 04:06 PM UTC
Duration
1h 53m
Affected: Amoy — JSON-RPC APIAmoy — Websockets APIAmoy — WebhooksAmoy — Streams
Timeline · 3 updates
  1. investigating May 19, 2026, 02:13 PM UTC

    We are investigating an issue affecting Polygon Amoy archive nodes. Users may experience 503 errors when making archive requests. Our team is actively working to restore full service and will provide updates as more information becomes available.

  2. monitoring May 19, 2026, 03:14 PM UTC

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

  3. resolved May 19, 2026, 04:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 18, 2026

Elevated API Errors - 429 Rate Limit Responses

Detected by Pingoru
May 18, 2026, 05:01 PM UTC
Resolved
May 18, 2026, 07:12 PM UTC
Duration
2h 11m
Timeline · 3 updates
  1. investigating May 18, 2026, 05:01 PM UTC

    We're experiencing an elevated level of API errors and are currently looking into the issue.

  2. monitoring May 18, 2026, 05:33 PM UTC

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

  3. resolved May 18, 2026, 07:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 16, 2026

Blast Mainnet Degraded Performance - SIN Region

Detected by Pingoru
May 16, 2026, 04:53 PM UTC
Resolved
May 17, 2026, 03:58 AM UTC
Duration
11h 4m
Affected: Mainnet — JSON-RPC APIMainnet — WebSocket APIMainnet — WebhooksMainnet — Streams
Timeline · 2 updates
  1. investigating May 16, 2026, 04:53 PM UTC

    The QuickNode team is investigating degraded performance of Blast Mainnet in the SIN (Singapore) region - we will update this page as we acquire new information.

  2. resolved May 17, 2026, 03:58 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 16, 2026

Hyperliquid Mainnet: Hypercore Block Height stalled at 998,059,177

Detected by Pingoru
May 16, 2026, 12:27 AM UTC
Resolved
May 16, 2026, 01:25 AM UTC
Duration
57m
Affected: Hypercore - JSON-RPC APIHypercore - Websockets APIHypercore - StreamsHypercore - Webhooks
Timeline · 3 updates
  1. investigating May 16, 2026, 12:27 AM UTC

    Hyperliquid Mainnet is experiencing a stall at block height 998,059,177. This incident only affects Hypercore JSON-RPC queries. We will provide updates as soon as they become available.

  2. monitoring May 16, 2026, 12:44 AM UTC

    A fix has been implemented and block height is progressing at this time. Our engineers are working to backfill the gaps experienced throughout this incident. This issue will be marked as resolved following confirmation of the backfill.

  3. resolved May 16, 2026, 01:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 15, 2026

Base Mainnet Degraded Performance

Detected by Pingoru
May 15, 2026, 03:17 PM UTC
Resolved
May 15, 2026, 05:21 PM UTC
Duration
2h 3m
Affected: Mainnet — JSON-RPC APIMainnet — WebSocket APIMainnet —WebhooksMainnet — Streams
Timeline · 3 updates
  1. investigating May 15, 2026, 03:17 PM UTC

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

  2. monitoring May 15, 2026, 03:50 PM UTC

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

  3. resolved May 15, 2026, 05:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 15, 2026

Lisk Mainnet Degraded Performance - Stale Data

Detected by Pingoru
May 15, 2026, 03:03 PM UTC
Resolved
May 20, 2026, 01:32 PM UTC
Duration
4d 22h
Affected: Mainnet — JSON-RPC APIMainnet — Websockets APIMainnet — StreamsMainnet — Webhooks
Timeline · 3 updates
  1. investigating May 15, 2026, 03:03 PM UTC

    The QuickNode team is investigating degraded performance of Lisk Mainnet - customers may experience stale data on block-dependent calls (e.g. eth_blockNumber) while archive nodes catch up to chain head. We will update this page as we acquire new information.

  2. identified May 19, 2026, 03:28 PM UTC

    The Quicknode team is continuing to address the degraded performance of Lisk Mainnet and we are working with the foundation to resolve the issue. Customers may continue to experience stale data on block-dependent calls (e.g. eth_blockNumber) while archive nodes catch up to chain head. We will update this page as we acquire new information.

  3. resolved May 20, 2026, 01:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 14, 2026

Blast Sepolia Network Stalled

Detected by Pingoru
May 14, 2026, 04:30 PM UTC
Resolved
May 14, 2026, 04:35 PM UTC
Duration
4m
Affected: Sepolia — JSON-RPC APISepolia — WebSocket APISepolia — WebhooksSepolia — Streams
Timeline · 4 updates
  1. investigating May 14, 2026, 04:30 PM UTC

    The Blast Sepolia network appears to have stalled — The QuickNode team is investigating and will update with more information once it is available.

  2. monitoring May 14, 2026, 04:31 PM UTC

    A fix has been applied to the Blast Sepolia network. We are monitoring the network for continued stability.

  3. monitoring May 14, 2026, 04:33 PM UTC

    A fix has been applied to the Blast Sepolia network. We are monitoring for continued stability and will provide further updates as needed.

  4. resolved May 14, 2026, 04:35 PM UTC

    The incident has been resolved.

Read the full incident report →

Minor May 14, 2026

Stellar Mainnet Degraded Performance

Detected by Pingoru
May 14, 2026, 03:33 PM UTC
Resolved
May 14, 2026, 06:38 PM UTC
Duration
3h 5m
Affected: Mainnet - REST APIMainnet — JSON-RPC API
Timeline · 4 updates
  1. investigating May 14, 2026, 03:33 PM UTC

    The QuickNode team is investigating the degraded performance of Stellar Mainnet - Users may experience 503 errors during this time. We will update this page as we acquire new information.

  2. monitoring May 14, 2026, 04:09 PM UTC

    A fix has been applied and we are monitoring for stability. We will continue to update this page as needed.

  3. monitoring May 14, 2026, 04:42 PM UTC

    A fix has been applied and we are monitoring for stability. We will continue to update this page as needed.

  4. resolved May 14, 2026, 06:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 14, 2026

Base Mainnet - TLS Errors

Detected by Pingoru
May 14, 2026, 03:24 PM UTC
Resolved
May 14, 2026, 06:38 PM UTC
Duration
3h 14m
Affected: Mainnet — JSON-RPC APIMainnet — WebSocket APIMainnet —WebhooksMainnet — Streams
Timeline · 4 updates
  1. investigating May 14, 2026, 03:24 PM UTC

    We are investigating reports of TLS errors affecting Base Mainnet endpoints. Users may experience issues with WebSocket and JSON-RPC connections. We will provide updates as we gather more information.

  2. monitoring May 14, 2026, 03:51 PM UTC

    The TLS errors affecting Base Mainnet endpoints have been resolved. WebSocket and JSON-RPC connectivity has returned to normal operation. We are continuing to monitor the services to ensure stability.

  3. monitoring May 14, 2026, 04:41 PM UTC

    The TLS errors affecting Base Mainnet endpoints have been resolved. WebSocket and JSON-RPC connectivity has returned to normal operation. We are continuing to monitor the services to ensure stability.

  4. resolved May 14, 2026, 06:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 14, 2026

Hemi Testnet: Stalled at block height 5,883,797

Detected by Pingoru
May 14, 2026, 12:21 AM UTC
Resolved
May 14, 2026, 07:23 AM UTC
Duration
7h 2m
Affected: Testnet - JSON-RPC APITestnet — Websockets APITestnet — StreamsTestnet — Webhooks
Timeline · 2 updates
  1. investigating May 14, 2026, 12:21 AM UTC

    Hemi Testnet has stalled at block height 5,883,797. This is a network-wide stall and not isolated to Quicknode. We will provide updates as soon as they become available.

  2. resolved May 14, 2026, 07:23 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 12, 2026

Fluent Testnet - Stuck Network

Detected by Pingoru
May 12, 2026, 08:38 AM UTC
Resolved
May 13, 2026, 02:57 AM UTC
Duration
18h 18m
Affected: Fluent Testnet - JSON RPC API
Timeline · 2 updates
  1. investigating May 12, 2026, 08:38 AM UTC

    Fluent Mainnet appears to have stalled at block 26,579,757 - The Quicknode team is investigating and will update with more information once it is available.

  2. resolved May 13, 2026, 02:57 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 11, 2026

Degraded Performance - TON Mainnet

Detected by Pingoru
May 11, 2026, 08:19 PM UTC
Resolved
May 19, 2026, 03:21 PM UTC
Duration
7d 19h
Affected: Mainnet — REST API
Timeline · 3 updates
  1. investigating May 11, 2026, 08:19 PM UTC

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

  2. monitoring May 11, 2026, 10:16 PM UTC

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

  3. resolved May 19, 2026, 03:21 PM UTC

    Service has stabilized, and 503s are back down significantly. We are still coordinating with the TON Foundation on an upstream release that provides a permanent fix, and we will roll it out once available. We will continue to monitor closely and will post a new update if impact returns or when the Foundation release is deployed.

Read the full incident report →

Minor May 11, 2026

Billing Dashboard Data Delay

Detected by Pingoru
May 11, 2026, 04:51 PM UTC
Resolved
May 11, 2026, 07:38 PM UTC
Duration
2h 47m
Affected: QuickNode Dashboard
Timeline · 2 updates
  1. identified May 11, 2026, 04:51 PM UTC

    We’re currently experiencing a delay in billing-related data appearing in the dashboard. Charges and usage may take longer than usual to reflect, but billing is still processing normally in the background. We’re working to restore normal update times and will post an update once data is fully caught up.

  2. resolved May 11, 2026, 07:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 10, 2026

Quicknode dashboard : Investigating Dashboard Loading Issues

Detected by Pingoru
May 10, 2026, 04:17 PM UTC
Resolved
May 11, 2026, 12:52 AM UTC
Duration
8h 35m
Affected: QuickNode Dashboard
Timeline · 3 updates
  1. investigating May 10, 2026, 04:17 PM UTC

    We are currently investigating this issue.

  2. monitoring May 10, 2026, 11:17 PM UTC

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

  3. resolved May 11, 2026, 12:52 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 10, 2026

Base Mainnet & Base Sepolia - Degrade Performance

Detected by Pingoru
May 10, 2026, 01:01 PM UTC
Resolved
May 10, 2026, 02:37 PM UTC
Duration
1h 35m
Affected: Mainnet — JSON-RPC APIMainnet — WebSocket APIMainnet —WebhooksSepolia - JSON-RPC APISepolia - WebSocket APISepolia — WebSocket APISepolia —Webhooks
Timeline · 2 updates
  1. investigating May 10, 2026, 01:01 PM UTC

    We are aware of a node peering stability issue affecting Base Mainnet and Testnet. The Base Foundation has published an incident report attributing this to upcoming changes to p2p peer discovery. Quicknode Base Infrastructure may be impacted and users could see intermittent 503 errors or request timeouts during this period. There is no action required on your end. Our team is monitoring the situation closely and will provide updates here as more information becomes available.

  2. resolved May 10, 2026, 02:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 10, 2026

Base Sepolia: Degraded Performance

Detected by Pingoru
May 10, 2026, 12:09 AM UTC
Resolved
May 10, 2026, 12:36 AM UTC
Duration
26m
Affected: Sepolia - JSON-RPC APISepolia - WebSocket APISepolia —WebhooksSepolia — Streams
Timeline · 3 updates
  1. investigating May 10, 2026, 12:09 AM UTC

    We are currently investigating an issue affecting archive calls on Base Sepolia. We will provide updates as they become available.

  2. monitoring May 10, 2026, 12:35 AM UTC

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

  3. resolved May 10, 2026, 12:36 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 9, 2026

Worldchain Mainnet: Degraded Performance

Detected by Pingoru
May 09, 2026, 08:51 PM UTC
Resolved
May 09, 2026, 10:11 PM UTC
Duration
1h 20m
Affected: Mainnet — JSON-RPC APIMainnet — Websockets APIMainnet — StreamsMainnet — Webhooks
Timeline · 3 updates
  1. investigating May 09, 2026, 08:51 PM UTC

    We are currently investigating degraded performance on our Worldchain Mainnet nodes. Users may experience 503s and null responses. We will provide updates as they become available.

  2. monitoring May 09, 2026, 09:06 PM UTC

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

  3. resolved May 09, 2026, 10:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 8, 2026

Quicknode Key-Value Store: Degraded Performance

Detected by Pingoru
May 08, 2026, 11:15 PM UTC
Resolved
May 09, 2026, 12:58 AM UTC
Duration
1h 43m
Affected: Quicknode StreamsQuicknode Webhooks
Timeline · 3 updates
  1. investigating May 08, 2026, 11:32 PM UTC

    We are currently investigating this issue.

  2. monitoring May 09, 2026, 12:04 AM UTC

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

  3. resolved May 09, 2026, 12:58 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 8, 2026

Quicknode Streams: Degraded Performance

Detected by Pingoru
May 08, 2026, 09:54 PM UTC
Resolved
May 08, 2026, 10:03 PM UTC
Duration
9m
Affected: Quicknode Streams
Timeline · 3 updates
  1. investigating May 08, 2026, 09:54 PM UTC

    We are currently investigating this issue.

  2. monitoring May 08, 2026, 09:59 PM UTC

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

  3. resolved May 08, 2026, 10:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 8, 2026

Quicknode streams API, Key Value storage API : Degraded performance

Detected by Pingoru
May 08, 2026, 07:45 AM UTC
Resolved
May 08, 2026, 09:46 AM UTC
Duration
2h 1m
Affected: Quicknode Streams
Timeline · 4 updates
  1. investigating May 08, 2026, 08:16 AM UTC

    We are currently investigating this issue.

  2. identified May 08, 2026, 08:39 AM UTC

    The issue has been identified, and our engineers are actively working on a resolution. Please expect the next update by 11:00 AM UTC.

  3. monitoring May 08, 2026, 09:04 AM UTC

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

  4. resolved May 08, 2026, 09:46 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 8, 2026

XRP testnet : Nodes are stalled at 17186304

Detected by Pingoru
May 08, 2026, 03:30 AM UTC
Resolved
May 08, 2026, 04:01 AM UTC
Duration
31m
Affected: Testnet — JSON-RPC APITestnet — Websockets APITestnet — StreamsTestnet — Webhooks
Timeline · 4 updates
  1. investigating May 08, 2026, 03:16 AM UTC

    We are currently investigating this issue.

  2. identified May 08, 2026, 04:01 AM UTC

    Our engineers are closely listening to updates from the foundation.

  3. monitoring May 08, 2026, 04:01 AM UTC

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

  4. resolved May 08, 2026, 04:01 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 7, 2026

Degraded Performance - Polygon Amoy

Detected by Pingoru
May 07, 2026, 08:47 PM UTC
Resolved
May 07, 2026, 11:08 PM UTC
Duration
2h 21m
Affected: Amoy — JSON-RPC APIAmoy — Websockets APIAmoy — WebhooksAmoy — Streams
Timeline · 2 updates
  1. identified May 07, 2026, 08:47 PM UTC

    The Quicknode team is aware of the degraded performance of the Polygon Amoy Network. The foundation has notified us they are performing stress tests on the network. Users may experience elevated latencies, timeouts, and 503 errors at this time.

  2. resolved May 07, 2026, 11:08 PM UTC

    This incident has been resolved.

Read the full incident report →