Why does my swap keep failing even though the pair exists

05 September 2026

The pair exists, but your swap fails because the liquidity pool for that pair has insufficient depth to handle your order at the current price. A trading pair can exist with only a few dollars in it. When you try to swap a meaningful amount, the slippage exceeds what the exchange or your wallet allows, and the transaction reverts.

This is the most common reason for a failed swap in low-liquidity tokens. The pair is real. It is listed. It has a price. But the pool holds so little value that a single swap of any size moves the price dramatically. If your slippage tolerance is set to, say, 1% or 2%, and the swap would require a 10% price impact, the exchange rejects the transaction.

How price impact works in a thin pool. Imagine a pool with 100 tokens A and 100 tokens B. The price is 1:1. If you want to buy 10 tokens A, you must put in roughly 11 tokens B. That is a 10% price impact. If the pool is 1000 of each, buying 10 tokens A costs about 10.1 tokens B - a 1% impact. The smaller the pool relative to your swap size, the larger the impact. Most exchanges cap automatic slippage at 0.5% to 5%. If your swap would exceed that, it fails.

Other reasons for failure, even when the pair exists. The token may have a transfer fee, a tax, or a max-wallet limit that your swap violates. Some tokens pause trading during certain conditions. The router may not find a route that respects the fee structure. The transaction may be frontrun or sandwitched, causing the price to move before your swap executes. Network congestion or a gas price that is too low can also cause a revert.

What you can do. Check the pool's liquidity on a block explorer. Look at the reserves. If they are tiny, your swap will fail unless you set a very high slippage tolerance - which risks being eaten by a sandwich attack. You can split your swap into smaller chunks. Each chunk has less impact. You can also try swapping into a more liquid intermediate asset first, then into your target. The hub page "Swapping in and out of memecoins" covers the full process of moving between thin tokens and spendable assets. That is the next page to read if this problem persists.

A note on the router. The exchanger uses a routing algorithm that tries to find the cheapest path. It may attempt a direct swap on the pair you see, but if that direct swap fails, it may try a multi-hop route through a more liquid token. That route might succeed where the direct one fails. The page "What does it mean when a swap route uses multiple hops" explains how that works. If you are seeing repeated failures, the router may be unable to find any viable path given your slippage setting.

The honest short answer. The pair exists. The liquidity does not. Your swap size is too large for that pool. Reduce your swap size, increase your slippage tolerance cautiously, or use a different route. If none of that works, the token may be untradeable at your intended volume.

Back to ledger