Quicknode logo

Is Quicknode Down?

SaaSLive status, outages, and incident history

No. Quicknode is up right now.

Every monitored Quicknode system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 3m agoLive · 60s while moving

Know the moment Quicknode breaks

Quicknode is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

Official Quicknode status page
How we know: the official Quicknode status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Quicknode Component Status

The main Quicknode systems on this page. All 533 are operational right now.

533operational
0g (Beta) » 0g - Galileo Testnet
Operational
0g (Beta) » 0G - Mainnet
Operational
0g (Beta) » 0g - Mainnet
Operational

530 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking 0g (Beta) » 0G Mainnet — JSON-RPC API, 0g (Beta) » 0G Mainnet — Streams, 0g (Beta) » 0G Mainnet — Webhooks, 0g (Beta) » 0G Mainnet — WebSocket API, 0g (Beta) » Galileo — JSON-RPC API, 0g (Beta) » Galileo — Streams, 0g (Beta) » Galileo — Webhooks, 0g (Beta) » Galileo — WebSocket API, Abstract (Beta) » Abstract - Mainnet, Abstract (Beta) » Abstract - Testnet, Abstract (Beta) » Mainnet — JSON-RPC API, Abstract (Beta) » Mainnet — Webhooks, and 518 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Quicknode Outages & Incidents

Incident history from the official Quicknode status page, including resolution updates.

[Standard] Ethereum Hoodi and Sepolia - Upgrade to Reth v2.6.0Scheduled for Oct 1, 2026 · 24h 0mScheduled

We are upgrading our Ethereum Hoodi and Sepolia infrastructure to Reth v2.6.0 on 2026-10-01. This release expands Amsterdam and Bogotá protocol support, advances snap-sync infrastructure, and delivers significant performance improvements across block processing and historical-state RPC queries. Brief interruptions to RPC availability may occur on that date. RPC Changes: - eth_getLogs — Returns an error when matching receipts have been pruned instead of incomplete results. Additionally, memory and CPU overhead have been reduced through windowing and bloom-filtering optimizations. - eth_estimateGas — Basic-transfer shortcut now returns actual used gas, fixing post-Amsterdam overestimation of up to 75%. - eth_callBundle — Now derives the next-block base fee for bundle simulation. - Transaction submission and signing — Rejects a caller-supplied chainId that does not match the node, preventing accidental cross-chain resubmission. - EIP-7702 authorization — Returns null for sender-nonce gaps consumed by authorization entries. - Transaction pool — Pending blob transactions are now parked when blob fee rises while base fee falls. Configured minimum priority fee is enforced for local transactions, and transactions below tracked sender nonce are rejected when enabled. https://github.com/paradigmxyz/reth/releases/tag/v2.6.0

[Standard] Zcash Mainnet - Upgrade to Zebra 6.4.0Scheduled for Oct 1, 2026 · 24h 0mScheduled

We are upgrading our Zcash Mainnet infrastructure to Zebra 6.4.0 on 2026-10-01. This release improves block template performance through precomputation, and includes multiple security and stability fixes. Brief interruptions to RPC availability may occur on that date. RPC Changes: - getblocktemplate — Now uses precomputed block templates for the current chain tip when available, refreshed on tip changes and periodically, reducing latency for miners; templates may be a few seconds behind the mempool but are validated against the committed tip. - getstandardfee — Reports updated conventional fee of 1000 zatoshis per ZIP-317 logical action (down from 5000; 2000 instead of 10000 for a minimal transaction). - z_gettreestate — No longer returns null commitments for blocks moved to a side chain during concurrent reorgs. - RPC response body size — `rpc.max_response_body_size` is now capped at 4,294,967,295 bytes; larger configured values are rejected during configuration loading. https://github.com/ZcashFoundation/zebra/releases/tag/v6.4.0

[Standard] 0g - Mainnet - Upgrade to v1.0.7Scheduled for Oct 1, 2026 · 24h 0mScheduled

We are upgrading our 0g Mainnet infrastructure to Aristotle v1.0.7 on 2026-10-01. This is an RPC-only release that fixes a critical correctness bug in eth_estimateGas and removes a CPU-amplification vector in the gas estimator. No consensus or state-transition changes are included. Brief interruptions to RPC availability may occur on that date. RPC Changes: - eth_estimateGas — Fixed critical bug where gas estimates were being seeded from post-settlement gas (raising gas_used to 80% of the cap), causing the method to return cap-sized limits instead of actual usage. This resulted in gas estimates up to ~850× too large. Estimates are now seeded from pre-settlement gas, matching 0g-geth behavior. Additionally, EIP-7623 calldata floor computation has been optimized to run once per transaction instead of per frame, eliminating a CPU-amplification vector. https://github.com/0gfoundation/0gchain-Aristotle/releases/tag/v1.0.7

Quicknode Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Quicknode incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 30 days with incidentsSep 25

Live Quicknode Outage Reports

Problems reported by engineers using Quicknode. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Quicknode problems reported yet.

Something wrong with Quicknode on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Quicknode

Quicknode publishes a public status page at status.quicknode.com covering 200 components, including Mainnet — JSON-RPC API, Mainnet Nitro — JSON-RPC API and Mainnet — REST API. PulsAPI tracks Quicknode outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured Quicknode uptime at 100.00%. Response times, incident history, and SLA tracking for Quicknode are available on the PulsAPI dashboard.

Quicknode Status FAQ

Is Quicknode down right now?

The verdict at the top of this page comes from the latest poll of the official Quicknode status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Quicknode is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Quicknode recovers.

How do I check Quicknode uptime history?

PulsAPI tracks Quicknode uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Quicknode changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Quicknode outages?

PulsAPI reads the official Quicknode status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Quicknode components?

Yes. PulsAPI monitors 533 individual Quicknode components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Quicknode goes down?

Yes. Create a free account and subscribe to Quicknode: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Quicknode to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Quicknode problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Quicknode?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Quicknode plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Quicknode with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services