QuickNode Outage History

QuickNode is up right now

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

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

Source: https://status.quicknode.com

Critical April 29, 2026

Solana Priority Fee API: Critical Outage

Detected by Pingoru
Apr 29, 2026, 12:20 AM UTC
Resolved
Apr 29, 2026, 12:55 AM UTC
Duration
34m
Affected: Quicknode Token API
Timeline · 3 updates
  1. investigating Apr 29, 2026, 12:18 AM UTC

    We are currently investigating this issue.

  2. investigating Apr 29, 2026, 12:20 AM UTC

    Quicknode Solana Priority Fee API is currently experiencing an outage. Requests to the API will fail at this time. Our team is actively investigating the issue with priority and will follow up as soon as new information becomes available.

  3. resolved Apr 29, 2026, 12:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 28, 2026

Osmosis Mainnet : Degraded Performance

Detected by Pingoru
Apr 28, 2026, 02:15 AM UTC
Resolved
May 02, 2026, 08:24 AM UTC
Duration
4d 6h
Affected: Mainnet — JSON-RPC APIMainnet — Websockets API
Timeline · 5 updates
  1. identified Apr 23, 2026, 04:48 PM UTC

    The Quicknode team is aware of the degraded performance on Osmosis Mainnet. This issue has been identified and our team is actively working on resolving the issue. Users may experience sporadic 503 errors during this time. We will update this page as we acquire new information.

  2. monitoring Apr 28, 2026, 01:07 AM UTC

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

  3. identified Apr 28, 2026, 02:26 AM UTC

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

  4. monitoring Apr 30, 2026, 07:06 AM UTC

    The Quicknode team is actively working with the foundation team on this. Nodes have recovered, but you may experience intermittent degraded performance for gRPC calls. We are monitoring performance to ensure stability.

  5. resolved May 02, 2026, 08:24 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 27, 2026

Polkadot Mainnet FRA Region - Degraded Performance

Detected by Pingoru
Apr 27, 2026, 08:09 PM UTC
Resolved
Apr 27, 2026, 11:21 PM UTC
Duration
3h 12m
Affected: Mainnet - JSON RPC APIMainnet - Websockets APIMainnet - substrate-api-sidecar
Timeline · 3 updates
  1. investigating Apr 27, 2026, 08:09 PM UTC

    The QuickNode team is investigating degraded performance of Polkadot Mainnet in FRA region. We are seeing elevated 503 errors at this time.

  2. identified Apr 27, 2026, 08:35 PM UTC

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

  3. resolved Apr 27, 2026, 11:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 27, 2026

Fantom mainnet- Block Height Stall

Detected by Pingoru
Apr 27, 2026, 12:01 PM UTC
Resolved
Apr 28, 2026, 07:20 AM UTC
Duration
19h 18m
Affected: Mainnet — JSON-RPC APIMainnet — Websockets APIMainnet — WebhooksMainnet — Streams
Timeline · 3 updates
  1. investigating Apr 27, 2026, 12:01 PM UTC

    We are aware of an issue affecting Fantom nodes where block height has stalled. Our team is currently investigating the root cause. Users may experience stale responses or inconsistent block data. We apologize for any inconvenience and will share an update as soon as we have more information.

  2. identified Apr 27, 2026, 06:10 PM UTC

    Engineers have identified the issue and are actively working on a fix for Fantom nodes where block height has stalled. Users may experience stale responses or inconsistent block data in the meantime. We’ll provide another update as progress is made.

  3. resolved Apr 28, 2026, 07:20 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 26, 2026

Identified – Singapore Region Node Disruption

Detected by Pingoru
Apr 26, 2026, 02:02 PM UTC
Resolved
Apr 26, 2026, 05:20 PM UTC
Duration
3h 17m
Affected: Mainnet — JSON-RPC APIMainnet — JSON-RPC APISepolia — JSON-RPC API
Timeline · 3 updates
  1. investigating Apr 26, 2026, 02:02 PM UTC

    We have identified a disruption affecting nodes hosted in the Singapore region. The issue was caused by a shutdown of several instances by our cloud infrastructure provider. Affected nodes are coming back online and re-syncing. Our team is actively monitoring recovery.

  2. monitoring Apr 26, 2026, 03:32 PM UTC

    The situation is now stabilized. Affected nodes in the Singapore region are back online and services are recovering as expected. Our team continues to monitor the environment closely to ensure full stability. We will confirm full resolution once all nodes have been verified healthy.

  3. resolved Apr 26, 2026, 05:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 24, 2026

