QuickNode Outage History

QuickNode is up right now

Pingoru has recorded 277 incidents for QuickNode: 277 in the last 12 months and 83 in the last 90 days.

Source: status.quicknode.com

277incidents recorded
277last 12 months
83last 90 days
18 hourstypical duration
Incidents per month
02550AprMayJunJulAugSepOctNov2
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov15%
Pingoru began tracking QuickNode in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202634159 of 720 (22%)
May 202648429 of 744 (58%)
June 202644268 of 720 (37%)
July 202634411 of 744 (55%)
August 202634130 of 744 (17%)
September 202628307 of 720 (43%)
October 202623201 of 744 (27%)
November 202627 of 49 (15%)

Incidents, newest first

Notice September 7, 2026 Gravity Mainnet Stalled at Block 41,384,106 12h 47m Gravity - Mainnet, Mainnet — Websockets API, Mainnet — Streams, Mainnet — Webhooks

Started Sep 07, 2026, 01:13 AM UTC· resolved Sep 07, 2026, 02:00 PM UTC

  1. investigating Sep 07, 2026, 01:13 AM UTC

    Gravity Mainnet appears to have stalled at block 41,384,106. The Quicknode team is investigating and will update with more information once it is available.

  2. identified Sep 07, 2026, 07:51 AM UTC

    The underlying issue has been identified. We are working with the Foundation to restore normal block progression. Further updates will be provided as the situation develops.

  3. resolved Sep 07, 2026, 02:00 PM UTC

    This incident has been resolved. Gravity Mainnet has resumed normal block progression past block 41,384,106.

Read the full incident report →

Minor September 4, 2026 RobinHood Mainnet - Increased Latency 12h 1m Robinhood - Mainnet, RobinHood - Mainnet - Websocket

Started Sep 04, 2026, 01:10 PM UTC· resolved Sep 05, 2026, 01:12 AM UTC

  1. investigating Sep 04, 2026, 01:10 PM UTC

    We are investigating increased latency on RobinHood Mainnet. The Quicknode team has notified the foundation and will update this page as we acquire new information.

  2. investigating Sep 04, 2026, 01:23 PM UTC

    The RobinHood foundation team has been notified and is actively investigating, this appears to be unrelated to Quicknode. We will provide further updates as more information becomes available.

  3. investigating Sep 04, 2026, 01:53 PM UTC

    The RobinHood foundation team has confirmed everything has returned back to normality. Our engineering team is actively monitoring performance.

  4. identified Sep 04, 2026, 04:20 PM UTC

    Users may continue to experience degraded performance and issues with transaction landing on Robinhood Mainnet. We are currently investigating connection issues regarding the sequencer feed and are closely listening to updates from the foundation.

  5. monitoring Sep 04, 2026, 05:15 PM UTC

    The upstream feed connection issues have stabilized and we are monitoring for stability.

  6. resolved Sep 05, 2026, 01:12 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 2, 2026 Injective Mainnet - Elevated Errors and Degraded Performance 23m Injective - Mainnet, Mainnet Cosmos gRPC & REST API, Mainnet — Streams, Mainnet — Webhooks

Started Sep 02, 2026, 06:03 PM UTC· resolved Sep 02, 2026, 06:26 PM UTC

  1. investigating Sep 02, 2026, 06:03 PM UTC

    The Quicknode team is investigating degraded performance of Injective Mainnet — we will update this page as we acquire new information.

  2. investigating Sep 02, 2026, 06:06 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Sep 02, 2026, 06:12 PM UTC

    The issue causing elevated errors and 503 responses on Injective Mainnet has been resolved. All systems are operating normally. We are monitoring for stability

  4. resolved Sep 02, 2026, 06:26 PM UTC

    The elevated errors and degraded performance affecting Injective Mainnet have been resolved. All systems are operating normally.

Read the full incident report →

Minor August 31, 2026 Injective Mainnet — Block Height Stalled 8h 8m

Started Aug 31, 2026, 03:57 PM UTC· resolved Sep 01, 2026, 12:05 AM UTC

  1. investigating Aug 31, 2026, 03:57 PM UTC

    Injective Mainnet appears to have stalled chain wide at block 181,027,000. The team is investigating and will update with more information once it is available.

  2. identified Aug 31, 2026, 06:40 PM UTC

    We have identified a possible root cause for the Injective Mainnet block height stall. A high priority patch is being deployed, and a network-wide upgrade may be in progress. We will continue to monitor and provide updates as more information becomes available.

  3. identified Aug 31, 2026, 11:03 PM UTC

    Our nodes are starting to recover following the patch deployment. We'll post another update once the system is fully operational.

  4. resolved Sep 01, 2026, 12:05 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 31, 2026 Gravity Mainnet — Block Height Stalled 6h 52m Gravity - Mainnet, Mainnet — Websockets API, Mainnet — Streams, Mainnet — Webhooks

