QuickNode Outage History

QuickNode degraded · 1 active incident View live status →

QuickNode had 250 outages in the last 2 years totaling 212h 20m of downtime — averaging 10 incidents per month.

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

Source: https://status.quicknode.com

Notice June 9, 2026

Injective Mainnet Tendermint JSON-RPC/REST API – 503 Errors

Detected by Pingoru
Jun 09, 2026, 08:58 PM UTC
Resolved
Jun 09, 2026, 10:32 PM UTC
Duration
1h 34m
Affected: Injective - Mainnet
Timeline · 5 updates
  1. investigating Jun 09, 2026, 08:58 PM UTC

    We are investigating an issue with Injective Mainnet Tendermint JSON-RPC/REST API returning 503 errors. Our team is actively working to resolve this and will provide updates as more information becomes available.

  2. investigating Jun 09, 2026, 09:08 PM UTC

    We have temporarily added nearby region to mitigate the 503 issue. Some users may experience elevated latency at this time. Our team is actively working to resolve this and will provide updates as more information becomes available.

  3. investigating Jun 09, 2026, 09:10 PM UTC

    We are continuing to investigate this issue.

  4. monitoring Jun 09, 2026, 09:27 PM UTC

    We have added additional regions to mitigate the 503 errors affecting Injective Mainnet. We are monitoring the service for stability and will provide further updates as needed.

  5. resolved Jun 09, 2026, 10:32 PM UTC

    The 503 errors affecting Injective Mainnet have been resolved. Additional regions were added to mitigate the issue and affected nodes have been brought back online. All systems are operating normally.

Read the full incident report →

Minor June 8, 2026

HyperEVM Testnet — Block Height Stalled

Detected by Pingoru
Jun 08, 2026, 09:56 PM UTC
Resolved
Jun 08, 2026, 10:27 PM UTC
Duration
30m
Affected: HyperEVM - Testnet
Timeline · 3 updates
  1. investigating Jun 08, 2026, 09:56 PM UTC

    We are currently investigating a block height stall affecting HyperEVM Testnet endpoints. We will provide updates as the investigation progresses.

  2. monitoring Jun 08, 2026, 10:03 PM UTC

    The network has recovered and we are monitoring the results.

  3. resolved Jun 08, 2026, 10:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 8, 2026

Polygon Amoy Testnet — Degraded Performance

Detected by Pingoru
Jun 08, 2026, 08:20 PM UTC
Resolved
Jun 09, 2026, 01:08 AM UTC
Duration
4h 48m
Affected: Polygon - Amoy TestnetAmoy — Websockets APIAmoy — WebhooksAmoy — Streams
Timeline · 3 updates
  1. investigating Jun 08, 2026, 08:20 PM UTC

    The QuickNode team is investigating the degraded performance of Polygon Amoy Testnet. Users may experience intermittent 503 errors when making RPC requests. We will update this page as we acquire new information.

  2. monitoring Jun 08, 2026, 10:36 PM UTC

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

  3. resolved Jun 09, 2026, 01:08 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 7, 2026

Polygon zkEVM Mainnet - Block Height Stalled

Detected by Pingoru
Jun 07, 2026, 09:52 AM UTC
Resolved
Jun 07, 2026, 09:56 PM UTC
Duration
12h 4m
Affected: Mainnet — JSON-RPC APIMainnet — Websockets APIMainnet — StreamsMainnet — Webhooks
Timeline · 3 updates
  1. investigating Jun 07, 2026, 09:52 AM UTC

    We are currently investigating a block height stall affecting Polygon zkEVM Mainnet endpoints. We will provide updates as the investigation progresses.

  2. monitoring Jun 07, 2026, 10:50 AM UTC

    Our engineers identified and addressed an issue affecting block height on Polygon zkEVM Mainnet endpoints. All systems are operating normally and we will continue to monitor to ensure stability.

  3. resolved Jun 07, 2026, 09:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 5, 2026

Polygon Amoy — Degraded Performance on Archive Nodes

Detected by Pingoru
Jun 05, 2026, 02:33 PM UTC
Resolved
Jun 06, 2026, 12:41 AM UTC
Duration
10h 7m
Affected: Polygon - Amoy TestnetAmoy — Websockets APIAmoy — WebhooksAmoy — Streams
Timeline · 4 updates
  1. investigating Jun 05, 2026, 02:33 PM UTC

    The Quicknode team is investigating degraded performance on Polygon Amoy archive nodes — we will update this page as we acquire new information.

  2. identified Jun 05, 2026, 08:08 PM UTC

    The issue has been identified and our engineering team is applying a fix.

  3. monitoring Jun 05, 2026, 11:16 PM UTC

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

  4. resolved Jun 06, 2026, 12:41 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 5, 2026

Degraded Performance — Elevated Latency on Trace Methods