Solana Testnet Scheduled Maintenance (Apr 23, 2026 14:00 UTC)

Detected by Pingoru
Apr 24, 2026, 03:17 PM UTC
Resolved
Apr 25, 2026, 06:59 PM UTC
Duration
1d 3h
Affected: Testnet — JSON-RPC APITestnet — Websockets APITestnet — StreamsTestnet — Webhooks
Timeline · 2 updates
  1. monitoring Apr 24, 2026, 03:17 PM UTC

    The Solana Testnet Network has restarted following the network upgrade. We are monitoring for stability.

  2. resolved May 14, 2026, 06:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 24, 2026

Quicknode Streams : Degraded performance

Detected by Pingoru
Apr 24, 2026, 02:45 AM UTC
Resolved
Apr 24, 2026, 05:33 AM UTC
Duration
2h 47m
Affected: Quicknode Streams
Timeline · 4 updates
  1. investigating Apr 24, 2026, 04:02 AM UTC

    We are currently investigating this issue.

  2. identified Apr 24, 2026, 05:33 AM UTC

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

  3. monitoring Apr 24, 2026, 05:33 AM UTC

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

  4. resolved Apr 24, 2026, 05:33 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 22, 2026

Solana Mainnet FRA Region - Degraded Performance

Detected by Pingoru
Apr 22, 2026, 11:01 PM UTC
Resolved
Apr 23, 2026, 08:02 AM UTC
Duration
9h
Affected: Mainnet — JSON-RPC APIMainnet — Websockets APIMainnet — StreamsMainnet — Webhooks
Timeline · 3 updates
  1. investigating Apr 22, 2026, 11:01 PM UTC

    Quicknode team is investigating degraded performance of Solana Mainnet in Frankfurt region. We will update this page as we acquire new information. Users may experience temporary 503 responses at this time.

  2. monitoring Apr 23, 2026, 06:40 AM UTC

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

  3. resolved Apr 23, 2026, 08:02 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 22, 2026

Degraded Performance - Polkadot Mainnet NRT Region

Detected by Pingoru
Apr 22, 2026, 08:10 PM UTC
Resolved
Apr 22, 2026, 09:15 PM UTC
Duration
1h 5m
Affected: Mainnet - JSON RPC APIMainnet - Websockets APIMainnet - substrate-api-sidecar
Timeline · 3 updates
  1. investigating Apr 22, 2026, 08:10 PM UTC

    The Quicknode team is investigating the degraded performance of Polkadot Mainnet in the NRT region. We will update this page as we acquire new information. Users may be served 503s at this time in the affected region.

  2. monitoring Apr 22, 2026, 08:44 PM UTC

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

  3. resolved Apr 22, 2026, 09:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 22, 2026

Degraded Performance - Polygon Mainnet NRT Region

Detected by Pingoru
Apr 22, 2026, 03:09 PM UTC
Resolved
Apr 22, 2026, 09:15 PM UTC
Duration
6h 5m
Affected: Mainnet — JSON-RPC APIMainnet — Websockets APIMainnet — WebhooksMainnet — Streams
Timeline · 3 updates
  1. investigating Apr 22, 2026, 03:09 PM UTC

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

  2. monitoring Apr 22, 2026, 03:33 PM UTC

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

  3. resolved Apr 22, 2026, 09:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 21, 2026

Degraded Performance - Solana Mainnet

Detected by Pingoru
Apr 21, 2026, 04:12 PM UTC
Resolved
Apr 21, 2026, 10:14 PM UTC
Duration
6h 2m
Affected: Mainnet — JSON-RPC APIMainnet — Websockets APIMainnet — StreamsMainnet — Webhooks
Timeline · 3 updates
  1. investigating Apr 21, 2026, 04:12 PM UTC

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

  2. monitoring Apr 21, 2026, 04:30 PM UTC

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

  3. resolved Apr 21, 2026, 10:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 21, 2026

Solana Mainnet Degraded Performance

Detected by Pingoru
Apr 21, 2026, 01:28 AM UTC
Resolved
Apr 21, 2026, 04:31 AM UTC
Duration
3h 2m
Affected: Mainnet — JSON-RPC APIMainnet — Websockets APIMainnet — StreamsMainnet — Webhooks
Timeline · 5 updates
  1. investigating Apr 21, 2026, 01:28 AM UTC

    The QuickNode team is investigating the degraded performance of Solana Mainnet. We are seeing elevated 503 errors at this time. We will update this page as we acquire new information.

  2. investigating Apr 21, 2026, 02:02 AM UTC

    We are continuing to investigate this issue. We will post another update at 02:30 UTC.

  3. identified Apr 21, 2026, 02:53 AM UTC

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

  4. monitoring Apr 21, 2026, 02:53 AM UTC

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

  5. resolved Apr 21, 2026, 04:31 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 21, 2026