Started Aug 31, 2026, 07:08 AM UTC· resolved Aug 31, 2026, 02:00 PM UTC

  1. investigating Aug 31, 2026, 07:08 AM UTC

    Gravity Mainnet appears to have stalled at block 39,007,386 - The Quicknode team is investigating and will update with more information once it is available.

  2. identified Aug 31, 2026, 07:26 AM UTC

    The underlying issue has been identified. We are working with the Foundation to restore normal block progression. Further updates will be provided as the situation develops.

  3. monitoring Aug 31, 2026, 01:41 PM UTC

    This continues to be an upstream issue on the Gravity network, not related to our infrastructure. Block production has partially resumed, with some nodes still catching up. We'll keep watching closely and update as the situation develops.

  4. resolved Aug 31, 2026, 06:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 29, 2026 ZkSync Sepolia Network Stall at 8,335,793 23h 15m ZKsync - Testnet, Testnet — Websockets API, Testnet — Streams, Testnet — Webhooks

Started Aug 29, 2026, 09:59 PM UTC· resolved Aug 30, 2026, 09:14 PM UTC

  1. investigating Aug 29, 2026, 09:59 PM UTC

    We are currently investigating a network wide stall at block height 8,335,793.

  2. investigating Aug 30, 2026, 01:57 PM UTC

    We are continuing to investigate a network-wide stall at block height 8,335,793. As this is affecting the entire network, we're currently waiting on guidance from the foundation before proceeding. We'll provide updates as soon as more information becomes available.

  3. resolved Aug 30, 2026, 09:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 27, 2026 ZkSync Era Testnet Degraded Performance 1h 33m ZKsync - Testnet, Testnet — Websockets API, Testnet — Streams, Testnet — Webhooks

Started Aug 27, 2026, 01:24 PM UTC· resolved Aug 27, 2026, 02:58 PM UTC

  1. investigating Aug 27, 2026, 01:24 PM UTC

    We are currently investigating degraded performance on zkSync Era Testnet, with timeouts and 503 errors. We will provide updates as more information becomes available.

  2. resolved Aug 27, 2026, 02:58 PM UTC

    This incident has been resolved. zkSync Sepolia is operating normally.

Read the full incident report →

Notice August 27, 2026 HyperLiquid Testnet - Degraded Performance 24m HyperEVM - Testnet

Started Aug 27, 2026, 11:42 AM UTC· resolved Aug 27, 2026, 12:06 PM UTC

  1. investigating Aug 27, 2026, 11:42 AM UTC

    We've identified an upstream issue causing timeouts and 503 errors on HyperLiquid Testnet. Updates to follow.

  2. resolved Aug 27, 2026, 12:06 PM UTC

    This incident has been resolved. HyperLiquid - HyperEVM-Testnet is operating normally.

Read the full incident report →

Minor August 26, 2026 Stellar Mainnet JSON-RPC Degraded Performance 9h 48m Stellar - Mainnet

Started Aug 26, 2026, 02:13 PM UTC· resolved Aug 27, 2026, 12:02 AM UTC

  1. investigating Aug 26, 2026, 02:13 PM UTC

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

  2. monitoring Aug 26, 2026, 02:33 PM UTC

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

  3. resolved Aug 27, 2026, 12:02 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 24, 2026 [Urgent] Moca - Testnet - Upgrade to v1.4.0 –

Started Aug 24, 2026, 12:30 PM UTC· resolved Aug 24, 2026, 12:30 PM UTC

  1. resolved Aug 24, 2026, 02:33 PM UTC

    We are upgraded our Moca Testnet infrastructure to v1.4.0. This is a coordinated network upgrade that bundles a broad set of fixes across the storage, payment, and permission modules, along with a scheduled hardfork handler. During the maintenance window, brief interruptions to RPC may have occurred. RPC Changes: - Address validation is now stricter across the board — a dedicated 20-byte address verifier is enforced, so malformed addresses that were previously accepted by some endpoints will now be rejected. - Permission checks for resource-pattern matching have been corrected, including how empty-Resources permissions are scoped — this may change authorization results returned for some API calls. - CopyObject behavior now aligns with CreateObject's destination handling, so copy operations resolve destination buckets/objects consistently. - Payment settlement logic has been corrected around frozen and resuming accounts, which may affect balance and settlement figures returned for impacted accounts. Release: https://github.com/mocachain/moca/releases/tag/v1.4.0

