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 November 10, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · every 60s1 active incident

Know the moment Quicknode breaks

Quicknode is healthy right now. We keep checking (every 60 seconds) and email you when 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), and outage reports from engineers. How PulsAPI monitoring works

Status report

Quicknode Status Summary

As of 02:54 UTC on 10 November 2026, Quicknode is operational. PulsAPI checked Quicknode's official status page and found 155 of 155 components operational, with 1 active incident. Over the last 30 days PulsAPI measured 100.00% uptime for Quicknode, counting degraded performance as up. The latest incident, "Elysium Mainnet – Elevated Errors on eth_sendRawTransaction", was on Nov 9, 2026 and lasted 33 min.

Cite as: PulsAPI, “Quicknode status”, checked 10 November 2026, 02:54 UTC. https://www.pulsapi.com/services/quicknode

Quicknode Component Status

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

155operational
0g » 0g - Galileo Testnet
Operational
0g » 0g - Mainnet
Operational
Abstract » Abstract - Mainnet
Operational

152 more components tracked

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

Also tracking Abstract » Abstract - Testnet, Aleo » Aleo - Mainnet, Aleo » Aleo - Testnet, Aptos » Aptos - Mainnet, Aptos » Aptos - Testnet, Arbitrum Nova » Arbitrum Nova - Mainnet, Arbitrum » Arbitrum - Mainnet Classic, Arbitrum » Arbitrum - Mainnet Nitro, Arbitrum » Arbitrum - Sepolia, Arc » Arc - Mainnet, Arc » Arc - Testnet, Ault » Ault - Mainnet, and 140 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.

Elysium Mainnet – Elevated Errors on eth_sendRawTransactionResolved Nov 9, 2026 · 33 minResolved

This incident has been resolved. --- [2026-11-09T23:41:01.040Z] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-11-09T23:23:25.711Z] (identified) The issue has been identified and a fix is being implemented. --- [2026-11-09T23:28:49.603Z] (investigating) We are investigating an issue affecting Elysium Mainnet where users are experiencing 429 and 403 errors on eth_sendRawTransaction requests. We will provide updates as we learn more.

RPC Logs - Service DisruptionResolved Nov 9, 2026 · 49 minResolved

The issue affecting RPC Logs has been resolved. Transaction and error logs are now operating normally. Please note that log data may show inaccuracies roughly between 15:10 UTC - 16:25 UTC. We apologize for any inconvenience caused. --- [2026-11-09T15:54:06.694Z] (investigating) We are investigating an issue affecting transaction and error log serving. Our engineers are actively working on a fix and will provide updates as more information becomes available.

Elysium Mainnet – Transaction Submission ErrorsResolved Nov 9, 2026 · 46 minResolved

Transaction submission on Elysium mainnet is working normally again. The issue was caused by rate limiting at the upstream sequencer. --- [2026-11-09T15:05:53.316Z] (monitoring) A fix has been implemented and we are monitoring. --- [2026-11-09T14:59:59.497Z] (identified) Some customers may see 429 errors when sending transactions (eth_sendRawTransaction) on Elysium mainnet. These errors are coming from rate limiting at the upstream sequencer level. Read requests are not affected. We've identified the cause and the team is working on it as a top priority. We'll post an update as soon as it's resolved.

Upcoming maintenance

Announced by Quicknode. Planned work, not an outage.

Urgent Sei - Atlantic (Testnet) - Upgrade to v6.8Scheduled for Nov 10, 2026 · 2h 0mScheduled

Sei Atlantic (testnet) will be undergoing a netowrk upgrade to v6.8 on 2026-11-10 ~16 UTC. This release removes the Cosmos gRPC and gRPC-Web servers, Rosetta, and the tokenfactory module; state proofs are now off by default. Per-IP RPC rate limiting is enabled by default on EVM JSON-RPC and CometBFT RPC endpoints. Brief interruptions to RPC availability may occur on that date. RPC Changes: - batch_request_limit — EVM JSON-RPC batch_request_limit default has been reduced from 1000 to 100; requests exceeding this limit will be rejected. - Cosmos gRPC and gRPC-Web — These servers have been removed from seid and are no longer available. - Rosetta API — The Rosetta API has been removed and is no longer available. - per-IP rate limiting — EVM JSON-RPC and CometBFT RPC now enforce per-IP rate limiting by default; users behind reverse proxies or load balancers may experience rate-limit errors if proxy IP configuration is not set.

[Standard] Stacks - Mainnet & Testnet - Upgrade API to v9.9.0Scheduled for Nov 11, 2026 · 23h 59mScheduled

We are upgrading our Stacks Mainnet infrastructure to stacks-blockchain-api v9.8.0 on 2026-11-11. This feature release adds transaction type filtering and fee-based sorting to transaction endpoints, and resolves performance issues causing timeouts on supply endpoints. Brief interruptions to RPC availability may occur on that date. RPC Changes: - GET /extended/v3/transactions — New type filter parameter allows filtering transactions by type. - GET /extended/v3/mempool/transactions — New type filter parameter allows filtering mempool transactions by type; new sort_by=fee option enables sorting by transaction fee. - GET /extended/v1/stx_supply — Performance improvements resolve timeout issues on this endpoint. https://github.com/hirosystems/stacks-blockchain-api/releases/tag/v9.8.0

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 history91 days observed
Aug 12100.00% average · 55 days with incidentsNov 10

Going further back: Quicknode uptime by month and every recorded Quicknode outage.

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 it every 60 seconds.

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 it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Quicknode components?

Yes. PulsAPI monitors 155 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

2660+ 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