Skip to main content
Quicknode logo

Is Quicknode Down?

No — Quicknode is up

Reachable from all 8 checked regions

Average response time: 855ms

Last checked · checks run every 6 hours

Official status page: https://status.quicknode.com

Components the vendor reports as affected: Solana - Mainnet Under Maintenance

A component listed here does not necessarily mean a full outage — large providers routinely report maintenance on individual locations. It only affects the verdict above when the vendor marks it major or critical and our own checks also saw Quicknode fail from enough regions to rule out probe noise.

Quicknode uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
847ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 15 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

15-day clean streak
Sep 14: no data
Sep 15: no data
Sep 16: no data
Sep 17: no data
Sep 18: no data
Sep 19: no data
Sep 20: no data
Sep 21: no data
Sep 22: no data
Sep 23: no data
Sep 24: no data
Sep 25: no data
Sep 26: no data
Sep 27: no data
Sep 28: no data
Sep 29: 100.00% uptime, 15 checks
Sep 30: 100.00% uptime, 28 checks
Oct 1: 100.00% uptime, 29 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

dfw
1678ms
DNS 54ms TCP 1ms TLS 9ms TTFB 1657ms
ewr
668ms
DNS 69ms TCP 2ms TLS 12ms TTFB 655ms
fra
781ms
DNS 51ms TCP 2ms TLS 14ms TTFB 764ms
gru
592ms
DNS 164ms TCP 2ms TLS 13ms TTFB 576ms
iad
820ms
DNS 73ms TCP 14ms TLS 22ms TTFB 739ms
jnb
471ms
DNS 34ms TCP 0ms TLS 10ms TTFB 457ms
lax
1113ms
DNS 70ms TCP 62ms TLS 78ms TTFB 794ms
lhr
723ms
DNS 47ms TCP 2ms TLS 14ms TTFB 703ms

What Quicknode does

Quicknode is blockchain infrastructure for developers, not a wallet or an exchange. Developers call a Quicknode endpoint instead of running their own nodes for Ethereum, Solana, Base, Bitcoin and dozens of other networks. Beyond JSON-RPC and WebSocket access it sells Streams, Webhooks, token and NFT APIs, a SQL API and trade execution tools, all managed from one dashboard.

What an outage looks like

Most incidents hit one network, not everything: one chain returns bursts of 503 errors, slows down or sits at a stalled block height while other chains answer normally. Regional incidents show as latency and timeouts in one location such as JFK. Some errors are not outages: 429 is a rate limit, 401 a failed token, IP allowlist or JWT check, 403 a disabled endpoint.

What to do about it

Find your chain and network on status.quicknode.com, which lists each mainnet and testnet separately plus a Quicknode Products group for Streams, Webhooks, the dashboard and support; @QNStatus on X posts updates too. For 429s, add backoff before retrying, since a JSON-RPC batch counts every call inside it. Quicknode's own error reference says to open a support ticket for persistent 500 or 503 errors.

Is it down for everyone, or just you?

If this page says Quicknode is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

C
Coinbase
O
OpenSea
AWS
AWS
Cloudflare
Cloudflare

Quicknode outage FAQ

Is Quicknode down for everyone or just me?
Check the row for your exact chain and network on status.quicknode.com, since most incidents are scoped to one network or one region. If that row is green, look at the status code: 401 points at token auth, an IP allowlist or a JWT, 403 at a disabled endpoint, which Quicknode says can follow a past-due payment, and 429 at your plan's rate limits.
Why am I getting 429 Too Many Requests from Quicknode?
A 429 means you hit one of several limits, not that Quicknode is down. Quicknode's knowledge base lists requests per second, method-specific limits, concurrent connections and add-on limits. A JSON-RPC batch is counted by the number of calls inside it, so batching does not help. Add backoff before retrying and check the endpoint's Metrics page in the dashboard.
Do Quicknode Streams lose data during an outage?
No, a failing destination pauses the stream instead of skipping blocks. Streams processes blocks in order and waits for a 2xx response before moving on. By default it retries every second and pauses after 3 failed retries, and Quicknode says deliveries resume once the destination is fixed and the stream reactivates. The Streams FAQ describes delivery as exactly-once, in finality order.
Is it a Quicknode outage or a problem with the blockchain itself?
Check the incident wording on status.quicknode.com, because many posted incidents are about a single network rather than Quicknode's platform. Titles such as Cosmos Mainnet Network Stalled at Block or Solana Testnet Network Stalled appear alongside region-wide ones such as higher latency in the JFK region. Scheduled node upgrades for specific chains are also posted there as maintenance windows.
How long do Quicknode outages usually last?
Anywhere from minutes to days, depending on the cause. In September 2026 a Solana Mainnet degradation lasted about an hour, Base Mainnet degraded performance about three hours, and higher latency in the JFK region about ten hours. Network stalls ran longer: one Cosmos Mainnet stall stayed open for about two days. Each incident's timeline is on status.quicknode.com.

How we measure this

  • We request Quicknode's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Quicknode publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Quicknode goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required