How Long Does an Across Bridge Transfer Take?

An acrossbridge transfer through Across usually delivers funds to the destination chain in about two seconds after the deposit is detected, though the route estimate and the transfer’s status matter. The process has three stages: you submit a deposit, a relayer fills it on the destination chain, and the protocol settles the relayer’s repayment later. That last step can take much longer, but you generally do not need to wait for it to receive your funds.

How long does an Across transfer usually take?

Across says most transfers fill in about two seconds on supported mainnet routes. That is the time for the relayer to deliver the destination funds, not a promise that every step from wallet confirmation onward will fit inside two seconds. Your wallet must submit the source transaction, and the source chain must record it before a relayer can act. The time for those steps depends on the chain and its conditions.

Before confirming, check the route’s quoted expected fill time if the interface provides one. The estimate is route-specific, so it gives a better guide than a single headline speed. For a fuller explanation of Across transfer types and how they differ, see the separate guide; the key timing distinction is whether a relayer fills the request promptly or the protocol has to use its fallback process.

In practical terms, treat “about two seconds” as the usual destination fill time once the deposit is available to relayers, not as a guaranteed end-to-end clock. A pending source transaction has not reached the point where the relayer can pay out.

Why can a transfer take longer?

A transfer takes longer when the source transaction is delayed, a relayer does not fill the request promptly, or the protocol needs to complete a slow fill. After you submit, Across records the deposit on a SpokePool contract on the origin chain. Relayers watch for that deposit and, once they can act on it, send the requested output token from their own funds to the destination address.

This is a little like a shop letting a customer leave with an item while the payment is checked in the background: the relayer fronts the destination funds, then seeks repayment through Across settlement. If relayers are unavailable or the request does not get a fast fill, liquidity providers can fund a slow fill instead. That path is tied to protocol settlement and its challenge period, so it can take far longer than the normal fill. Across’s documentation describes settlement as background work; relayers’ repayment is separate from the user’s receipt.

Several parts of the route can affect what you see:

• Source-chain inclusion: the deposit must appear on the origin chain before the relay can proceed.
• Relayer fill: a relayer sends the destination funds; this is the fast, user-facing stage.
• Fallback fill: if a fast fill does not happen, the protocol may use liquidity-provider funds through a slower settlement path.
• Settlement: Across verifies fills and repays relayers later, in aggregated bundles.

A slow status does not by itself mean the tokens are lost. It may mean the source deposit is still pending, or that the transfer is waiting for a fill or settlement step. Use the transfer status and transaction records on both chains to identify which stage is incomplete.

How can you check the timing before you send?

Check the quote for the exact origin chain, destination chain, token and amount you plan to use. Across’s API includes an expected fill-time estimate, and its interface may show route timing before you confirm. Because liquidity and fees vary by route, a quote for a different token or amount may not describe your transfer.

After submitting, first confirm that the source transaction succeeded. Then look for the destination fill: Across’s tracking tools can report whether the deposit has been fulfilled. If the destination funds have arrived, protocol settlement can continue in the background. If they have not, the status can help distinguish a source-chain delay from a pending or slow fill.

The useful measure is destination delivery, not when the relayer receives repayment. Most Across transfers are designed to deliver funds in roughly two seconds after the deposit is detected; slower fallback fills and later settlement follow a different clock. Check the live route estimate before sending, then watch the source deposit and destination fill as separate steps.