No Available Router GMGN Error (2026): Causes and Fixes

The no available router GMGN error means exactly what it says: when you hit Buy or Sell, GMGN's router looked for a liquidity pool to route your swap through and found none. The raw strings behind the message are trade_error_40002700 in the manual trade panel and order10013 on automated orders. Nothing was submitted on-chain, so you have not lost gas or paid the 1% fee.

According to GMGN's documentation (docs.gmgn.ai), there are three mechanical reasons this happens: the pool was removed, the token is mid-migration between a bonding curve and a DEX pool, or the RPC endpoint GMGN is using cannot see the pool because of congestion or an outage. Which one you are hitting decides the fix, and the fix order matters because two of the three resolve themselves if you simply wait.

This is an independent guide; GMGN AI App Guide is not affiliated with GMGN. Below is the exact meaning of each string, how to tell the three causes apart, how to confirm the pool on Solscan, and which related codes actually cost you money.

What does "No Available Router" mean on GMGN?

A router is the piece of GMGN's trade engine that decides which pool (or sequence of pools) will execute your swap. On Solana that can be a Pump.fun bonding curve, a Raydium pool, or another DEX pool; on EVM chains it is the equivalent AMM pool. The GMGN router needs at least one pool with live liquidity for the token pair you selected. If it cannot find one, it refuses to build the transaction and shows "No Available Router."

Some traders read this as "gmgn no available route" or "no available routes gmgn" and search for those phrases; they are all the same condition. The key point is that it is a pre-flight failure, not a failed on-chain transaction.

The exact error strings you will see

If your trade history shows a different code, you are not looking at a routing problem. Jump to the related-codes table further down to identify what actually happened.

Why does GMGN show no available router? Three mechanical causes

GMGN's docs list three causes. Each one leaves a different trace on-chain, which is how you tell them apart.

Cause 1: The pool no longer exists

The most common reason on fresh memecoins. The deployer or liquidity provider pulled liquidity, so the pool that existed a minute ago is empty or closed. GMGN also has a dedicated code for a pull that happens while your transaction is in flight, D1 (0x28, liquidity pulled), but if the pool is already gone when you click, you get the router error instead. Nothing will fix this; there is no route because there is nothing to trade against.

Cause 2: The token is mid-migration

When a Pump.fun or other launchpad token fills its bonding curve, the launchpad moves liquidity to a DEX pool. During that window the bonding-curve pool is closed and the new pool has not been indexed yet. GMGN's Trenches columns label these tokens "Almost Bonded" and then "Migrated" for a reason. The router sees no route for anywhere from seconds to a few minutes. The related code is D2 (0x1775, "Liquidity has migrated to Raydium") if the migration completes while your order is processing.

Cause 3: RPC or network congestion

The router asks an RPC node for pool state. If the default endpoint is overloaded or partially down, it can return stale or empty data, and GMGN concludes there is no route even though the pool is fine. GMGN's D3 code (congestion) and A3 (anti-MEV RPC fail) are the neighbors of this condition. The tell-tale sign is that the error hits several unrelated tokens at once.

How to fix the no available router GMGN error (in this order)

Work through these steps in sequence. Steps 1 and 2 cover the two causes that fix themselves; step 4 is the one lever you control.

1. Check the token's stage in Trenches. If it sits in "Almost Bonded" or has just moved to "Migrated," you are in a migration window. Wait 1–3 minutes and retry. Do not change any settings yet.
2. Verify the pool on Solscan (details in the next section). If liquidity was removed, stop. No setting will create a route.
3. Retry once. A single retry rules out a transient indexing hiccup. Repeated instant retries do nothing useful because the router will hit the same stale state.
4. Switch RPC. If the pool is alive on Solscan and the error persists, or if it is hitting multiple tokens, point GMGN's custom RPC setting at a different endpoint and retry.
5. Raise slippage only if a route exists. GMGN recommends Auto slippage for manual trades, 30–35% for automated orders, and 50%+ for brand-new tokens. Slippage matters for the C1 revert path, not for a missing route, so this step is last and conditional.
6. If it still fails, note the exact string, the token, and the time, and open a ticket through GMGN support with your UID.

If you are seeing other errors alongside this one, the broader GMGN not working checklist covers outages, Cloudflare challenges, and RPC symptoms.

How to confirm the pool status on Solscan

Solscan is the quickest way to separate cause 1 from causes 2 and 3 without trusting any terminal's indexer.

