You enter your phone number, get an SMS code, type it in, and instead of finishing signup ChatGPT either shows this phone number is already linked to the maximum number of accounts or just throws you back to the phone-entry screen. The loop is almost always one of four things: the number was already used to verify a ChatGPT account, it is a virtual / VOIP number that OpenAI rejects, the country is region-blocked, or your network looks risky and the code never reliably lands. Fastest fix: use a real mobile SIM on a major carrier that has never been used for ChatGPT, turn off any VPN, and enter the code within a couple of minutes from a clean incognito window.
One thing changed in 2026 worth knowing up front: as of June 2026 OpenAI no longer forces phone verification on every plain web signup. The phone step now appears mainly when a risk check fires (shared IP, datacenter / VPN exit, suspected automation) or when you sign in through Codex / the CLI, and it is still required the first time you create an API key on platform.openai.com. So if you are looping, fixing the trigger (the network, the number type) often matters more than the number itself.
Which bucket are you in?
| Symptom | Most likely cause | Jump to |
|---|---|---|
this phone number is already linked to the maximum number of accounts | Number already bound to a ChatGPT account | Cause 1 / Step 7 |
| Form accepts the number, then rejects after the code, or rejects instantly | VOIP / virtual number | Cause 2 / Step 5 |
| SMS never arrives even after minutes, or the correct code is always rejected | Region not supported | Cause 3 / Step 6 |
You've made too many phone verification requests. Please try again later. | Resend rate limit (24h) | Cause 4 / Step 4 |
| Code arrives late, then is rejected as expired | Carrier delivery delay | Cause 4 / Step 1 |
| Loop only on VPN, shared Wi-Fi, or Codex / CLI login | Risk trigger on your network | Cause 6 / Step 6 |
| Loop disappears in incognito | Stale half-finished signup state | Cause 5 / Step 2 |
Common causes
1. Number was already used to verify another ChatGPT account
OpenAI binds one ChatGPT signup per phone number, effectively for the life of the number. If you ever signed up before (Free, Go, Plus, or a now-deleted account), that number is bound and you will see this phone number is already linked to the maximum number of accounts.
How to judge: Try to log in with the email you think is tied to the number. If it works, that account already exists. If you no longer have access, recovery has to go through help.openai.com first.
2. VOIP / virtual number rejected
Google Voice, TextNow, Twilio, second-line apps, and some MVNO ranges are flagged as VOIP and rejected. OpenAI is one of the stricter platforms for VOIP detection, so SIM numbers have a much higher acceptance rate than any virtual option. The form sometimes accepts the number, then rejects it after you enter the code; sometimes it rejects on submit.
How to judge: Run the number through any carrier-lookup tool. A type of VOIP or Wireless Reseller means it will almost certainly be rejected.
3. Region blocked or not on OpenAI’s SMS list
Some country codes (sanctioned regions, or low-deliverability ones) cannot complete SMS verification. The code may never arrive, or a correct code may always be rejected. This is separate from the broader unsupported country block that stops you before signup even starts.
How to judge: You never receive the SMS at all after several minutes, or the same correct code is rejected repeatedly. If signup is blocked before the phone screen with an unsupported-country message, see OpenAI’s supported-countries help article instead.
4. Carrier delivery delay or resend rate limit
Two distinct timing problems live here. Some carriers delay SMS by 5-15 minutes; the 6-digit code expires in roughly 10 minutes, so by the time you enter it ChatGPT rejects it as expired and asks for a new one. Separately, hammering “Resend” trips a rate limit and you get You've made too many phone verification requests. Please try again later., which can lock that number for about 24 hours.
How to judge: Compare the SMS timestamp to when you entered it — over 10 minutes apart means expiry. If you see the “too many requests” string, you are rate-limited and must wait, not retry.
5. Browser cache / partial signup record
If a previous attempt half-completed (email verified, phone failed), the next attempt can pull stale state from cookies, skip steps, and loop.
How to judge: Clear cookies and try in an incognito window. If the loop disappears, it was cached state.
6. Risky network triggered the check (new in 2026)
Because the phone step is now risk-driven, signing up over a VPN, a shared office / café Wi-Fi, a datacenter IP, or through Codex / the CLI can both cause the verification prompt and make it loop. OpenAI treats those exits as higher-abuse, so codes are throttled or the check repeats.
How to judge: Switch to home Wi-Fi or mobile data with no VPN. If the loop only happens on one network or only inside Codex, the network is the trigger.
Before you start
- Use a real mobile number on a major carrier (AT&T, Verizon, T-Mobile, Vodafone, etc.). Do not start with a VOIP number.
- Turn off VPN, especially anything that changes your country. Verification is region- and IP-sensitive.
- Have the phone in your hand with signal confirmed — not in another room or on Wi-Fi calling only.
- Sign up over home Wi-Fi or mobile data, not a shared / corporate network if you can avoid it.
Information to collect
- Exact error message and the screen where it appeared.
- Country code and carrier of the phone number.
- Whether the number is postpaid, prepaid, or VOIP.
- Time between SMS receipt and code entry.
- Browser, OS, and whether you are in incognito.
- The network you are on (home, mobile data, office Wi-Fi, VPN) and whether this is a web signup or a Codex / CLI login.
- Whether you have ever signed up for ChatGPT before with this number or email.
- Whether you can receive SMS from other services (banking, Google) without delay.
Step-by-step fix
Step 1: Test SMS deliverability with another service
Before blaming OpenAI, send yourself a test SMS via Google’s password reset, your bank’s 2FA, or any other service. Arrived in under 30 seconds? The carrier is fine. Took 5+ minutes or never arrived? Carrier delivery is the problem — use a different number.
Step 2: Clear all OpenAI-related cookies and start fresh
Open an incognito / private window, or clear cookies for chatgpt.com, openai.com, and auth.openai.com. Go to chatgpt.com and choose Sign up. Enter email and password (or SSO), receive the email verification, click the link, then reach the phone screen.
Step 3: Enter the number in international format
Always use +CountryCode NumberWithoutLeadingZero:
US: +1 5551234567
UK: +44 7700900123
Germany: +49 17612345678
India: +91 9876543210
China: +86 13800138000 (note: mainland numbers are frequently blocked)Missing the + or dropping the country code causes silent rejection.
Step 4: Enter the code within 5 minutes — and do not spam Resend
The moment the SMS arrives, switch back to the browser and enter it immediately. If a slow entry caused the loop, request one new code and prioritize speed.
If nothing arrives within 5 minutes, click “Resend” exactly once and wait another 5. Do not click it repeatedly: more than two resends commonly returns You've made too many phone verification requests. Please try again later. and locks the number for about 24 hours. If you already hit that message, stop — switch to a different number or wait a full day; retrying sooner just extends the lock.
Step 5: If VOIP / virtual, switch numbers
OpenAI’s VOIP filter is strict and there is no software workaround as of June 2026. If your number is Google Voice / TextNow / Twilio, you have three real options:
- Borrow a friend’s real mobile number for verification — the number is bound to your account afterward, so they cannot use it for their own ChatGPT later.
- Buy a prepaid SIM in a supported country. SIM numbers from higher-acceptance regions clear far more often than any virtual number.
- Wait for OpenAI to loosen VOIP policy (not reliable).
Step 6: For region or network blocks, do not use a VPN to fake location
A VPN changes your IP but cannot change the country code of the phone number, and SMS verification reads the number’s country, not your IP. Worse, a VPN or datacenter IP now adds risk checks rather than removing them. If you are looping only on a VPN, shared Wi-Fi, or a Codex / CLI login, turn the VPN off and retry from home Wi-Fi or mobile data with a real local number. If the country itself is unsupported, no VPN fixes that — you need a number from an unblocked country.
Step 7: If the number is “already in use” and you do not know the account
Go to help.openai.com, open Messages (the chat widget) or submit a request, and describe it plainly: “Phone number +1 555… returns this phone number is already linked to the maximum number of accounts, but I do not have access to the associated account.” Support will either help recover the original account or release the number after identity verification. Expect this to be slow (often 7-14 days).
How to confirm it’s fixed
- After entering the SMS code, the page advances to the avatar / name screen rather than back to phone entry.
chatgpt.comloads the chat interface with your new account email shown top-right.- Settings → Account lists the verified phone number.
- An “Account created” confirmation email is in your inbox.
- You can sign out and back in without being asked to verify again.
Long-term prevention
- Sign up with a real, primary mobile number — not a burner or VOIP — to avoid future verification headaches.
- If you might want multiple ChatGPT accounts later (work, personal), use a separate real number for each from day one.
- Do not delete an account whose phone you might want to reuse — OpenAI does not reliably release the number on deletion.
- For corporate signups, use a dedicated company phone or your work mobile, not a personal cell you may later use for a personal account.
- Save the recovery email separately from the signup email so future verification flows have an alternative.
Common pitfalls
- Hitting “Resend” rapidly — this triggers the 24-hour rate limit, not a faster code.
- Entering the number without the country code — the form often accepts it but verification fails silently.
- Using a VPN during signup — extra anti-fraud checks make verification harder, not easier.
- Reusing a number from a deleted account — the binding persists after deletion.
- Switching browser or tab while waiting for the code — the original verification session expires.
FAQ
Q: Why does it say my number is “already in use” if I never had ChatGPT?
A: Likely a family member or coworker used your number on their account, or you signed up briefly and forgot. The current wording is this phone number is already linked to the maximum number of accounts. Recover or release the number via help.openai.com.
Q: Do I even need phone verification anymore?
A: Not always. As of June 2026 plain web signup often skips it, but the phone step still appears on risky networks, through Codex / the CLI, and the first time you create an API key on platform.openai.com.
Q: How many ChatGPT accounts can one phone number have? A: One. The binding is effectively permanent for the life of the number.
Q: Does deleting my account release the phone number? A: Officially yes, in practice often no — OpenAI keeps anti-abuse signals on the number for an extended period.
Q: I got “too many phone verification requests” — how long until it clears? A: Roughly 24 hours. Do not keep retrying, which can extend the lock. Switch to a different real number or wait it out.
Q: Can a virtual number ever work? A: Rarely and unreliably. OpenAI’s VOIP detection is strict; a physical SIM from a supported country is the only dependable path.