Hello,
Since last Friday, we started receiving such errors very often when placing market orders via REST. The response seems to come after a significant delay when calling the POST endpoint. Does anyone else have a similar experience?
Binance API system operates asynchronously, which naturally allows for some delay as requests are processed based on the order they are received and according to server load at that time. Depending on the data source that the endpoint interacts with (Matching Engine, Memory, or Database), the response times can vary. Endpoints pulling data directly from the database are usually slower compared to those fetching from the memory or matching engine
Additionally, the API requires each request to be timestamped, and there is a ‘recvWindow’ parameter that defines the validity period of the request. If your requests experience high latency, it’s worth ensuring that your server’s time is synchronized with Binance’s server time, and consider adjusting the ‘recvWindow’ parameter to accommodate any network delays you are observing.
For further details on managing API calls and understanding potential latency, you can refer to the the below:
Thank you for your reply, I am, however, aware of all those circumstances. My question was if anyone else has experienced increased lag when placing market orders over REST.
What happened after this issue occurred? Did it automatically resolve itself after some time passed? or did you have to do something to fix it (e.g. restart your machine)? The authentication mechanism for any API calls of this type involves a timestamp and a recv window. If your timestamp is significantly behind the server timestamp (bigger than the recv window), you will start seeing this error. A momentary hiccup should be network jitter or potential lag on the server side, but if it’s a regular occurrence, the first troubleshooting step should be to ensure your system clock is in sync. Lots of guidance here on how this works and how to sync your clock with tools such as ntp: