QuickNode Outage History

QuickNode is up right now

QuickNode had 136 outages in the last 2 years totaling 444h 10m of downtime — averaging 5.6 incidents per month.

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

Source: https://status.quicknode.com

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 →

Minor May 7, 2026

Degraded Performance - Ethereum Mainnet

Detected by Pingoru
May 07, 2026, 04:05 PM UTC
Resolved
May 07, 2026, 09:04 PM UTC
Duration
4h 59m
Affected: Mainnet — JSON-RPC APIMainnet — Websockets APIMainnet Beacon — REST APIMainnet — WebhooksMainnet — Streams
Timeline · 3 updates
  1. investigating May 07, 2026, 04:05 PM UTC

    The Quicknode team is investigating the degraded performance of specific methods such as eth_getLogs on Ethereum Mainnet - we will update this page as we acquire new information. Users may experience elevated latency and timeouts at this time.

  2. monitoring May 07, 2026, 05:02 PM UTC

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

  3. resolved May 07, 2026, 09:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 7, 2026

Arbitrum Mainnet - Sporadic API Errors

Detected by Pingoru
May 07, 2026, 02:37 PM UTC
Resolved
May 07, 2026, 09:22 PM UTC
Duration
6h 44m
Affected: Mainnet Nitro — JSON-RPC APIMainnet Nitro — WebSocket APIMainnet Classic — JSON-RPC APIMainnet Classic — WebSocket API
Timeline · 3 updates
  1. investigating May 07, 2026, 02:37 PM UTC

    The Quicknode team is investigating sporadic API errors being served on Arbitrum Mainnet - we will update this page as we acquire new information. Users may experience sporadic 503 errors at this time.

  2. monitoring May 07, 2026, 05:23 PM UTC

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

  3. resolved May 07, 2026, 09:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 4, 2026

Degraded Performance - HyperEVM Testnet

Detected by Pingoru
May 04, 2026, 09:17 PM UTC
Resolved
May 05, 2026, 12:33 AM UTC
Duration
3h 15m
Affected: HyperEVM-Testnet - JSON-RPC API
Timeline · 3 updates
  1. investigating May 04, 2026, 09:17 PM UTC

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

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

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

  3. resolved May 05, 2026, 12:33 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 3, 2026

Degraded Performance - Tron Mainnet FRA Region

Detected by Pingoru
May 03, 2026, 09:09 PM UTC
Resolved
May 04, 2026, 03:54 AM UTC
Duration
6h 45m
Affected: Mainnet — JSON-RPC APIMainnet — REST APIMainnet — StreamsMainnet — Webhooks
Timeline · 2 updates
  1. investigating May 03, 2026, 09:09 PM UTC

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

  2. resolved May 04, 2026, 03:54 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 2, 2026

Sei Pacific : Degraded Performance

Detected by Pingoru
May 02, 2026, 05:08 PM UTC
Resolved
May 09, 2026, 08:29 AM UTC
Duration
6d 15h
Affected: Pacific-1 Mainnet — EVM JSON-RPC APIPacific-1 Mainnet — Tendermint JSON-RPC/REST APIPacific-1 Mainnet — Cosmos REST APIPacific-1 Mainnet — Websockets APIPacific-1 Mainnet — StreamsPacific-1 Mainnet — Webhooks
Timeline · 6 updates
  1. investigating May 02, 2026, 05:08 PM UTC

    The Quicknode team is investigating the degraded performance of Sei Pacific - we will update this page as we acquire new information. Users may experience heightened latency and timeouts at this time.

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

    The Quicknode team is continuing to mitigate the degraded performance of Sei Pacific. We will update this page as we acquire new information. Users may continue to experience heightened latency and timeouts at this time.

  3. identified May 02, 2026, 07:22 PM UTC

    The Quicknode team is actively working to resolve the degraded performance affecting Sei Pacific. We are coordinating closely with the Sei team to address the issue. This page will be updated as new information becomes available. Users may continue to experience elevated latency and intermittent timeouts at this time.

  4. identified May 06, 2026, 05:58 AM UTC

    Our engineers are closely listening to updates from the foundation. We will provide another update on or before 7th May, 17:00 UTC

  5. monitoring May 09, 2026, 08:29 AM UTC

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

  6. resolved May 09, 2026, 08:29 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 1, 2026