Base Sepolia - Increase in `instrinsic gas too high` Errors on eth_estimateGas calls

Detected by Pingoru
Apr 21, 2026, 12:30 AM UTC
Resolved
Apr 21, 2026, 08:11 AM UTC
Duration
7h 41m
Affected: Sepolia - JSON-RPC APISepolia - WebSocket API
Timeline · 4 updates
  1. investigating Apr 20, 2026, 07:43 PM UTC

    We are investigating an increase in `instrinsic gas too high` API errors on `eth_estimateGas` requests on Base Sepolia that started with the Sepolia Azul Upgrade at 18 UTC today. We are working with the Base team to address this issue and will update this status with findings and resolution ASAP.

  2. identified Apr 21, 2026, 08:09 AM UTC

    Foundation cut a new release with a couple of bug fixes for Azul (latest hardfork) on Base Sepolia. https://github.com/base/base/releases/tag/v0.7.6

  3. monitoring Apr 21, 2026, 08:11 AM UTC

    Our engineers completed upgrading the Base Sepolia node infrastructure to 0.7.6 https://github.com/base/base/releases/tag/v0.7.6

  4. resolved Apr 21, 2026, 08:11 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 20, 2026

TON Mainnet Degraded Performance

Detected by Pingoru
Apr 20, 2026, 09:48 AM UTC
Resolved
Apr 30, 2026, 06:09 PM UTC
Duration
10d 8h
Affected: Mainnet — REST API
Timeline · 8 updates
  1. investigating Apr 20, 2026, 09:48 AM UTC

    We are aware of an issue affecting TON Mainnet endpoints. Some users may experience elevated error rates, increased latency, or failed requests. Our team is actively investigating the root cause and working to restore full service as quickly as possible. We apologize for any inconvenience and will post updates as the situation develops.

  2. identified Apr 20, 2026, 11:50 AM UTC

    The TON Foundation has confirmed this is an upstream network issue affecting multiple providers. Their engineering team has been notified and is actively working on a resolution. We will continue to monitor the situation and provide updates as soon as we have more information.

  3. identified Apr 21, 2026, 08:13 AM UTC

    Our engineers are working closely with the TON Foundation. We’ll provide the next update by 5 PM UTC.

  4. identified Apr 21, 2026, 05:52 PM UTC

    Our engineers are working closely with the TON Foundation. We are awaiting a new TON client upgrade release from the foundation that will resolve the issue. We will update this page once we receive further updates from the foundation.

  5. identified Apr 23, 2026, 11:34 AM UTC

    The TON Foundation has identified the root cause as liteserver synchronization instability affecting multiple operators. An interim update has been made available for Lite Server and Full Node operators to improve stability and reduce sync issues but a full resolution requires a validator update from the TON Foundation, which is expected on April 28. We will continue to update this page as the situation progresses.

  6. identified Apr 28, 2026, 03:42 PM UTC

    The Ton Foundation has provided a new upgrade today to address the issues regarding Lite Servers experiencing synchronization instability. Our team will be upgrading to the newest version and we will update this page with further updates as we progress.

  7. monitoring Apr 30, 2026, 07:01 AM UTC

    The Quicknode team has been upgrading nodes to the latest version from the foundation team and is monitoring performance to ensure stability.

  8. resolved Apr 30, 2026, 06:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 18, 2026

Stacks Testnet: Block Height Stalled at 3,959,436

Detected by Pingoru
Apr 18, 2026, 10:52 PM UTC
Resolved
Apr 19, 2026, 10:34 PM UTC
Duration
23h 41m
Affected: Testnet — REST APITestnet — Websockets API
Timeline · 2 updates
  1. investigating Apr 18, 2026, 10:52 PM UTC

    We are currently investigating this issue. Users requesting data beyond this block will experience 503s. The Quicknode team is investigating and will update with more information once it is available.

  2. resolved Apr 19, 2026, 01:34 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 17, 2026

Polygon Amoy: Archive Nodes Stalled at Block 36,805,071