Read the full incident report →

Notice August 24, 2026 Moca Testnet Degraded Performance 57m Moca - Testnet, Moca Testnet - REST API, Moca Testnet - Websockets API

Started Aug 24, 2026, 12:17 PM UTC· resolved Aug 24, 2026, 01:15 PM UTC

  1. investigating Aug 24, 2026, 12:17 PM UTC

    We are currently investigating degraded performance on Moca Testnet, with elevated latency and 503 errors. We will provide updates as more information becomes available.

  2. monitoring Aug 24, 2026, 12:48 PM UTC

    A fix has been implemented and services have returned to normal. We are monitoring closely to ensure stability.

  3. resolved Aug 24, 2026, 01:15 PM UTC

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

Read the full incident report →

Notice August 24, 2026 Stacks Mainnet Degraded Performance 1h 16m Stacks - Mainnet, Mainnet — Websockets API

Started Aug 24, 2026, 12:07 PM UTC· resolved Aug 24, 2026, 01:24 PM UTC

  1. investigating Aug 24, 2026, 12:07 PM UTC

    We are currently investigating degraded performance on Stacks Mainnet, with elevated latency and 503 errors. We will provide updates as more information becomes available.

  2. monitoring Aug 24, 2026, 12:53 PM UTC

    A fix has been implemented and services have returned to normal. We are monitoring closely to ensure stability.

  3. resolved Aug 24, 2026, 01:24 PM UTC

    This incident has been resolved. Stacks Mainnet is operating normally.

Read the full incident report →

Notice August 23, 2026 XRPL EVM Mainnet — Block Height Stalled 18h 58m XRPL EVM - Mainnet, XRPL EVM Mainnet - Websocket API

Started Aug 23, 2026, 06:42 AM UTC· resolved Aug 24, 2026, 01:40 AM UTC

  1. identified Aug 23, 2026, 06:42 AM UTC

    We are following up with the Foundation and working toward restoring normal block progression. Further updates will be provided as the situation develops.

  2. resolved Aug 24, 2026, 01:40 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 22, 2026 Flow Mainnet Degradation 29m Flow - Mainnet, gRPC, Mainnet — Webhooks, Mainnet — Streams

Started Aug 22, 2026, 02:31 AM UTC· resolved Aug 22, 2026, 03:00 AM UTC

  1. identified Aug 22, 2026, 02:31 AM UTC

    We have investigated degradation and identified the cause on archive nodes related to an upstream issue.

  2. resolved Aug 22, 2026, 04:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 21, 2026 Arbitrum Mainnet - Elevated 503 Errors 7h 3m Arbitrum - Mainnet Classic, Mainnet Classic — WebSocket API

Started Aug 21, 2026, 10:30 AM UTC· resolved Aug 21, 2026, 05:34 PM UTC

  1. investigating Aug 21, 2026, 02:15 PM UTC

    We are investigating the degradation of Arbitrum Mainnet archive requests. Users may experience elevated latenc, 503 responses, and API errors during this time.

  2. monitoring Aug 21, 2026, 03:33 PM UTC

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

  3. resolved Aug 21, 2026, 05:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 20, 2026 BNB Smart Chain Mainnet - Elevated API Errors (eth_getLogs) 19m BNB - Mainnet, Mainnet — WebSocket API, Mainnet — Webhooks, Mainnet — Streams

Started Aug 20, 2026, 05:40 PM UTC· resolved Aug 20, 2026, 06:00 PM UTC

  1. investigating Aug 20, 2026, 05:53 PM UTC

    We are investigating an elevated rate of 503 errors affecting eth_getLogs requests on BNB Smart Chain Mainnet. We will update this page as we acquire new information.

  2. resolved Aug 21, 2026, 05:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 20, 2026 Polygon Amoy - Scheduled Stress Test 10h 15m Polygon - Amoy Testnet, Amoy — Websockets API, Amoy — Webhooks, Amoy — Streams

