If you get blocked for requesting verification codes too frequently, wait at least 10 minutes before trying again. This is the minimum cooldown to restore attempts in most cases, but the exact time depends on the limit level triggered: a normal frequency limit resets in about 10 minutes, while a limit caused by too many failed login attempts can last up to 24 hours.
Step 1: Stop — identify which limit level you triggered
Before waiting, determine which message you see so you know the right waiting strategy.
Case A: The page says "Requests too frequent" or "Send code failed. Please click 'Get Code' again." — this is usually a short-term rate limit. Triggered by clicking "Get Code" too many times in a short period, and it generally recovers after 10 minutes. Binance Thailand site offered a more conservative suggestion: "If you clicked too frequently, wait 2 hours before trying again," but this information was from 2023 and later versions updated to a shorter wait time.
Case B: The page says "Too many login attempts" — this is an account-level security lock, usually triggered by entering wrong verification codes multiple times. You need to wait 24 hours before trying again.
Completion check: You have confirmed whether you are under a short-term limit or an account lock, and you know the corresponding wait time.
Step 2: Do two things while waiting — troubleshoot the root cause and prepare a backup method
Don't just wait idly for 10 minutes. Use this window to check why the request may have failed, so you avoid hitting the limit again as soon as it resets.
What to do: Check your phone network signal and SMS blocking settings, and see if any other verification methods are available.
How to do it:
Check your phone's signal strength, and make sure you haven't turned on "block unknown numbers" or SMS filtering, which might catch the verification code as spam.
Go to Binance Security Center and check if your account has a backup verification method set up (such as Google Authenticator, passkey, or email). If yes, and the SMS still hasn't arrived after 10 minutes, use the backup method to get the code and log in.
Completion check: Backup verification method confirmed to be working (or you've verified that network/phone settings are correct).
Common reasons for failure
If you keep clicking "resend" during the cooldown period, each click resets the timer and extends the waiting time. Do not request again — wait until the time is up, then make one clean attempt.
If you still can't log in after 24 hours, you'll need to go through the 2FA reset process: submit a video via email showing your face while holding your ID and reading a required statement. The review usually takes 48 hours. If you receive verification codes you did not request, it means someone is trying to access your account — immediately change your password and enable a hardware key or passkey for stronger protection.
How to verify after waiting
After the wait time, make one complete verification code request. If you receive and verify it successfully on the first try, the limit has been lifted. If it fails again but no longer says "requests too frequent," the problem is with your phone number or carrier — troubleshoot your SMS reception settings.
Next steps
Set up at least one backup verification method that is different from SMS (like Google Authenticator or passkey). Next time you encounter a verification code request limit, you can simply log in via the backup channel without waiting.
