Axiom Trade Not Working? How to Fix Failed Transactions and Slippage

Most Axiom problems fall into a handful of repeatable categories, and almost none of them require contacting support. Here's what actually causes each one and the fastest real fix.

Failed Transactions and Slippage

This is the number one reported issue, and it's almost always slippage rather than a platform bug. A thin, freshly-launched pool can move a long way between when you click buy and when the transaction lands. Set your slippage tolerance below that movement and the trade fails rather than executing at a worse price.

The ranges people work with are heuristics rather than measurements, and we have not tested them: roughly 10 to 20% or more on a thin new launch, roughly 1 to 3% on an established token like SOL, JUP or BONK. The underlying variable is your position size against the pool's depth, so treat those as reasoning rather than settings to copy. Best Axiom Trade settings works through what each value does.

The tradeoff: higher slippage means fewer failed transactions, but it also means a worse guaranteed fill and more exposure to price movement during confirmation. There's no single right number, so match it to what you're actually trading.

The Limit Order Cap

If you get an error placing a new limit order, the most likely cause is Axiom's cap on active limit orders, since you can only have so many open simultaneously. Check your open orders and cancel a stale one before placing a new one.

Perps Withdrawal Delays

Axiom's perpetuals route to Hyperliquid, and withdrawals settle through Hyperliquid's own bridge. That means the timing belongs to Hyperliquid's infrastructure rather than to Axiom, even though the withdrawal starts inside the Axiom interface.

Neither company publishes a guaranteed arrival time that we have found, and we have not measured one, so we are not going to quote you a number. What is useful in practice: if a perps withdrawal is slow, check Hyperliquid's own status channels and its bridge before concluding Axiom has a bug, because a delay there will look identical from inside Axiom.

The August 2025 Sell Outage: What to Learn From It

In late August 2025, selling through Axiom broke for several hours. Axiom's own Discord attributed it to Pump.fun's API, posting: "Pump Fun has pushed a breaking change without notifying trading bots," and telling users who needed to sell that they could only do so directly on Pump.fun's site during the outage.

That is Axiom's account of what happened. We have not seen Pump.fun's account of the same event, and what either company did or did not tell the other is not something we can verify, so treat the attribution as Axiom's statement rather than as an established fact.

The lesson generalizes past this one incident: export your seed phrase into Phantom, Rabby, or Solflare before you need it, covered in our getting-started guide. A trading terminal outage doesn't lock your funds if you hold your own keys and can fall back to trading directly on the underlying AMM.

Fee Confusion

Axiom isn't hiding fees, but the layered cost on a fresh launch surprises people who only budgeted for Axiom's own 1%. You're also paying whatever the underlying AMM charges, plus network gas and your priority fee or Jito tip. That AMM fee is not Axiom's and is not quoted in Axiom's interface: Pump.fun's Dynamic Fees schedule for PumpSwap is tiered by market cap, running from roughly 1.25% at the smallest tier down to about 0.30% at the largest, as published on Pump.fun's own fee docs, read August 2026. Check there for current figures, and see the full fee breakdown for the real all-in number before you size a small trade and wonder where the balance went.

Wallet Connection Issues

If Phantom or another wallet won't connect, the standard fixes apply before assuming an Axiom-side problem: refresh the page, make sure your wallet extension is unlocked and updated, and check you're on the genuine axiom.trade domain rather than a lookalike. auth-axiom.trade appeared on the MetaMask, ScamSniffer and SEAL phishing blocklists when we checked on 6 August 2026. See our security guide for the full list of domains observed impersonating Axiom.

Contacting Support

Axiom support operates through Discord tickets only, via its official server. Axiom's documentation lists no official Telegram bot, so a bot presenting itself as Axiom support is not something Axiom publishes, and the same goes for anything presenting itself as an Axiom app in an app store. Axiom's own support guidance is explicit that legitimate support will never message you first, so treat any unsolicited DM offering to help as a phishing attempt.

Is Axiom Down Right Now?

When a transaction looks stuck, check the chain before you blame the app. Solscan will tell you whether your transaction actually landed, failed, or never broadcast, which is the difference between an Axiom bug and a Solana congestion event:

Source: Solscan, used under fair use for educational purposes

We have not found a public Axiom status page as of August 2026. Check Axiom's official X account and Discord for outage announcements, and consider whether the issue might be Solana-wide congestion rather than Axiom-specific, since the two can look identical from inside the app but require different fixes.