Sometimes a swap is delayed by the network itself: a planned upgrade, a halt in block production or provider node maintenance.
How to recognise it
The transaction does not appear, confirmations stop growing, or the order does not see a confirmed deposit — while other services also delay that coin. Check whether the explorer's latest block number is moving and read the network status page, such as status.solana.com.
What to do
- Do not resend: a broadcast transaction will be processed once the network recovers.
- If a confirmed deposit is not credited for longer than usual, contact support with the order number, hash, network and amount.
- If the order expired during the outage, do not pay the same address again.
Avoiding it
Check status pages and exchange announcements before large swaps and avoid announced hard-fork windows. For AVAX use the C-Chain (see C-, X- and P-Chain) and create orders on the AVAX → USDT page.
What happens during a halt
During a halt a transaction either waits in node queues or is rejected outright, leaving the coins in your wallet — so first check whether it exists on the explorer. During planned upgrades services pause crediting and resume after nodes sync.
When delayed, check that the transaction is on the explorer, the latest block number is growing, no suspension is announced, and confirmations are still below the required count. If everything is fine and crediting is late, contact support with the order number and hash; if the network is halted, wait without resending.
FAQ
Should I resend during a network halt?
No; a broadcast transaction is processed after recovery and a resend creates a second payment.
How do I know the network is the problem?
See whether new blocks appear in the explorer and check the network status page.