Stuck Network - Polygon zkEVM

Detected by Pingoru
May 01, 2026, 02:24 PM UTC
Resolved
May 02, 2026, 01:54 AM UTC
Duration
11h 30m
Affected: Mainnet — JSON-RPC APIMainnet — Websockets APIMainnet — StreamsMainnet — Webhooks
Timeline · 3 updates
  1. investigating May 01, 2026, 02:24 PM UTC

    The Polygon zkEVM network appears to have stalled. The Quicknode team is investigating and will update with more information once it is available.

  2. monitoring May 01, 2026, 04:37 PM UTC

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

  3. resolved May 02, 2026, 01:54 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 1, 2026

Worldchain Mainnet: Block Height Stalled at 29,128,981

Detected by Pingoru
May 01, 2026, 01:30 AM UTC
Resolved
May 01, 2026, 09:01 AM UTC
Duration
7h 30m
Affected: Mainnet — JSON-RPC APIMainnet — Websockets APIMainnet — StreamsMainnet — Webhooks
Timeline · 4 updates
  1. investigating May 01, 2026, 12:56 AM UTC

    We are currently investigating this issue.

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

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

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

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

  4. resolved May 01, 2026, 09:01 AM UTC

    The issue affecting Worldchain Mainnet has been resolved. The block stall was caused by nodes requiring updates for the Jovian Hardfork that activated on May 1, 2026 at 00:00 UTC. All nodes have been updated and have caught up to the current block height. All Worldchain Mainnet RPC endpoints, WebSockets, Streams, and Webhooks are now fully operational. If you continue to experience any issues, please contact our support team.

Read the full incident report →

Minor April 29, 2026

Stuck Network - Blast Sepolia

Detected by Pingoru
Apr 29, 2026, 04:52 PM UTC
Resolved
Apr 29, 2026, 05:16 PM UTC
Duration
23m
Affected: Sepolia — JSON-RPC APISepolia — WebSocket APISepolia — WebhooksSepolia — Streams
Timeline · 2 updates
  1. investigating Apr 29, 2026, 04:52 PM UTC

    The Blast Sepolia network appears to have stalled at block 36373475 - The Quicknode team is investigating and will update with more information once it is available.

  2. resolved Apr 29, 2026, 05:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 29, 2026

Degraded Performance - Polygon Mainnet

Detected by Pingoru
Apr 29, 2026, 03:45 PM UTC
Resolved
Apr 29, 2026, 07:05 PM UTC
Duration
3h 20m
Affected: Mainnet — JSON-RPC APIMainnet — Websockets APIMainnet — WebhooksMainnet — Streams
Timeline · 5 updates
  1. investigating Apr 29, 2026, 03:45 PM UTC

    The Quicknode team is investigating the degraded performance of Polygon Mainnet - we will update this page as we acquire new information. Users may be served 503s at this time.

  2. investigating Apr 29, 2026, 04:31 PM UTC

    The Quicknode team is continuing to investigate the degraded performance of Polygon Mainnet and we are working closely with the foundation to resolve the issue. We will update this page as we acquire new information. Users may be served 503s at this time.

  3. identified Apr 29, 2026, 06:32 PM UTC

    Quicknode Polygon Mainnet endpoints may experience degraded performance, including intermittent 503 responses, increased latency, and nodes lagging behind tip while checkpoint/milestone processing is disrupted. Our team is actively applying mitigations and working with upstream guidance to restore normal service, and we will post further updates to this incident as more information becomes available.

  4. monitoring Apr 29, 2026, 06:55 PM UTC

    A fix is in place, and we are monitoring performance to ensure stability and will provide an update upon confirmation or if further action is required within 10 minutes.

  5. resolved Apr 29, 2026, 07:05 PM UTC

    This incident has been resolved.

Read the full incident report →