About these signals: Optaimaze currently measures historical candidate rankings, not payment success probability or independent node reliability. Read methodology and coverage →
Lightning payment failures

Why Lightning payments fail, and how to see the risk earlier.

Last updated:

Lightning payments can fail for reasons that are not always obvious from the outside. A route may look available, but liquidity, node behavior, route volatility, shifting network conditions, or a weakening trust signal can still prevent a payment from completing.

Live data

Current Lightning routing signal

Reliability signal100/100
SignalStrong historical signal
Risk levelLow
Top-ranked nodeACINQ
Last snapshotNov 22, 2026 20:56 UTC

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 →
Error guides

Troubleshoot a specific error message

Common causes

Lightning failures are usually reliability problems, not fee problems.

Low routing fees do not guarantee that a payment path is dependable. Payment success depends on liquidity, routing stability, and the quality of the path available at the time of payment.

01

Insufficient liquidity

A route may exist, but the available channel liquidity may not support the payment amount.

02

Unstable route conditions

Route leadership can shift as network conditions change, making yesterday’s best path less reliable today.

03

Weak node reliability

Nodes with weaker connectivity, low trust, or inconsistent leadership can introduce risk into the payment path.

04

Missed warning signals

Frequent score changes, route winner changes, or risk-level shifts can matter before a user reports a failed payment.

How to think about failures

A failed payment is often a signal problem.

Lightning payments do not fail randomly. Failures often point to unstable route conditions, liquidity limitations, weaker network paths, or ranking consistency changes. Optaimaze focuses on reading those signals before they become payment problems.

The Optaimaze insights dashboard tracks current recommendations, payment reliability, Ranking Consistency Scores, alert status, stability score, risk level, winner changes, volatility, and leadership distribution from collected route snapshots.

Route confidence

Know whether the recommendation looks dependable

Optaimaze evaluates whether the current route candidate is supported by recent history and confidence signals.

Volatility tracking

Watch for shifting route leadership

Winner changes and score movement help reveal when routing conditions are still unstable.

Reliability alerts

Focus on change, not only current score

The core question is whether Lightning payments are likely to work consistently enough for real usage, and whether the signal changed enough to notify a team.

FAQ

Lightning payment error FAQ

What does "no route found" mean when a Lightning payment fails?

Your node, or your wallet's routing service, could not find a path to the recipient that met the amount, fee limit, time-lock limit, and channel constraints at that moment, or it tried every candidate path and they all failed. No funds are lost. Common fixes are trying a smaller amount, using multi-path payments, raising the fee limit modestly, waiting and retrying, or asking the recipient whether they have inbound liquidity.

Why do I get "insufficient balance" or "insufficient liquidity" errors?

"Insufficient balance" usually means your own channels cannot cover the amount plus fees after channel reserves and commitment fees are set aside. "Insufficient liquidity" usually means a channel along the route, or the recipient's inbound side, does not have enough balance in the needed direction. Channel liquidity is directional and private, so senders discover it by trying routes.

What should I do when a Lightning payment times out?

Check whether any attempt is still in flight before retrying. If nothing is pending, the payment failed and you can retry the same invoice. If an HTLC is still pending, wait for it to settle or fail, and do not pay a new invoice for the same purchase, or you may pay twice.

Why does my Lightning invoice say expired?

Each BOLT 11 invoice has an expiry set by the recipient, one hour by default if unspecified and often 10 to 15 minutes at exchanges and merchants. After it passes, wallets refuse to pay and the recipient rejects late payments. Request a fresh invoice and check that your device clock is correct.

What does fee_insufficient mean?

A forwarding node returns fee_insufficient when the payment offered less than its current routing fee. This usually happens because the sender's view of the channel's fee policy is out of date. The error includes the updated policy, and most node software applies it and retries automatically. It is different from your own fee limit being too low, which typically shows up as no route found.

What is temporary_channel_failure?

It is a BOLT 4 error from a forwarding node whose outgoing channel cannot handle the payment right now. The most common cause is insufficient balance in that direction, but HTLC count or in-flight value limits and short peer outages can also trigger it. The sender records the failure and tries a different path.

What does incorrect_or_unknown_payment_details mean?

It is a permanent error from the recipient's node. It covers an unknown payment hash, an invoice that is expired, canceled, or already paid, a wrong amount, a mismatched payment secret, or a final time-lock that is too short. Because the payment reached the recipient, routing was not the problem. Usually the fix is a fresh, correct invoice.

Live reliability signal

See whether current Lightning route recommendations are stable.

View route status, payment reliability, Ranking Consistency Scores, alert status, risk level, confidence trend, and recent route history.