Routewell

Solana RPC failover

One RPC address. Always the healthiest provider.

KEY 1clear KEY 2clear KEY 3clear
Sending to key 1, all signals clear Tap a signal to slow it or hold it

Paste your free-tier keys from Helius, QuickNode, Alchemy and the rest once. Routewell sends each request to whichever is fastest right now, and moves to the next when one slows down or hits its limit.

Create your endpoint Live provider status
  • Free for hobby use
  • Keys encrypted at rest
  • Any Solana client

How it works

Swap one URL. Keep your own keys.

Routewell doesn't resell RPC. It sits in front of the providers you already use and decides, call by call, which one gets the request.

app.ts
// ROUTEWELL_RPC_URL is the address shown in your console
import { Connection } from "@solana/web3.js";

const connection = new Connection(process.env.ROUTEWELL_RPC_URL, "confirmed");
  1. 01

    At the signals

    Paste your provider URLs

    Add the RPC URLs from your provider dashboards. Each one is checked against Solana's genesis hash before it's saved, then stored encrypted.

  2. 02

    At the switch

    Choose how to route

    Fastest sends each call to the best-measured provider. In order follows your list top to bottom. Both skip anything slow, failing or rate-limited.

  3. 03

    In your app

    Point your app at Routewell

    Replace your RPC URL with your Routewell address. Single calls and batches pass through unchanged, with CORS for browser apps.

Signal aspects

What moves traffic off a provider

Every call is measured. A provider that misbehaves sits out a short cooldown and the call is retried on the next one, up to four providers deep.

  • Clear

    Answers quickly with a valid response. Providers are ranked by latency measured over the last five minutes.

    Ranked by speed

  • Slow

    No answer within 6 seconds: the call moves to the next provider, and the slow one drops down the ranking until it recovers.

    Drops in the ranking

  • Rate-limited

    HTTP 429 or a rate-limit error in the response. The provider sits out its Retry-After time, 15 seconds by default.

    Sits out 15 s

  • Failing

    5xx, a refused key, or a node that reports it is behind (-32005). Sits out 2 seconds, doubling while it keeps failing. Bad requests come back as they are.

    Sits out 2 s, doubling

Measured in the open

Real numbers, per provider

Routewell probes the public endpoints every 30 seconds and folds in the outcome of every routed call. The status board shows latency, success rate and rate limits for the last 24 hours.

Last 24 hours

Open the status board

Loading measurements…

Plans

Free for side projects

Hobby

Free

  • 100,000 calls a day per endpoint
  • Up to 25 calls a second
  • Up to 8 provider URLs, any mix
  • Failover, cooldowns and per-key stats
Create your endpoint

Team

Monthly

  • Higher daily volume and rate
  • Alerts when a provider on your endpoint degrades
  • Several endpoints under one team

Questions

Before you swap the URL

Can Routewell see my keys?

Your provider URLs are stored encrypted (AES-256-GCM) and only decrypted in memory to forward your calls. The console shows the host and the last four characters, never the full URL. Request bodies aren't stored.

Is it safe to retry sendTransaction on another provider?

Yes. A signed transaction carries its own signature and Solana processes it at most once, so sending it through a second provider can't make it land twice.

Do websockets and subscriptions work?

Not yet. Routewell handles HTTP JSON-RPC: single calls and batches of up to 100. Keep your provider's websocket URL for subscriptions.

Do I need an account?

No sign-up. Creating an endpoint gives you a manage key. Keep it somewhere safe: it's the only way to change or delete the endpoint.

Mainnet or devnet?

Both. Each endpoint serves one network, and provider URLs for the other network are refused when you add them.