QuickNode Outage History

QuickNode is up right now

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

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

Source: https://status.quicknode.com

Notice June 2, 2026

Polygon zkEVM mainnet : Block height stalled

Detected by Pingoru
Jun 02, 2026, 04:20 AM UTC
Resolved
Jun 03, 2026, 06:06 AM UTC
Duration
1d 1h
Affected: Mainnet — JSON-RPC APIMainnet — Websockets APIMainnet — StreamsMainnet — Webhooks
Timeline · 4 updates
  1. investigating Jun 02, 2026, 04:36 AM UTC

    We are currently investigating this issue.

  2. identified Jun 02, 2026, 04:38 AM UTC

    Our engineers are closely listening to updates from the foundation.

  3. monitoring Jun 02, 2026, 04:45 PM UTC

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

  4. resolved Jun 03, 2026, 06:06 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 1, 2026

Hemi Mainnet Network Stalled at Block 4538215

Detected by Pingoru
Jun 01, 2026, 03:14 PM UTC
Resolved
Jun 01, 2026, 06:58 PM UTC
Duration
3h 44m
Affected: Mainnet - JSON RPC APIMainnet - Websockets APIMainnet — StreamsMainnet — Webhooks
Timeline · 3 updates
  1. investigating Jun 01, 2026, 03:14 PM UTC

    The Hemi Mainnet network appears to have stalled at block 4538215. This is a chain-wide issue and is not specific to QuickNode. Our team has raised this with the Hemi Foundation and will provide updates as more information becomes available.

  2. identified Jun 01, 2026, 04:56 PM UTC

    The Hemi Foundation has identified a fix for the network stall at block 4538215. Our team is monitoring the situation as the fix is being applied. We will provide further updates as the network recovers.

  3. resolved Jun 01, 2026, 06:58 PM UTC

    The Hemi Mainnet network stall at block 4538215 has been resolved. The Hemi Foundation identified and deployed a fix, and the network is now advancing normally. All Hemi Mainnet services are fully operational.

Read the full incident report →

Notice May 29, 2026

Sui Mainnet: User Transactions are not being accepted

Detected by Pingoru
May 29, 2026, 09:38 PM UTC
Resolved
May 30, 2026, 07:16 AM UTC
Duration
9h 37m
Affected: SUI Mainnet — JSON-RPC APISui Mainnet - gRPCSui Mainnet - GraphQL
Timeline · 3 updates
  1. investigating May 29, 2026, 09:38 PM UTC

    Sui Mainnet stopped accepting user transactions due to an issue during the epoch change beginning at ~1:30PT. Validators are up and creating system transactions, but user transactions are not currently being accepted. This is a network-wide incident announced by the Sui Core Team. We are monitoring for any changes and our engineering team will promptly act on any updates.

  2. monitoring May 30, 2026, 07:15 AM UTC

    Sui mainnet's network activity has resumed. https://x.com/SuiNetwork/status/2060549945594401126

  3. resolved May 30, 2026, 07:16 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 29, 2026

Sui Mainnet Network Stalled at Block 280,912,461

Detected by Pingoru
May 29, 2026, 12:22 PM UTC
Resolved
May 29, 2026, 06:33 PM UTC
Duration
6h 11m
Affected: SUI Mainnet — JSON-RPC APISui Mainnet - gRPCSui Mainnet - GraphQL
Timeline · 4 updates
  1. investigating May 29, 2026, 12:22 PM UTC

    The Sui Mainnet appears to have stalled at block 280,912,461 - The QuickNode team is investigating and will update with more information once it is available.

  2. investigating May 29, 2026, 04:03 PM UTC

    We are investigating 503 errors on Sui Mainnet following a network stall. The Sui Network team has issued an emergency release (mainnet-v1.72.4) and we are actively monitoring the situation. We will provide updates as more information becomes available.

  3. monitoring May 29, 2026, 04:36 PM UTC

    The network stall has been addressed. We are monitoring Sui Mainnet for stability following the emergency release (mainnet-v1.72.4). We will continue to update this page as we confirm full recovery.

  4. resolved May 29, 2026, 06:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 29, 2026

Flow Testnet: Network-wide stall at block height 112,873,473