Detected by Pingoru
Jun 05, 2026, 02:14 PM UTC
Resolved
Jun 05, 2026, 04:42 PM UTC
Duration
2h 28m
Timeline · 3 updates
  1. investigating Jun 05, 2026, 02:14 PM UTC

    The Quicknode team is investigating degraded performance and elevated latency affecting debug_trace* and tracing requests across multiple networks in the FRA region. We will update this page as we acquire new information.

  2. monitoring Jun 05, 2026, 02:45 PM UTC

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

  3. resolved Jun 05, 2026, 04:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 4, 2026

Plasma Mainnet Degraded Performance - JFK Region

Detected by Pingoru
Jun 04, 2026, 07:33 PM UTC
Resolved
Jun 05, 2026, 02:13 AM UTC
Duration
6h 40m
Affected: Plasma - MainnetMainnet - Websockets APIMainnet — WebhooksMainnet — Streams
Timeline · 4 updates
  1. investigating Jun 04, 2026, 07:33 PM UTC

    The QuickNode team is investigating degraded performance of Plasma Mainnet nodes in the JFK region - we will update this page as we acquire new information.

  2. identified Jun 04, 2026, 09:34 PM UTC

    We have identified the root cause of the degraded performance affecting Plasma Mainnet in the JFK region. Our engineers are actively working to restore the affected nodes.

  3. identified Jun 04, 2026, 11:00 PM UTC

    We have identified the root cause of the degraded performance affecting Plasma Mainnet in the JFK region and node recovery is in progress. As a temporary mitigation, traffic has been rerouted to nearby region while our engineers are working to recover the nodes. Some users may notice elevated latency at this time. We will continue to provide any new updates.

  4. resolved Jun 05, 2026, 02:13 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 4, 2026

Scheduled: Injective Mainnet - Upgrade injectived to v1.20.0

Detected by Pingoru
Jun 04, 2026, 08:54 AM UTC
Resolved
Jun 04, 2026, 06:28 PM UTC
Duration
9h 34m
Affected: Injective - MainnetMainnet Cosmos gRPC & REST APIMainnet — StreamsMainnet — Webhooks
Timeline · 1 update
  1. investigating Jun 04, 2026, 08:54 AM UTC

    We will be upgrading our Injective Mainnet nodes to injectived v1.20.0 starting at 09:00 UTC on June 4, 2025. This is a mandatory mainnet hard fork upgrade. During this maintenance window, you may experience temporary disruptions to Injective Mainnet services, including JSON-RPC, gRPC, Streams, and Webhooks. We expect the process to be completed within 24 hours. We will update this page as the upgrade progresses and mark the maintenance as complete once everything has been confirmed stable. Affected components (:large_yellow_circle: Degraded performance) Mainnet Tendermint JSON-RPC/REST API • Mainnet Cosmos gRPC & REST API • Mainnet — Streams • Mainnet — Webhooks

Read the full incident report →

Minor June 4, 2026

Degraded Performance - Celo Mainnet Archived Nodes

Detected by Pingoru
Jun 04, 2026, 06:20 AM UTC
Resolved
Jun 04, 2026, 08:01 PM UTC
Duration
13h 40m
Affected: Celo - MainnetMainnet — WebSocket API
Timeline · 2 updates
  1. investigating Jun 04, 2026, 06:20 AM UTC

    The Quicknode team is investigating the degraded performance of Celo mainnet archived nodes. Customers may experience increased error rates, including 503 responses, when querying archive data. We will update this page as we acquire new information.

  2. resolved Jun 04, 2026, 08:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 3, 2026

Polygon Amoy — Elevated Errors During Foundation Stress Test

Detected by Pingoru
Jun 03, 2026, 06:12 PM UTC
Resolved
Jun 04, 2026, 06:14 AM UTC
Duration
12h 2m
Affected: Polygon - Amoy TestnetAmoy — Websockets APIAmoy — WebhooksAmoy — Streams
Timeline · 5 updates
  1. investigating Jun 03, 2026, 06:12 PM UTC

    We are aware of elevated API errors and 503 errors on Polygon Amoy. The Polygon Foundation is currently conducting a network stress test which may be contributing to degraded performance. We will provide updates as this progresses.

  2. monitoring Jun 03, 2026, 08:52 PM UTC

    The Polygon Amoy nodes are recovering following the network stress test. We are monitoring for stability.

  3. investigating Jun 03, 2026, 11:57 PM UTC

    We are aware of elevated API errors and 503 errors on Polygon Amoy. The Quicknode team is actively investigating. We will provide updates as this progresses.

  4. monitoring Jun 04, 2026, 04:17 AM UTC

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

  5. resolved Jun 04, 2026, 06:14 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 3, 2026

Starknet Mainnet — Degraded Performance

