"No route found": why Lightning pathfinding fails and how to fix it
Last updated:
"No route found" is one of the most common Lightning payment errors. Depending on the software it appears as no_route or FAILURE_REASON_NO_ROUTE in LND, "Ran out of routes to try" or "Could not find a route" in Core Lightning, and "Failed to find a path to the given destination" in LDK-based wallets. Many mobile wallets simply show "route not found" or "payment failed".
The common thread: your node (or your wallet's routing provider) could not build or complete a path from you to the recipient that satisfied every constraint at the moment you paid. It does not mean the recipient is offline, and it does not mean your funds are at risk. It means no acceptable path was found, or every candidate path was tried and failed.
Live Lightning routing signal
This is a historical ranking proxy built from observed route candidates over the last 24 hours. It is not a payment success probability and does not measure directional liquidity for your specific path.
Check current routing reliability on the dashboard →How Lightning pathfinding works, briefly
Lightning uses source routing. The sender's node looks at its local copy of the public channel graph, learned through gossip, and searches for a path to the destination. Each candidate path has to satisfy several constraints at once:
- Every channel on the path must be able to carry the amount, including fees added by later hops, in the right direction.
- The total routing fee must stay under the sender's fee limit.
- The total time-lock (CLTV delta) must stay under the sender's maximum.
- The amount must fall within each channel's minimum and maximum HTLC size.
Public gossip shows channel capacity but not how that capacity is split between the two sides. Senders therefore guess, try a path, learn from the failure, and try again. "No route" is what you see when the search runs out of candidates.
Common causes
- The recipient has no inbound liquidity. If the recipient's channels are mostly on their own side, there is no capacity flowing toward them. This is very common with new nodes and self-custodial wallets that have only just opened a channel.
- The amount is too large for the available paths. A payment that is small enough succeeds while a larger one fails. Large payments need either big, well-balanced channels or multi-path payments (MPP).
- Your fee limit is too low. Paths may exist, but every path costs more than your configured maximum fee, so pathfinding rejects them all.
- Private or unannounced channels without route hints. If the recipient is reachable only through private channels and the invoice carries no route hints (or blinded paths), the sender cannot see a way in.
- A stale or incomplete graph. A node that has just started, or whose gossip sync is behind, may not know about channels that would work.
- Mission control has penalized the paths. After recent failures, LND and other implementations temporarily avoid channels that failed. Retrying immediately after several failures can return "no route" sooner.
- Your own channels are offline or depleted. If your peers are disconnected or your outbound balance is low, the search fails before it leaves your node.
Fixes for senders and wallet users
- Try a smaller amount. If a smaller payment succeeds, liquidity along the path is the constraint. Split the payment, or use a wallet that supports MPP.
- Raise the fee limit slightly. In LND,
lncli payinvoice --fee_limitor--fee_limit_percent. In Core Lightning, adjustmaxfeepercentormaxfeeonpay. Keep the limit reasonable. Raising it only helps when fee was the blocker. - Wait and retry. Liquidity moves constantly, and penalties from recent failures decay. A retry a few minutes later often succeeds.
- Ask the recipient to check their inbound capacity or to send a fresh invoice with route hints if they use private channels.
- Check your own node: confirm your channels are active and your outbound balance covers the amount plus fees.
Fixes for node operators and developers
- Get inbound liquidity before you need to receive. Options include buying a channel from a Lightning Service Provider, using liquidity marketplaces, or doing a submarine swap (loop out) to shift balance to the remote side.
- Connect to well-connected, consistently active peers. Fewer, better channels to reliable routing nodes usually beat many tiny channels.
- Enable MPP and allow enough parts, for example LND's
--max_parts, so large payments can be split across channels. - Include route hints or blinded paths on invoices if your channels are private.
- Log the failure reason and amount for every failed payment, so you can tell a fee-limit problem from a liquidity problem.
- Watch route stability over time. If your preferred routing candidates keep changing, "no route" errors tend to cluster. A historical view such as the Optaimaze insights dashboard shows whether leadership among top-ranked candidates is stable or shifting.
"No route" vs. other failures
"No route" is a sender-side conclusion: the search ended without success. It differs from errors returned by a specific hop on the path, such as temporary_channel_failure, covered in insufficient balance and liquidity, and from final-hop rejections like incorrect_or_unknown_payment_details, covered in invoice expired. Often a "no route" result is the end state after several hop-level failures. Your node's detailed payment log (for example lncli trackpayment or listpays/paystatus) shows which.
Lightning payment error guides
"No route found" FAQ
What does "no route found" mean on Lightning?
It means the sender could not find, or ran out of, paths to the recipient that satisfied the amount, fee limit, time-lock limit, and channel constraints at the time of payment. Your funds are not lost. The payment simply did not complete.
Why does a smaller Lightning payment work when a larger one fails with no route?
Channel liquidity is limited and directional. Small payments fit through more channels. Larger payments need bigger, well-balanced channels or multi-path payments that split the amount across several routes.
Can a low fee limit cause "no route found"?
Yes. If every available path costs more than your maximum routing fee, pathfinding rejects them all and reports no route. Raising the fee limit modestly can help, but only when fee was the constraint.
How do I receive Lightning payments without "no route" errors?
Make sure you have inbound liquidity, meaning capacity on the remote side of your channels. You can buy a channel from a Lightning Service Provider, use a liquidity marketplace, or swap funds out. If your channels are private, include route hints or blinded paths in your invoices.
Does the Optaimaze reliability score predict whether my payment will find a route?
No. The Optaimaze signal is a historical ranking proxy based on observed route candidates. It is not a payment success probability and does not measure directional liquidity on your specific path.
Check current routing reliability.
See current top-ranked route candidates, leadership changes, volatility, and risk level from recent snapshots.