A Jupiter swap can fail because a route is unavailable, liquidity is insufficient, the trade size is unsuitable, the token has restrictions, the quote expired, or the network could not refresh pricing. Jupiter Support says “no routes found” commonly points to liquidity, amount, or token restrictions. Diagnose the cause before trying again.
Start with the Jupiter Exchange guide, and check the fee and price-impact guide before changing slippage.
Read the exact error
Save the message, token mints, amount, route, wallet network, and signature if one exists. “No routes found,” stale routes, rejected signatures, and a transaction that fails on-chain are different states with different next checks.
Check amount and liquidity
A pair may have no usable pool, or the amount may be too large or too small for the available depth. Try a smaller test only after verifying the asset and route. Do not assume a visible price means an executable market.
Check slippage and token behavior
Price movement or shallow liquidity can exceed the allowed tolerance. Increasing tolerance can permit a materially worse fill and may increase sandwich exposure. Transfer hooks, taxes, frozen accounts, and program restrictions can also prevent execution.
Check network and quote freshness
Refresh the page, inspect wallet network and RPC settings, and request a new quote. Jupiter Support notes that route refresh failures can block execution to avoid a stale price. A failed attempt can still consume a fee.
Escalate with evidence
After a small number of well-spaced retries, use official support with the exact error and signature. Never paste a recovery phrase. A support response may explain a product issue, but it cannot reverse an irreversible transfer automatically.
Limits and responsible use
Troubleshooting cannot guarantee execution or recover funds sent to the wrong destination. Token-specific restrictions and market conditions can change without notice. Last reviewed 2026-09-21.