If i get a 418 with a retry-after header of 120 seconds, and i wait exactly 120 seconds to dispatch further requests, most of the time i get further 418 responses with a retry-after header of 0 seconds. This lasts for ~100-500ms. If i wait for 1s then the retry-after specifies (eg 120 + 1), i do not see this Behavior. Seems the timer on the server running in ms and when sending the retry-after header seconds get floored instead of ceiled. Noticed this on https://api.binance.com/api/v3/* endpoints.