Detected by Pingoru
Apr 17, 2026, 09:38 PM UTC
Resolved
Apr 17, 2026, 11:01 PM UTC
Duration
1h 22m
Affected: Amoy — JSON-RPC APIAmoy — Websockets APIAmoy — WebhooksAmoy — Streams
Timeline · 2 updates
  1. investigating Apr 17, 2026, 09:38 PM UTC

    Polygon Amoy archive nodes are currently stalled at block 36,805,071. Requests for historical data following this block will result in 503s. Users querying tip data are not affected. Our team is actively investigating the cause with priority and we'll provide updates as new information becomes available.

  2. resolved Apr 17, 2026, 11:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 16, 2026

Base Sepolia - Stuck Network at Block 40297498

Detected by Pingoru
Apr 16, 2026, 06:30 PM UTC
Resolved
Apr 16, 2026, 09:57 PM UTC
Duration
3h 27m
Affected: Sepolia - JSON-RPC APISepolia - WebSocket APISepolia —WebhooksSepolia — Streams
Timeline · 2 updates
  1. investigating Apr 16, 2026, 06:30 PM UTC

    The Base Sepolia Network appears to have stalled at block 40297498 - This is not limited to Quicknode and is a network wide stall. The Quicknode team is investigating and will update with more information once it is available. You can follow the official Base Status Page for further information: https://status.base.org/incidents/l6d3mnl0c9hs

  2. resolved Apr 16, 2026, 09:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 15, 2026

Quicknode Platform Services - Service Disruption

Detected by Pingoru
Apr 15, 2026, 12:19 PM UTC
Resolved
Apr 15, 2026, 03:34 PM UTC
Duration
3h 14m
Affected: Quicknode StreamsQuicknode Webhooks
Timeline · 3 updates
  1. investigating Apr 15, 2026, 12:19 PM UTC

    We are currently experiencing service disruptions affecting multiple Quicknode platform services. Affected services include Dashboard, Streams, Webhooks, and KV REST APIs. Customers may be unable to access these services. Quicknode RPC endpoints remain fully operational. Only platform management services are affected. Our engineering team is actively investigating and working to restore these services. We will provide the next update by 2PM UTC or sooner.

  2. monitoring Apr 15, 2026, 12:31 PM UTC

    Update: The issue affecting Dashboard, Streams, Webhooks, and KV REST APIs appears to be resolved. Services have been restored and are operational. Our DevEx team is actively monitoring to ensure full service stability. We will provide a final update once monitoring is complete.

  3. resolved Apr 15, 2026, 03:34 PM UTC

    The service disruption affecting Dashboard, Streams, Webhooks, and KV REST APIs has been resolved. All platform services are fully operational. We apologize for any inconvenience this may have caused and thank you for your patience.

Read the full incident report →

Notice April 14, 2026

Stuck Network - Solana Devnet

Detected by Pingoru
Apr 14, 2026, 04:30 AM UTC
Resolved
Apr 14, 2026, 03:36 PM UTC
Duration
11h 5m
Affected: Devnet — JSON-RPC APIDevnet — Websockets APIDevnet — WebhooksDevnet — Streams
Timeline · 4 updates
  1. investigating Apr 14, 2026, 04:30 AM UTC

    Solana Devnet is currently stalled at block 455,406,479. This has been confirmed as a network-wide issue and is expected, according to the foundation team. QuickNode is awaiting further guidance and will provide updates as more information becomes available.

  2. identified Apr 14, 2026, 05:00 AM UTC

    The QuickNode team is currently following the foundation team's guidance to recover the nodes and will provide further updates as more information becomes available.

  3. monitoring Apr 14, 2026, 07:42 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.

  4. resolved Apr 14, 2026, 03:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 12, 2026

Investigating | Dashboard, Streams & KV Store REST API

Detected by Pingoru
Apr 12, 2026, 08:55 AM UTC
Resolved
Apr 12, 2026, 04:19 PM UTC
Duration
7h 24m
Affected: QuickNode Dashboard
Timeline · 3 updates
  1. investigating Apr 12, 2026, 08:55 AM UTC

    We are currently investigating an issue intermittently affecting the QuickNode Dashboard, Streams, and KV Store REST API. Some customers may experience degraded performance or errors. Our team is actively working to identify the root cause. We will provide updates as more information becomes available.

  2. monitoring Apr 12, 2026, 09:45 AM UTC

    The issue intermittently affecting the QuickNode Dashboard, Streams, and KV Store REST API has been resolved. Services have recovered and are operating normally. Our team will continue to monitor the situation closely to ensure stability is maintained. We apologize for any inconvenience this may have caused.

  3. resolved Apr 12, 2026, 04:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 10, 2026