Detected by Pingoru
May 29, 2026, 01:18 AM UTC
Resolved
May 29, 2026, 01:47 AM UTC
Duration
29m
Affected: Testnet — REST APITestnet — WebhooksTestnet — Streams
Timeline · 2 updates
  1. investigating May 29, 2026, 01:18 AM UTC

    Flow Testnet is currently experiencing a network-wide stall at block height 112,873,473. We will provide updates as soon as they become available. Explorer: https://evm-testnet.flowscan.io/blocks

  2. resolved May 29, 2026, 01:47 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 28, 2026

Sui Mainnet Network Stalled at Block 280,692,037

Detected by Pingoru
May 28, 2026, 02:15 PM UTC
Resolved
May 28, 2026, 11:07 PM UTC
Duration
8h 51m
Affected: SUI Mainnet — JSON-RPC APISui Mainnet - gRPCSui Mainnet - GraphQL
Timeline · 4 updates
  1. investigating May 28, 2026, 02:15 PM UTC

    The Sui Mainnet network appears to have stalled at block 280,692,037. The QuickNode team is investigating and has raised the issue with the Sui Foundation. We will update this page as more information becomes available.

  2. identified May 28, 2026, 04:01 PM UTC

    The Sui Foundation has acknowledged the issue and is actively working on a fix. We will continue to provide updates as more information becomes available.

  3. identified May 28, 2026, 10:59 PM UTC

    Our engineers are updating nodes to the recent 1.72.3 release. Users may begin to see 503s mitigated and we will mark the incident as resolved once stability at tip has been confirmed.

  4. resolved May 28, 2026, 11:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 28, 2026

Plasma Mainnet : Degraded Performance

Detected by Pingoru
May 28, 2026, 05:23 AM UTC
Resolved
May 28, 2026, 08:30 AM UTC
Duration
3h 6m
Affected: Mainnet - JSON-RPC APIMainnet - Websockets APIMainnet — WebhooksMainnet — Streams
Timeline · 4 updates
  1. investigating May 28, 2026, 05:23 AM UTC

    We are investigating intermittent 503 errors affecting the Plasma Mainnet. Some customers may experience temporary request failures or degraded performance. Our team is actively working to mitigate the issue and restore full service stability. We will provide an update as more information becomes available.

  2. investigating May 28, 2026, 05:47 AM UTC

    We are continuing to investigate this issue.

  3. monitoring May 28, 2026, 06:24 AM UTC

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

  4. resolved May 28, 2026, 08:30 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 27, 2026

Polygon Mainnet – Archive Node Degraded Performance

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

    The QuickNode team is investigating the degraded performance of Polygon Mainnet (Matic) archive nodes - we will update this page as we acquire new information.

  2. monitoring May 27, 2026, 02:54 PM UTC

    We have brought additional nodes online and are monitoring the situation. Performance is improving, though we have not yet reached full capacity. We will continue to provide updates as the situation develops.

  3. resolved May 27, 2026, 06:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 26, 2026

Unichain Sepolia: Degraded Performance

Detected by Pingoru
May 26, 2026, 09:44 PM UTC
Resolved
May 26, 2026, 10:40 PM UTC
Duration
55m
Affected: Sepolia — JSON-RPC APISepolia – Websockets APISepolia — StreamsSepolia — Webhooks
Timeline · 3 updates
  1. investigating May 26, 2026, 09:44 PM UTC

    Unichain Sepolia archive and flashblocks endpoints are currently experiencing degraded performance. Users may experience 503s during this time. We are actively investigating the issue and will provide an update as soon as possible.

  2. monitoring May 26, 2026, 10:15 PM UTC

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

  3. resolved May 26, 2026, 10:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 24, 2026

Degraded Performance - Abstract Testnet

Detected by Pingoru
May 24, 2026, 02:30 AM UTC
Resolved
May 24, 2026, 02:55 AM UTC
Duration
25m
Affected: Testnet — JSON-RPC APITestnet — WebSocket APITestnet — Webhooks
Timeline · 3 updates
  1. investigating May 24, 2026, 02:30 AM UTC

    We are investigating intermittent 503 errors affecting the Abstract Testnet. Some customers may experience temporary request failures or degraded performance. Our team is actively working to mitigate the issue and will provide an update as more information becomes available.

  2. monitoring May 24, 2026, 02:45 AM UTC

    Some nodes have recovered, and 503s have been mitigated. Quicknode teams are continuing to work to recover full capacity and monitor performance to ensure stability.

  3. resolved May 24, 2026, 02:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 23, 2026

Blast Sepolia - Network Stalled

