Logo

Hello, How can we help?

Get help straight from our team...

My port-in was declined

Activation & Switching

My port-in was declined

Last updated on 04 Sept, 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 your MyBundle account once the details are corrected

Log in to your MyBundle account, click the person icon in the top right, then click 'Mobile' to open your Mobile Dashboard. Select 'Contact Support' to start a chat with our mobile support team, who can help with any questions or issues.

Did you find this article helpful?
Previous

My port-in is delayed or stuck

Next