Degraded Performance - Polygon Amoy Debug and Archive Requests

Detected by Pingoru
Apr 10, 2026, 03:52 PM UTC
Resolved
Apr 10, 2026, 08:29 PM UTC
Duration
4h 37m
Affected: Amoy — JSON-RPC APIAmoy — Websockets APIAmoy — WebhooksAmoy — Streams
Timeline · 4 updates
  1. investigating Apr 10, 2026, 03:52 PM UTC

    The QuickNode team is investigating the degraded performance of Polygon Amoy archive and debug requests - we will update this page as we acquire new information. Users may experience 503s during this time for archive and debug RPC calls.

  2. identified Apr 10, 2026, 04:34 PM UTC

    The Quicknode team has identified the cause of the degraded performance of Polygon Amoy archive and debug requests and our engineers are applying a fix. Users may still experience 503s during this time for archive and debug RPC calls.

  3. monitoring Apr 10, 2026, 06:20 PM UTC

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

  4. resolved Apr 10, 2026, 08:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 9, 2026

Fuel Sepolia - Stuck Network

Detected by Pingoru
Apr 09, 2026, 10:10 PM UTC
Resolved
Apr 09, 2026, 10:53 PM UTC
Duration
43m
Affected: Sepolia — GraphQL API
Timeline · 2 updates
  1. investigating Apr 09, 2026, 10:10 PM UTC

    Fuel Sepolia network appears to have stalled at block 59,643,457. The QuickNode team is investigating and will update with more information once it is available.

  2. resolved Apr 09, 2026, 10:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 8, 2026

Morph Mainnet – Block Production Halted

Detected by Pingoru
Apr 08, 2026, 08:38 AM UTC
Resolved
Apr 08, 2026, 12:51 PM UTC
Duration
4h 12m
Affected: Mainnet — JSON-RPC APIMainnet — Websockets APIMainnet — StreamsMainnet — Webhooks
Timeline · 3 updates
  1. investigating Apr 08, 2026, 08:38 AM UTC

    We are currently experiencing a service disruption on Morph Mainnet. Block production has halted due to an issue with the sequencer. This incident has been acknowledged by the Morph Foundation, who are actively investigating. We will provide updates as the situation develops.

  2. monitoring Apr 08, 2026, 09:18 AM UTC

    Block production on Morph Mainnet has resumed and nodes are currently catching up and syncing. The Morph Foundation has acknowledged an issue with the sequencer as the root cause of the halt. We are continuing to monitor until full sync is confirmed.

  3. resolved Apr 08, 2026, 12:51 PM UTC

    Block production on Morph Mainnet has fully resumed and nodes are synced. The issue was caused by a sequencer problem acknowledged by the Morph Foundation, who have since resolved it on their end. We will continue to monitor to confirm stability.

Read the full incident report →

Notice April 8, 2026

Morph mainnet : Block height stalled at 22013628

Detected by Pingoru
Apr 08, 2026, 06:15 AM UTC
Resolved
Apr 08, 2026, 06:58 AM UTC
Duration
42m
Affected: Mainnet — JSON-RPC APIMainnet — Websockets APIMainnet — StreamsMainnet — Webhooks
Timeline · 4 updates
  1. investigating Apr 08, 2026, 06:19 AM UTC

    We are currently investigating this issue.

  2. identified Apr 08, 2026, 06:28 AM UTC

    This is a chain-level incident. As our engineers are actively monitoring updates from the Morph Foundation, please find the next update by 8 AM UTC.

  3. monitoring Apr 08, 2026, 06:56 AM UTC

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

  4. resolved Apr 08, 2026, 06:58 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 7, 2026

Degraded Performance - Hedera Mainnet

Detected by Pingoru
Apr 07, 2026, 02:41 PM UTC
Resolved
Apr 08, 2026, 12:50 AM UTC
Duration
10h 8m
Affected: Mainnet - JSON-RPC APIMainnet - REST APIMainnet — StreamsMainnet — Webhooks
Timeline · 2 updates
  1. investigating Apr 07, 2026, 02:41 PM UTC

    The Quicknode team is investigating the degraded performance of Hedera Mainnet - we will update this page as we acquire new information. Users may experience API errors and 503 responses during this time.

  2. resolved Apr 08, 2026, 12:50 AM UTC

    This incident has been resolved.

Read the full incident report →