Detected by Pingoru
May 23, 2026, 08:45 PM UTC
Resolved
May 23, 2026, 08:46 PM UTC
Duration
1m
Affected: Sepolia — JSON-RPC APISepolia — WebSocket APISepolia — WebhooksSepolia — Streams
Timeline · 2 updates
  1. investigating May 23, 2026, 08:45 PM UTC

    Blast Sepolia appears to have stalled. The Quicknode team is investigating and will update this page as more information becomes available.

  2. resolved May 23, 2026, 08:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 23, 2026

Billing Dashboard Metrics Delayed

Detected by Pingoru
May 23, 2026, 03:57 PM UTC
Resolved
May 23, 2026, 08:31 PM UTC
Duration
4h 33m
Timeline · 3 updates
  1. investigating May 23, 2026, 03:57 PM UTC

    We are investigating an issue causing billing metrics on the dashboard to appear delayed. We will provide updates as more information becomes available.

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

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

  3. resolved May 23, 2026, 08:31 PM UTC

    The incident has been resolved. The Billing Dashboard Metrics are now operating normally. We will continue to monitor the situation and apologize for any inconvenience caused.

Read the full incident report →

Minor May 22, 2026

Stacks Testnet Network Stalled at Block 3,990,595

Detected by Pingoru
May 22, 2026, 06:21 PM UTC
Resolved
May 22, 2026, 11:07 PM UTC
Duration
4h 45m
Affected: Testnet — REST APITestnet — Websockets API
Timeline · 4 updates
  1. investigating May 22, 2026, 06:21 PM UTC

    The Stacks Testnet appears to have stalled at block 3,990,595 - The QuickNode team is investigating and will update with more information once it is available.

  2. identified May 22, 2026, 06:52 PM UTC

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

  3. monitoring May 22, 2026, 10:26 PM UTC

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

  4. resolved May 22, 2026, 11:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 21, 2026

Injective Testnet Network Stalled at Block 126627399

Detected by Pingoru
May 21, 2026, 02:59 PM UTC
Resolved
May 21, 2026, 03:48 PM UTC
Duration
49m
Affected: Testnet Tendermint JSON-RPC/REST APITestnet Cosmos gRPC & REST APITestnet — StreamsTestnet — Webhooks
Timeline · 2 updates
  1. investigating May 21, 2026, 02:59 PM UTC

    The Injective Testnet network appears to have stalled at block 126627399 following a network upgrade — The Quicknode team is investigating and will update with more information once it is available.

  2. resolved May 21, 2026, 03:48 PM UTC

    The Injective Testnet network has resumed producing blocks. Our nodes have reconnected to peers and are advancing normally. This incident has been resolved.

Read the full incident report →

Minor May 20, 2026

Arbitrum Mainnet - Elevated 503 and API Errors

Detected by Pingoru
May 20, 2026, 07:43 PM UTC
Resolved
May 20, 2026, 10:58 PM UTC
Duration
3h 15m
Affected: Mainnet Nitro — JSON-RPC APIMainnet Nitro — WebSocket APIMainnet Classic — JSON-RPC APIMainnet Classic — WebSocket APIMainnet — WebhooksMainnet — Streams
Timeline · 3 updates
  1. investigating May 20, 2026, 07:43 PM UTC

    We are investigating an elevated rate of 503 errors affecting Arbitrum Mainnet. Our team has identified an issue with backend connectivity and is actively working to restore full service. We will provide updates as more information becomes available.

  2. monitoring May 20, 2026, 08:34 PM UTC

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

  3. resolved May 20, 2026, 10:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 20, 2026

Polygon Amoy Testnet - Elevated 503 Errors During Load Testing

Detected by Pingoru
May 20, 2026, 07:34 PM UTC
Resolved
May 20, 2026, 08:29 PM UTC
Duration
54m
Affected: Amoy — JSON-RPC APIAmoy — Websockets APIAmoy — WebhooksAmoy — Streams
Timeline · 2 updates
  1. investigating May 20, 2026, 07:34 PM UTC

    We are aware of elevated 503 errors on the Polygon Amoy Testnet. This is related to scheduled load and stress testing being conducted by the Polygon team between 19:00 – 20:00 UTC. We will update this page as more information becomes available.

  2. resolved May 20, 2026, 08:29 PM UTC

    The elevated 503 errors on Polygon Amoy Testnet observed during the scheduled load testing window (19:00–20:00 UTC) have subsided. The incident has been resolved and all systems are operating normally.

Read the full incident report →

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 →