Detected by Pingoru
Jun 03, 2026, 03:23 PM UTC
Resolved
Jun 03, 2026, 08:22 PM UTC
Duration
4h 59m
Affected: Starknet - MainnetMainnet — Websockets API
Timeline · 4 updates
  1. investigating Jun 03, 2026, 03:23 PM UTC

    The QuickNode team is investigating the degraded performance of Starknet Mainnet - Users may experience elevated 503 errors and increased latency. We will update this page as we acquire new information.

  2. identified Jun 03, 2026, 04:54 PM UTC

    We have identified the issue affecting Starknet Mainnet performance. Our team is working closely with the Starknet Foundation to resolve the issue. We will continue to provide updates as the situation progresses.

  3. monitoring Jun 03, 2026, 06:56 PM UTC

    A fix has been applied and we are monitoring the service for stability.

  4. resolved Jun 03, 2026, 08:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 3, 2026

HyperEVM Testnet - Network Stalled at Block 55,231,856

Detected by Pingoru
Jun 03, 2026, 01:08 PM UTC
Resolved
Jun 04, 2026, 10:36 AM UTC
Duration
21h 28m
Timeline · 2 updates
  1. investigating Jun 03, 2026, 01:08 PM UTC

    The HyperEVM Testnet (archive) appears to have stalled at block 55,231,856 - The QuickNode team is investigating and will update with more information once it is available.

  2. resolved Jun 04, 2026, 10:36 AM UTC

    The issue with the HyperEVM Testnet archive nodes stalling at block 55,231,856 has been resolved. A patch (nb-20260604) has been applied to the affected nodes and block height is advancing normally. We will continue to monitor for stability.

Read the full incident report →

Minor June 3, 2026

Polygon mainnet : Degraded performance on archive calls

Detected by Pingoru
Jun 03, 2026, 07:15 AM UTC
Resolved
Jun 03, 2026, 07:45 PM UTC
Duration
12h 29m
Affected: Polygon - MainnetMainnet — Websockets APIMainnet — WebhooksMainnet — Streams
Timeline · 4 updates
  1. investigating Jun 03, 2026, 07:40 AM UTC

    We are currently investigating this issue.

  2. identified Jun 03, 2026, 12:31 PM UTC

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

  3. monitoring Jun 03, 2026, 12:32 PM UTC

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

  4. resolved Jun 03, 2026, 07:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 2, 2026

Berachain Bepolia Network Stalled at Block 20,782,375

Detected by Pingoru
Jun 02, 2026, 09:55 PM UTC
Resolved
Jun 02, 2026, 11:37 PM UTC
Duration
1h 41m
Affected: Berachain - BepoliaBepolia — WebSocket APIBepolia — StreamsBepolia — Webhooks
Timeline · 3 updates
  1. investigating Jun 02, 2026, 09:55 PM UTC

    The Berachain Bepolia network appears to have stalled at block 20,782,375. The QuickNode team is investigating and will update with more information once it is available.

  2. identified Jun 02, 2026, 10:52 PM UTC

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

  3. resolved Jun 02, 2026, 11:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 2, 2026

Solana Testnet - Degraded Performance

Detected by Pingoru
Jun 02, 2026, 06:13 PM UTC
Resolved
Jun 03, 2026, 12:22 AM UTC
Duration
6h 8m
Affected: Solana - TestnetTestnet — Websockets APITestnet — StreamsTestnet — Webhooks
Timeline · 4 updates
  1. investigating Jun 02, 2026, 06:13 PM UTC

    The QuickNode team is investigating instability on the Solana Testnet. We will update this page as we acquire new information.

  2. identified Jun 02, 2026, 09:19 PM UTC

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

  3. monitoring Jun 02, 2026, 09:59 PM UTC

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

  4. resolved Jun 03, 2026, 12:22 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 2, 2026

Robinhood Testnet Network Stalled at Block 63,024,491

Detected by Pingoru
Jun 02, 2026, 04:15 PM UTC
Resolved
Jun 03, 2026, 08:56 PM UTC
Duration
1d 4h
Affected: Robinhood - TestnetRobinhood Testnet - WebSocket API
Timeline · 4 updates
  1. investigating Jun 02, 2026, 04:15 PM UTC

    The Robinhood Testnet appears to have stalled at block 63,024,491 - The QuickNode team is investigating and will update with more information once it is available.

  2. identified Jun 03, 2026, 06:07 AM UTC

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

  3. identified Jun 03, 2026, 06:09 AM UTC

    Block height is progressing across the node infrastructure. We will notify you once the nodes are in sync with the broader network.

  4. resolved Jun 03, 2026, 08:56 PM UTC

    This incident has been resolved.

Read the full incident report →

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: Hemi - MainnetMainnet - 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 - MainnetSui 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 - MainnetSui 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: Flow - TestnetTestnet — 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 - MainnetSui 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: Plasma - MainnetMainnet - 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: Polygon - MainnetMainnet — 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: Unichain - Sepolia TestnetSepolia – 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 →