> For the complete documentation index, see [llms.txt](https://docs.futuregold.us/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.futuregold.us/ai-arbitrage-trade-system/5.-technical-details/5.3-latency-reduction/5.3.1.-why-latency-is-a-problem.md). # 5.3.1. Why Latency Is a Problem As highlighted, latency is the delay that occurs between the request being made and the response. When it comes to trading, it has a great impact on the profitability. Traders and investors need to have an accurate snapshot of the market so that they can make prudent decisions. The high volatility means that prices are always highly fluctuating. Therefore, an accurate reading and a fast transmission of instructions are both integral to making profits. Most exchanges have a high latency. A high latency means that the delay between the requests and the results is considerable. The result tends to be inaccurate readings of the market. If the chart suite used has a high latency, the trader is not aware of price changes. They may be seconds behind others making similar trades. These unexpected price changes can cause serious losses. An example is a trader who wants to make a trade buying at 5.5 and selling at 7.0. If there is a high latency, his purchase request will be approved when the price has already risen to 6.0. This reduces the profits. In the worst, case, if the transaction cost is greater than the margin, then the trade makes losses. This is why low latency communication channels should be used with exchanges. Compared to traditional financial markets, the terminals and network interfaces of crypto exchanges seem to be from a previous era. There is huge potential for improvement, and Future Gold ARBITRAGE acquired lots of expertise in this area. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.futuregold.us/ai-arbitrage-trade-system/5.-technical-details/5.3-latency-reduction/5.3.1.-why-latency-is-a-problem.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.