1. Copy the token's contract address from GMGN's token page.
2. Paste it into the Solscan search bar and open the token page.
3. Look for an active market or pool listing for the token. If no pool is listed, or the listed pool shows near-zero liquidity, the pool was removed or never existed on a DEX.
4. Open the most recent transactions. A liquidity-removal or migration-related instruction in the last few minutes confirms cause 1 or cause 2 respectively.
5. If the pool shows healthy liquidity and recent swaps from other wallets are landing, the pool is fine and your problem is RPC-side (cause 3). Switch RPC.

Do this check before touching slippage or priority fees. A route that does not exist on Solscan will not exist on GMGN either, no matter what you set.

How does no available router relate to other GMGN error codes?

GMGN groups sniper and trade failure codes into families. The letter tells you where in the pipeline the failure happened and, crucially, whether it cost anything.

"No Available Router" sits with the B-family and order-validation failures: it is a submission failure and, per GMGN's docs, submission failures cost nothing. Only execution failures like C1 burn gas and priority fee. The full breakdown of what a trade actually costs is in the GMGN fees guide.

When should you set a custom RPC on GMGN?

GMGN lets you paste a custom RPC endpoint in its trading settings. Use it when:

• the router error hits several tokens at the same time,
• Solscan shows a healthy pool but GMGN still finds no route,
• charts or balances are updating late, which suggests the default endpoint is lagging,
• you are trading during a congestion event and GMGN is returning D3 codes.

A paid or private RPC from any established Solana provider will usually see pool state faster than a public endpoint. If you use Anti-MEV mode, remember GMGN's minimums still apply: 0.002 SOL priority fee plus 0.0001 SOL tip. Switching RPC does not change the 1% GMGN fee or the priority fee you set. If you trade on more than one chain, check the GMGN chains guide because the endpoint you paste must match the chain you are trading.

Does a no available router error cost money?

No. This is the one piece of good news in the whole error. GMGN's documentation states that submission failures cost nothing because the transaction never left GMGN's servers. There is no gas, no priority fee, no tip, and no 1% platform fee.

Compare that with a C1 slippage revert, where the transaction landed on Solana, failed, and still consumed gas and priority fee. If you set a 0.006 SOL priority fee and hit three C1 reverts on a 0.1 SOL buy, you have burned 0.018 SOL on nothing, which is 18% of your intended position. That is why "transaction failed gmgn" searches are so frustrating: the label is the same but the cost is not. Always check the code.

One caveat: GMGN's PnL display does not reliably deduct priority fees and tips. Trust your wallet balance change, not the PnL card, when tallying what failed trades cost you. The GMGN PnL guide explains what the display does and does not include.

Does this happen with copy trades and limit orders too?

Yes, and it is more common there than in manual trading, because automated orders fire at the exact moments pools are most likely to be in flux.

• Copy trading: if the wallet you follow buys on the bonding curve seconds before migration, your copy order can hit order10013. GMGN copy tasks auto-pause after three consecutive failures, so a run of router errors during a busy migration window can silently stop your task. Check the task status in GMGN copy trading and resume it.
• Limit and TP/SL orders: an order that triggers while liquidity is being migrated returns order10013 instead of executing. GMGN's auto-created TP/SL orders are valid for 24 hours, so a single failed trigger does not usually cancel the order, but you should verify it is still active. See GMGN limit orders and stop-loss.
• Sniper buys: the sniper is designed for the first blocks of a launch, when the only pool is the bonding curve. If the launchpad has not created the curve yet, the router has nothing to route through.

For automated orders GMGN recommends a 0.006 SOL or higher on-chain fee and 30–35% slippage, but again, those settings help only when a route exists.

Key takeaways

• "No Available Router" (trade_error_40002700 manual, order10013 automated) means the GMGN router found no liquidity pool for your swap.
• Three causes: pool removed, token mid-migration, or RPC/congestion. Two of them resolve by waiting; only the RPC case responds to a settings change.
• It costs nothing. Submission failures never reach the chain. Execution failures like C1 do burn gas and priority fee.
• Fix order: check Trenches stage, verify pool on Solscan, retry once, switch custom RPC, raise slippage only if a route exists.
• Copy tasks auto-pause after three consecutive failures, so a burst of router errors can stop your task without a loud alert.

If you are still seeing the no available router GMGN error after confirming a live pool and switching RPC, it is time for a support ticket with the exact string, token, chain, and timestamp. Start from the GMGN AI app hub for the login, fee, and automation guides, and Open GMGN when you are ready to retry.

Sources: GMGN documentation, DefiLlama, official app store listings and GMGN's public channels. See our methodology. Last reviewed 2026-09-22.