Inconsistent results in response from /api/v3/openOrders ?

Hi - I had an order disappear then reappear from this response despite being filled. Here’s the sequence I saw:

  1. Order present (not filled)
  2. Order got filled
  3. Order disappeared (correct)
  4. Order reappeared as ‘new’ (incorrect)

Is this common/expected? I’ve used the API for a while and not had this issue so I’m wondering if it’s something new or if something has changed. I have the order IDs and timestamps if anyone from Binance would like to look into it.


Thanks for the feedback, I’ve informed internally. During high load peaks, openOrders can be affected, so it’s advised to use websocket which is more consistent.