My port-in was declined
Last updated: April 3, 2026
If your port request was submitted but came back declined, it usually means something in the information provided didn't match your carrier's records, or there's a restriction on the account.
Common reasons for a declined port
Account number, PIN, or ZIP code submitted didn't match exactly
The number was recently cancelled or is no longer active
Port protection is enabled on your old account — contact your carrier to disable it
The number is ineligible for porting (some VoIP, landline, or prepaid numbers have restrictions)
What to do
Contact your current carrier to verify the exact credentials needed
Confirm the number is still active and in good standing
Ask if any port freeze or protection is in place and remove it
Resubmit through the app once the details are corrected
If the port is declined a second time with the same reason, contact support — we can help identify whether the issue is on our side or with the losing carrier.
This article doesn't cover:
Port blocked immediately →My port-in was blocked
Port delayed →My port-in is delayed or stuck
Port failed →My port-in failed — what do I do?