> For the complete documentation index, see [llms.txt](https://broker-docs.tiger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://broker-docs.tiger.com/english-2/frequently-asked-questions/withdrawal-from-the-broker-to-external-wallets-is-delayed.md).

# Withdrawal from the broker to external wallets is delayed

This issue is usually caused by **high network congestion**.

Network load depends on the number of transactions and processing servers at the current moment. Once all required network confirmations are received, the transaction will be considered complete.

You can check **network transaction speeds** through public sources. We **do not** have any influence over transaction speed, as blockchain processing depends on multiple factors and participants.

For example, when withdrawing funds from Binance, you can check the selected network’s congestion status [on this page](https://www.binance.com/en/network).\
For Bybit withdrawals, check the network status [here](https://www.bybit.com/en/announcement-info/deposit-withdraw/).

If the withdrawal remains in "Processing" status for more than an hour, please contact us at <broker.support@tiger.com> from the email linked to your Tiger.com Broker account. Go to the [History - Transactions](https://account.tiger.com/history/transactions) page, left-click once on the transaction in question, copy the Tiger.com ID, and send it to us:

<figure><img src="https://3857619824-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fyw4jlbyXBiRSgCIsu0tg%2Fuploads%2FLv7SL4oNE0sUELxA0Ree%2F%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%202025-03-08%20%D0%B2%2019.30.49.png?alt=media&amp;token=812dd0c2-b001-4e35-a159-304b192b3b14" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://broker-docs.tiger.com/english-2/frequently-asked-questions/withdrawal-from-the-broker-to-external-wallets-is-delayed.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.