667 MNP Not Working? Common Problems & Their Solutions
Whether 667 isn't replying at all, keeps returning a confusing status, or your actual port request seems frozen mid-process, this guide walks through every known cause — ranked by how often it actually happens — and the exact fix for each one.
Why MNP Checks And Requests Break Down
Number portability involves more moving parts than a simple status lookup — a 667 query has to reach PTA's MNP database correctly, and an actual port request has to clear checks at both your old and new operator before it finalizes. A failure anywhere in that chain looks the same from your side: nothing happens, or something happens that doesn't match what you expected.
It helps to separate two different things that both get called "667 not working." The first is the status check itself failing — your SMS to 667 doesn't get a reply, or the reply doesn't make sense. The second is the underlying port request being stuck, rejected, or delayed, which 667 will actually report correctly, but the result itself feels like a problem because the port isn't going the way you expected. Most complaints are really about the second issue, even though people describe it as "667 isn't working."
Knowing which of these two you're dealing with changes the fix entirely. A failed SMS check is a connectivity problem you can usually solve yourself in minutes. A stuck or rejected port is a data problem — an unpaid bill, a documentation mismatch, or a cooling-off period — that needs to be resolved with your operator directly, no matter how many times you resend the check. If you haven't already, our complete 667 MNP SIM check guide covers the correct format and what each status actually means, which is worth confirming before assuming something's broken.
Quick Fixes For A Silent Or Failed 667 Check
Try these in order if your SMS to 667 isn't returning any reply, or returns an error instead of a status.
01Re-check the number format
02Confirm standard SMS balance
03Improve your signal before resending
04Wait a few minutes before retrying
05Restart your phone
06Ask your intended new operator directly
Do's And Don'ts When A Port Isn't Behaving
✅ Do
- ✓Clear any outstanding postpaid balance before requesting a port.
- ✓Keep your original SIM active until the new one is confirmed working.
- ✓Note the date you submitted the port request if you need to follow up later.
- ✓Recheck 667 after 24–48 hours rather than every few minutes.
- ✓Contact the new operator's helpline if a port stays "in process" beyond a week.
🚫 Don't
- ✕Submit a second port request while one is already pending — this usually resets or complicates the queue.
- ✕Deactivate or discard the old SIM before the port fully completes.
- ✕Assume "not eligible" is permanent without asking your current operator why.
- ✕Pay any third party claiming to speed up or force a stuck port.
- ✕Try porting again immediately after a rejection without fixing the underlying cause first.
Three Different Ways "Not Working" Shows Up
Being specific about which symptom you're actually seeing makes it much faster to find the right fix below.
Your SMS sends but nothing comes back. Almost always a formatting, signal, or SMS-bundle issue rather than a fault with the number itself.
You get a reply, but it doesn't match what you expected — showing the wrong current operator, or "not eligible" with no explanation given.
667 replies correctly, but the actual porting process at your operator isn't progressing — this is a request-processing issue, not a 667 fault.
Which Network You're Porting Between Can Matter
667 itself behaves the same regardless of operator, but the speed and smoothness of the actual port depends heavily on both the network you're leaving and the one you're joining.
Keep Checking 667 vs. Escalating To Your Operator
📩 Keep Rechecking 667
The right move if it's been less than 48 hours since you submitted a port, or if your last check simply failed to send due to signal or a bundle issue. 667 is a status mirror, not a control panel — it can only tell you what's already true in the system, so rechecking too soon just repeats the same answer.
☎️ Contact Your Operator Directly
The better move once 667 has clearly shown "not eligible" or a stuck "in process" status for several days. Operator support staff can see the specific internal reason — an unpaid bill, a documentation mismatch, or a manual review flag — that 667's short status text simply doesn't display.
If you're unsure which SIMs are even registered to your CNIC before troubleshooting a port, run a quick 668 SIM check first to confirm.
Every Common 667 & Porting Problem — With The Fix
Ordered from most to least common, covering both the SMS check itself and the underlying port request.
A note on persistence: if a port stays blocked well beyond the timelines above with no clear reason given, escalate through your operator's official complaint channel rather than repeatedly resubmitting the request, which can push it further back in the queue. If you ever discover a number under your own CNIC has been ported without your knowledge or consent, treat it as a security issue — see our guide on removing an unauthorized SIM, and file a formal report with the NCCIA if fraud is confirmed.
Frequently Asked Questions
Why does 667 say "not eligible" when I have no unpaid bills?
Eligibility locks can also come from a very recent prior port, an open dispute, or a documentation mismatch — none of which are unpaid-balance related, so it's worth asking your operator to check the specific reason.
How long is the mandatory cooling-off period between ports?
PTA enforces a waiting period after each port before the same number can be ported again, intended to prevent abuse of the system — your operator can confirm the exact remaining time for your number.
My port completed but I lost service for a few hours — is that normal?
A brief service gap during the final cutover is expected as the number's routing switches networks, and it typically resolves on its own within a few hours.
Can I cancel a port request once it's submitted?
Yes, but only by contacting the new operator you submitted the request through — 667 itself only reports status and can't submit or cancel a request.
Does a factory reset or new phone affect an in-progress port?
No — porting is tied entirely to the SIM and the CNIC behind it, not to any specific device, so changing phones mid-port has no effect.
Why does the reply show a different network than I expected?
If the number was ported previously, 667 always shows its current network, not the one it originally launched on — this is expected behavior, not an error.
Is there a way to speed up a slow port?
There's no official expedited option — the fastest path is confirming eligibility with 667 before submitting, since most delays trace back to an issue found only after the request is already in process.
Can prepaid numbers get stuck the same way postpaid ones do?
Yes, though less often — prepaid ports typically only stall due to formatting errors at submission or a very recent prior port rather than billing issues.
What should I do if both 667 and the franchise give conflicting answers?
Trust the franchise's internal system over 667's short SMS reply for edge cases, since staff can see the full record rather than a summarized status line.
Will retrying 667 too often get flagged as abuse?
There's no evidence of a penalty for retrying, but spacing checks out by several hours is more useful anyway, since the underlying status rarely changes within minutes.
Related & Official Resources
Still stuck after trying these fixes?
Recheck your number's status, or reach out with the specifics of your case.
Recheck Via 667