Insufficient balance and liquidity: the most common reason Lightning payments fail
Last updated:
Liquidity errors show up in a few different forms. Your own node might report insufficient_balance (LND's FAILURE_REASON_INSUFFICIENT_BALANCE) or "insufficient local balance". A node partway along the route might return temporary_channel_failure. And when liquidity is the hidden cause behind a failed search, many wallets just say "insufficient liquidity" or "route not found".
They all point to the same fact. Lightning channels hold a fixed amount of bitcoin split between two parties, and a payment can only move through a channel in a direction where enough of that balance sits on the sending side.
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 →Outbound vs. inbound liquidity
Every channel has two sides. Outbound liquidity is the balance on your side, which you can send. Inbound liquidity is the balance on your peer's side, which is how much you can receive. If you open a 1,000,000 sat channel, you start with roughly 1,000,000 sats outbound and close to zero inbound. You can pay right away but cannot receive until some balance moves to the other side.
The same applies at every hop. A route works only if each channel along it has enough balance on the forwarding side for the amount plus the fees added by later hops. Public gossip announces each channel's total capacity, not how it is split, so senders have to discover this by trying.
Where the error comes from
1. Your own channels: "insufficient balance"
Your node checks its own channels first. Even if your wallet balance looks large enough, the spendable amount is lower than the total because:
- Each side must keep a channel reserve, commonly around 1% of channel capacity, that cannot be spent.
- The channel funder pays the on-chain commitment transaction fee and, with anchor channels, keeps a small amount for anchor outputs.
- The amount must also cover routing fees for the whole path.
- Balance may be split across several channels, and without multi-path payments (MPP) a single channel has to carry the whole amount.
2. A channel along the route: temporary_channel_failure
BOLT 4 defines temporary_channel_failure as a forwarding node saying its outgoing channel could not handle this HTLC right now but might later. The usual cause is not enough balance in that direction. It can also mean the channel hit its limit on pending HTLCs or in-flight value, or that the next peer is briefly unavailable. Your node records the failure, avoids that channel for a while, and tries another path.
3. The recipient: no inbound capacity
If the recipient's channels hold almost nothing on the remote side, every path dies at the last hop. Senders usually see this as repeated temporary failures followed by "no route found". It is very common with newly opened nodes and self-custodial wallets.
Fixes for senders
- Check your spendable balance, not your total balance. Most node software reports both, for example
lncli channelbalanceorlistfundsin Core Lightning. - Send less or split the payment. Use MPP if your wallet supports it, or send two smaller payments if the recipient agrees.
- Retry after a short wait. Liquidity shifts constantly as other payments flow through the network.
- If you control both ends, consider opening a direct channel to the recipient or a well-connected peer close to them.
Fixes for receivers and node operators
- Acquire inbound liquidity: buy a channel from a Lightning Service Provider, use a liquidity marketplace, ask a peer to open a channel to you, or do a submarine swap (loop out) that moves your balance on-chain and frees inbound capacity.
- Rebalance depleted channels with circular payments or swaps when the cost makes sense. Rebalancing that costs more than it earns is a common trap.
- Set fees that reflect scarcity. Channels that drain in one direction can carry higher fees in that direction to slow the outflow.
- Raise HTLC limits carefully if you route heavy traffic, and monitor pending HTLC counts.
- Track failures by channel and direction so you can see which peers keep returning
temporary_channel_failure.
Watching liquidity risk over time
Individual balances are private, so nobody outside a channel can see them directly. What you can watch is behavior over time: whether the same routing candidates keep ranking well, how often leadership changes, and how volatile scores are. The Optaimaze dashboard summarizes those historical signals. Treat them as context for your own node's payment logs, not as a liquidity measurement.
Lightning payment error guides
Insufficient balance and liquidity FAQ
Why does my Lightning wallet say insufficient balance when I have enough funds?
Spendable Lightning balance is lower than your total. Channel reserves (often around 1% of capacity), commitment transaction fees, anchor reserves, and routing fees all reduce it, and without multi-path payments one channel may need to carry the whole amount.
What is temporary_channel_failure on Lightning?
It is a BOLT 4 error a forwarding node returns when its outgoing channel cannot handle the payment right now. The most common cause is not enough balance in that direction, but HTLC count or in-flight value limits and short peer outages can also trigger it. The sender usually tries another path automatically.
Why can I send but not receive Lightning payments?
You probably have outbound liquidity but little inbound liquidity. A channel you open starts with the balance on your side. To receive, you need capacity on the remote side, from an inbound channel, a Lightning Service Provider, a liquidity marketplace, or a swap.
How do I fix insufficient liquidity errors as a node operator?
Add inbound capacity, rebalance channels that drain in one direction when the cost is justified, set directional fees that reflect scarcity, and log failures by channel so you can see which peers repeatedly fail to forward.
Can Optaimaze show me channel balances?
No. Channel balances are private. Optaimaze publishes historical ranking signals about observed route candidates, which give context about routing stability but do not measure the liquidity of any specific channel or path.
Check current routing reliability.
See current top-ranked route candidates, leadership changes, volatility, and risk level from recent snapshots.