“Too Many Attempts”: How Long to Wait and What to Do
This message means the app has stopped sending codes for a while: to that number, to your device, or to both. More requests make it worse.
By the editorial team · Updated · 4 min read · What changed- Stop requesting codes: every request can extend the pause.
- If every number shows the error, the lock is on your device.
- Come back with one fresh number and request the code once.
“Too many attempts” means the app has paused codes — for the number, for your device or for both. More requests usually make the pause longer. This guide explains how to tell which kind of lock you have, how long to wait, and how to come back with one fresh number so the next request actually gets a code.
For: Anyone who sees “too many attempts” or “try again later”.
Covers: Number locks vs device locks, waiting, and how to avoid the error.
Not covered: Account bans after sign-up — that’s a different problem.
Key terms: OTP, Public inbox
What Causes the “Too Many Attempts” Error
The error appears when an app sees too many code requests from one number, device or IP address in a short time. Wrong codes and busy shared numbers trigger it too. The common causes are listed below.
- Several code requests for the same number in a row.
- Trying many numbers quickly from one device or IP address.
- Typing a wrong code several times.
- A shared number that many other people are using with the same app right now.
Is the Number or the Device Locked?
If the error appears on one number only, the number is locked; if it appears on every number you try, the lock is on your device or IP address. The table shows how to tell and what to do in each case.
| Sign | Likely lock | What to do |
|---|---|---|
| The message appears on one number, another number works | Number | Use a different fresh number |
| The message appears on every number you try | Device or IP | Stop and wait before you try again |
| The message appears after a wrong code | Account or session | Wait, then request one new code |
What to Do When Codes Are Paused
Stop requesting codes, wait for the pause to end, then come back with one fresh number and request the code once. Short pauses last minutes; repeated ones can last hours. Here is the order to follow.
- 01Stop requesting codes. Every new request can extend the pause.
- 02Wait. The lock is usually temporary, and its length is set by the app, not by the number. Short locks often last minutes; repeated ones can last hours.
- 03Come back with one fresh number. Pick one from Added in the Last 24 Hours, request the code once and watch its inbox.
- 04If the lock follows your device, switching numbers won’t help. Wait it out before you try any number, free or private.
How to Avoid “Too Many Attempts” Next Time
Fewer, slower requests prevent most locks. Wait two minutes before pressing resend, check the inbox for a recent code from your app, copy the code instead of typing it, and test one number at a time.
- Wait the full two minutes before pressing “resend”.
- Check the number’s inbox for a recent code from your app before you use it.
- Copy the code instead of typing it from memory.
- Try one number at a time, and switch country after two failures rather than burning through ten numbers: pick a backup country.
Telegram shows this message often; its quirks are covered in the Telegram guide.
“Too Many Attempts” FAQ
How long does a “too many attempts” lock last?+
The app decides, and it doesn’t publish the length. Short locks often clear within minutes; repeated attempts can stretch it to hours. Stop requesting codes while you wait. If the message still appears after an hour, wait until the next day before trying again.
Will a different free number get around it?+
Only if the lock is on the number. If every number shows the same message, the lock is on your device or connection, and a new number won’t help. To tell which it is, try one fresh number once: if it shows the same message immediately, wait.
Can the lock affect my own phone number?+
If the lock is on your device or account, yes, it can apply to any number you try on that device until it clears. That is why it’s worth waiting out the pause before you switch to your own number. Requests from a locked device often fail on every number until the app lifts the limit.
Does a private number skip the lock?+
Not a device lock. A private number helps when the shared number itself is overused, not when the app has paused your device. If every number shows the same error, wait out the pause, often a few hours, and request the code once. Then a private number can help if the app refuses shared lines.
Why did I get this message on the first try?+
Other people may be using the same public number with the same app at the same time. Pick a quieter number with fewer recent messages from that app. Open the number’s inbox and count recent codes from your app: several in the last hour means the line is busy right now.
- Across 10 tracked apps, 7% (Tinder) to 91% (Telegram) of codes reached our free numbers.
- Telegram, Signal and Snapchat passed more than 80% of the time; Gmail, ChatGPT and Tinder passed less than 35%.
- New numbers are added every 24 hours; codes stay visible for 10 minutes.
We triggered and waited out this error on our own numbers with several apps. Lock length is set by each app and isn’t published, so we describe the pattern rather than exact times.
When this guide won’t help- The lock is on your device or IP address: new numbers won’t help until it ends.
- Shared numbers used by others at the same moment can trigger the lock on the first try.
General information only. Apps change their checks often; follow each app’s terms and never use a free number for banking, payments or government services.