[BUG REPORT] Persistent 400 Bad Request on startSmsPinVerification - Registration Blocked for 72 Hours
The AWS account registration flow is a complete trash. For three consecutive days, I have been locked out of the sign-up process by a persistent 400 Bad Request error on the startSmsPinVerification endpoint an issue clearly rooted in your server-side throttling logic rather than any user-side misconfiguration. Despite attempting the process across multiple devices, distinct browsers, and even international phone numbers, your automated security filters have effectively 'blocklisted' a legitimate developer trying to onboard. To make matters worse, your Support system is caught in a useless loop, firing off automated template responses that tell me to 'verify my phone number' the very thing your broken API is preventing me from doing. It is embarrassingly ironic that a global leader in cloud infrastructure cannot manage a basic SMS handshake without collapsing into an unrecoverable state for 72+ hours where there is barely any information on what happened except 'Sorry, something went wrong please try again'. You are actively trying to make it a bitter experience for a student like me to use this platform and host my very own projects.
- Language
- English
- Newest
- Most votes
- Most comments
Based on what you’ve described, this does not appear to be a client-side issue, but rather a temporary block triggered by AWS account registration safeguards.
What’s likely happening
During account creation, AWS performs automated checks on:
- Phone number validity (mobile vs VoIP)
- IP reputation and geolocation
- Frequency of verification attempts
If multiple attempts are made (even across devices or numbers), the system may temporarily throttle or block SMS verification requests. This can result in errors like:
400 Bad RequestonstartSmsPinVerification- No OTP being delivered
This behavior aligns with AWS protections designed to prevent abuse of the signup process.
Recommended steps (based on AWS guidance)
To resolve this, I suggest:
-
Wait 24–72 hours before retrying
- Avoid repeated attempts during this window, as it can extend the block
-
Use a valid mobile number
- Ensure it is:
- Not a VoIP/virtual number
- Capable of receiving international SMS
- Ensure it is:
-
Avoid VPNs or proxy networks
- Use a stable residential or mobile network
-
Retry from a clean environment
- New browser session or incognito mode
- Clear cookies/cache
If the issue persists
If you’re still blocked after the cooldown period, the best path is to contact AWS Support via: https://aws.amazon.com/contact-us/
You can also refer to AWS official documentation here:
- Troubleshoot AWS account sign-up issues : https://docs.aws.amazon.com/signin/latest/userguide/troubleshooting-sign-in-issues.html
- AWS account creation : https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-creating.html
Hello Sandeep,
I am answering you after 72 hours because that' the time you told me to wait and yes still getting the same "something went wrong error, please try again. And if error persists, contact support". I did it from a new fresh without any cached browser but still the same problem. And also I cannot contact support because I get a bot response saying my account isn't complete yet please verify the phone number. So as you can see I am stuck in a loop where I can't verify my phone number neither can I contact support.