If you are making your first cross-chain swap, route failure metrics help you judge how often a route finishes as planned. They are clues, not guarantees: a low failure rate can hide slow payouts or costly retries. Check what each metric counts before comparing routes.
What does a route failure rate tell you?
A route failure rate is the share of started transfers that did not reach the expected result. A route is the full path your assets take, including any bridge transfer and swap between networks. For example, if 8 of 100 started transfers fail, the rate is 8%.
That number only helps when you know the denominator: what counts as a started transfer. Some reports may count only transfers that reached the source network; others may include quotes that never became transactions. Ask whether the data includes pending transfers, user cancellations, or only confirmed failures.
- Completion rate: The share that reached the destination. Check that “complete” means the expected asset arrived, not merely that the first transaction was accepted.
- Failure rate: The share that stopped or reverted. A reverted transaction is rejected, though its sender may still pay a network fee.
- Time to completion: How long transfers take, often shown as a median or an average. A median is the middle result; a few very slow transfers can pull up an average.
- Recovery rate: The share of failed transfers that later finished or returned funds. Check how long recovery took and whether the original amount was restored.
How do these numbers expose execution risk?
Execution risk is the chance that a route will not finish as expected, or will take extra time or cost. A cross-chain route can depend on several steps: the source transaction, a bridge message, and the destination transaction. If one step stalls or fails, the rest may wait.
Compare two routes for the same transfer. Route A completes 98% of transfers in a few minutes, while Route B completes 99% but often takes hours. If timing matters, A may suit you better; if waiting is acceptable, B’s extra completion may matter. These figures are examples, not current service statistics.
Look for the time window and sample size behind each figure. A 99% completion rate across 20 transfers is weak evidence; the same rate across 10,000 transfers is more informative, though past results still cannot promise yours. Chainlink CCIP’s documentation describes how a rate limit can cause a send-time rejection or a destination execution failure that can be retried. That illustrates why “failed” may mean delayed recovery, not lost funds.
For a first transfer, quickswap is a cross-chain bridge and swap service that moves assets between networks and exchanges them in one flow. The same route-level checks are useful when considering how quickswap handles treasury transfers, because the underlying question is still whether the full transfer completes and when.
What should you check before sending?
Use these steps to compare the available route information before you commit funds:
- Confirm that the source and destination assets and networks match your plan.
- Check whether the completion figure counts transfers that are still pending.
- Compare the time window, number of transfers, and median completion time.
- Find out what happens after a failure: retry, refund, or manual recovery.
- Decide whether the likely wait and possible extra network fees suit your transfer.
Ethereum.org explains that a transaction can fail while still using gas, the fee paid for network computation. So even when the asset swap does not finish, the source transaction may cost something. Before acting, ask yourself: could I accept this route’s likely delay and the fee if one step fails?
Does a high completion rate mean a route is safe?
No. It measures past completion under a particular definition and time window. It does not prove that a route is secure, that every asset will arrive quickly, or that a future transfer will succeed. Use it alongside recovery information and the route’s stated steps.
What should I do if a transfer is still pending?
First, check the transaction status on the source network and see whether the destination step has started. A pending transfer may be waiting for confirmations or retrying execution. Avoid starting a duplicate transfer until you understand the original status; otherwise, you could send the funds twice.
Top comments (0)