Started Aug 20, 2026, 02:38 PM UTC· resolved Aug 21, 2026, 12:53 AM UTC

  1. investigating Aug 20, 2026, 02:38 PM UTC

    The Polygon Foundation is running a stress test on the Amoy network at 15:00 UTC. Users may experience elevated latencies and degraded performance during the duration of the stress test. We will keep this page updated as the test progresses.

  2. identified Aug 20, 2026, 03:51 PM UTC

    The Polygon Foundation is currently running a stress test on the Amoy network. Users may experience elevated latencies, 503 responses and degraded performance during the duration of the stress test. Our team is working to resolve the degradation and we will follow up on this page with further updates.

  3. monitoring Aug 20, 2026, 05:34 PM UTC

    The degraded performance and 503 responses for Polygon Amoy have been resolved. We are monitoring for stability.

  4. resolved Aug 21, 2026, 12:53 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 20, 2026 BNB Smart Chain Mainnet , Degraded Archive RPC Performance 4h 23m BNB - Mainnet, Mainnet — WebSocket API, Mainnet — Webhooks, Mainnet — Streams

Started Aug 20, 2026, 10:52 AM UTC· resolved Aug 20, 2026, 03:15 PM UTC

  1. investigating Aug 20, 2026, 10:52 AM UTC

    BSC Mainnet is experiencing degraded performance on archive RPC methods. Some requests for historical data (trace, debug, and historical state lookups) may see increased latency or intermittent 503 errors. We are monitoring the situation and working on a resolution.

  2. monitoring Aug 20, 2026, 01:10 PM UTC

    Performance on archive RPC methods has improved significantly. We are continuing to monitor the situation.

  3. resolved Aug 20, 2026, 03:15 PM UTC

    This incident has been resolved. Archive RPC methods are operating normally across all regions. We will continue to monitor for any recurrence.

Read the full incident report →

Notice August 18, 2026 Base Sepolia - Degraded Performance 4d 20h Base - Sepolia, Sepolia - WebSocket API, Sepolia —Webhooks, Sepolia — Streams

Started Aug 18, 2026, 06:01 PM UTC· resolved Aug 23, 2026, 02:10 PM UTC

  1. investigating Aug 18, 2026, 01:42 AM UTC

    The Quicknode team is investigating degraded performance of Base Sepolia in FRA region. We will follow up once we have more updates.

  2. monitoring Aug 18, 2026, 01:45 AM UTC

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

  3. investigating Aug 18, 2026, 06:08 PM UTC

    The Quicknode team is investigating degraded performance of Base Sepolia. Users may observe 503 responses from their requests. We will follow up once we have more updates.

  4. identified Aug 19, 2026, 06:32 AM UTC

    Customers may experience higher error rates, including 503 responses. We are in active communication with the Foundation and waiting for a new release to mitigate this. Further updates will be provided as the situation develops.

  5. investigating Aug 19, 2026, 09:52 AM UTC

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

  6. identified Aug 21, 2026, 05:46 PM UTC

    Our team is actively listening to updates from the Base team regarding Base Sepolia degradation. A fix has been identified and is being implemented by the Base team for the Base node client. We will update this page as we receive further updates.

  7. resolved Aug 23, 2026, 02:10 PM UTC

    The issue has been resolved and Base Sepolia services are operating normally.

Read the full incident report →

Minor August 18, 2026 Monad RPC elevated error rates 14m Monad - Mainnet, Mainnet - Streams, Mainnet - Websockets API, Mainnet - Webhooks

Started Aug 18, 2026, 04:06 PM UTC· resolved Aug 18, 2026, 04:20 PM UTC

  1. monitoring Aug 18, 2026, 04:06 PM UTC

    We identified an issue causing elevated error rates for Monad RPC requests. Our team has deployed a fix, and error rates have returned to normal. We are continuing to monitor the service to ensure stability.

  2. resolved Aug 18, 2026, 06:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 17, 2026 Hyperliquid EVM Testnet, Service Disruption 37m HyperEVM - Testnet

Started Aug 17, 2026, 10:40 AM UTC· resolved Aug 17, 2026, 11:18 AM UTC

  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 1h 10m Stacks - Mainnet, Mainnet — Websockets API

Started Aug 16, 2026, 11:05 AM UTC· resolved Aug 16, 2026, 12:16 PM UTC

  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 5h 44m Arbitrum - Mainnet Nitro, Mainnet Nitro — WebSocket API, Mainnet — Webhooks, Mainnet — Streams

Started Aug 14, 2026, 05:30 PM UTC· resolved Aug 14, 2026, 11:14 PM UTC

  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 9h 25m Flare - Mainnet

Started Aug 12, 2026, 03:42 PM UTC· resolved Aug 13, 2026, 01:08 AM UTC

  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 16h 35m

Started Aug 12, 2026, 04:00 AM UTC· resolved Aug 12, 2026, 08:35 PM UTC

  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 →