Last Verified: June 2026 | By SimOwner.net.pk Editorial Team — Pakistan’s SIM verification specialists since 2015
You send your CNIC to 668 expecting a quick response, and nothing comes back. Or you dial 667 for number portability and get an error message instead of your PAC code. These PTA services are critical infrastructure for Pakistani SIM verification and management — and when they don’t respond as expected, the uncertainty about whether it’s a temporary glitch, a permanent problem, or a sign of something more serious can be frustrating.
This guide documents every common error pattern reported by users of PTA’s 667 (Mobile Number Portability) and 668 (CNIC SIM Verification) services, explains the most likely cause for each, and provides the specific solution or workaround. As of June 2026, both services remain core PTA infrastructure used by millions monthly — and most “not working” issues fall into a predictable set of categories with straightforward fixes. Check your situation against SimOwner.net.pk‘s verification guidance for additional troubleshooting context.
Understanding 667 vs 668 — Quick Clarification
Before troubleshooting, ensure you’re using the correct service for your need:
668 — CNIC SIM Verification: Send your CNIC number to 668 to see all SIMs registered on your identity. This is the service most relevant to fraud detection and SIM count verification.
667 — Mobile Number Portability (MNP): Dial 667 (as a call, not SMS) to generate a Porting Authorization Code (PAC) when you want to switch your number to a different network while keeping the same number.
Confusing these two services causes a significant portion of “not working” reports — make sure you’re sending an SMS to 668 (not dialing it) and dialing 667 (not texting it).
668 Service Errors — Complete Troubleshooting
Error 1 — No Response At All
Likely cause: Network congestion, temporary PTA system load, or incorrect message format.
Solution: Wait 5 minutes and retry. Confirm you sent only the 13-digit CNIC number with no dashes, spaces, or additional text. Example correct format: 3520112345671
Error 2 — “Invalid CNIC Format” Response
Likely cause: Dashes, spaces, or extra characters included in your message.
Solution: Remove all formatting — send only the raw 13 digits with nothing else in the message body.
Error 3 — Delayed Response (Beyond 5 Minutes)
Likely cause: High system load during peak usage hours (commonly evenings and around news events related to SIM fraud awareness, which spike 668 usage nationally).
Solution: Retry during off-peak hours (early morning, 6-8 AM, tends to have faster response times). If consistently delayed beyond 30 minutes, the issue may be operator-side SMS delivery rather than PTA’s system — try sending from a different network’s SIM.
Error 4 — “No SIM Registered on This CNIC” (But You Know You Have SIMs)
Likely cause: Temporary SVMS sync issue, or your CNIC number was entered incorrectly.
Solution: Double-check your CNIC number for typos. Retry after 1-2 hours. If problem persists beyond 24 hours despite confirmed correct CNIC entry, call PTA helpline at 0800-55055 to report the discrepancy directly.
Error 5 — Response Cuts Off / Incomplete List
Likely cause: SMS character limit truncation when a CNIC has many registered SIMs (close to or at the 8-SIM limit).
Solution: Use the web-based alternative at cnic.sims.pk, which displays complete results without SMS character constraints.
Error 6 — “Service Temporarily Unavailable”
Likely cause: Scheduled or unscheduled PTA system maintenance.
Solution: Wait several hours and retry. PTA system maintenance windows are typically brief (under 4 hours) but can occasionally extend longer during major system updates.
Error 7 — Response Shows Outdated Information
Likely cause: Recent SIM changes (new registration, deactivation, transfer) not yet propagated to SVMS — this propagation typically takes 2-4 hours but can extend to 24 hours during high system load.
Solution: If you made a SIM-related change in the last 24 hours, wait the full 24-hour window before treating the discrepancy as an error.
Error 8 — 668 Works From One Network But Not Another
Likely cause: Operator-specific SMS gateway issues affecting delivery to the 668 short code from that particular network.
Solution: Try sending from a different network’s SIM if available. Report the specific network issue to PTA helpline if it persists across multiple attempts.
Error 9 — Receiving Generic/Unrelated Auto-Reply
Likely cause: You may have sent the SMS to an incorrect number (668 vs a similar-looking number) or your operator’s system misrouted the message.
Solution: Carefully re-verify you’re sending to exactly “668” with no additional digits, and resend.
Error 10 — No Network Signal Prevents Sending
Likely cause: Basic connectivity issue unrelated to 668 itself.
Solution: Move to an area with stronger signal. 668 requires only basic SMS capability — even 2G signal is sufficient.
667 Service Errors — Complete Troubleshooting
Error 11 — Call Doesn’t Connect
Likely cause: Dialing 667 as an SMS rather than a call, or network-specific routing issue.
Solution: Ensure you are placing a voice call to 667, not sending a text message. Some networks require pressing the call button explicitly after entering 667 rather than relying on auto-dial features.
Error 12 — Call Connects But No PAC Code Received
Likely cause: SMS delivery delay for the PAC code (which arrives separately from the call itself), or your SIM has an active block preventing PAC generation.
Solution: Wait up to 10 minutes for the PAC SMS. If your SIM has any active operator-level restriction (postpaid balance dispute, fraud flag, compliance hold), the PAC may be blocked — contact your current operator’s helpline to check for any account holds.
Error 13 — “This Number Is Not Eligible for Porting”
Likely cause: Account holds outstanding balance, contract lock-in period not yet expired, or recent porting activity (a cooling-off period applies between consecutive ports on the same number).
Solution: Contact your current operator’s helpline to identify and resolve the specific eligibility block.
Error 14 — PAC Code Expired Before Use
Likely cause: PAC codes have a limited validity window (typically 4-15 days depending on current PTA regulation); if not used to complete porting within this window, a new PAC must be generated.
Solution: Dial 667 again to generate a fresh PAC code.
Error 15 — Receiving Unsolicited PAC Code (Without Requesting)
Likely cause: This is a critical security alert, not a technical error — someone else may be attempting unauthorized porting of your number, as detailed extensively in our MNP fraud guide.
Solution: Do NOT share this code with anyone. Immediately contact your current network’s fraud line to report a suspected unauthorized port attempt.
General Connectivity and Account-Level Issues Affecting Both Services
Error 16 — SIM Recently Activated (Within 24-48 Hours)
Likely cause: New SIM registrations take time to fully propagate across all PTA systems including the SMS gateways serving 668 and 667.
Solution: Wait 48 hours after activation before expecting full functionality from both services.
Error 17 — SIM Has a Compliance/Verification Hold
Likely cause: As detailed in our PTA SIM blocking guide, certain compliance issues can restrict specific service functions while basic calling still works.
Solution: Resolve the underlying compliance issue at your operator’s service center, which typically restores full service functionality including 668/667 access.
Error 18 — Roaming Status Affects Service Access
Likely cause: Both 667 and 668 are domestic Pakistani services — international roaming may not route correctly to these short codes.
Solution: These services require you to be using a Pakistani network signal (not international roaming) for reliable access. Wait until you have direct Pakistani network connectivity.
Error 19 — Postpaid Account With Outstanding Balance
Likely cause: Some operators restrict short-code SMS services (668) when a postpaid account has significant overdue balance.
Solution: Clear the outstanding balance, then retry.
Error 20 — Device-Level SMS Issues (Not Network-Related)
Likely cause: Your phone’s SMS app may have a filtering or blocking issue preventing the response from displaying properly.
Solution: Check your phone’s spam/blocked message folder. Try restarting your device. Test with a basic SMS to a friend to confirm general SMS functionality works correctly.
Less Common But Documented Errors
Error 21 — CNIC Recently Renewed/Updated
Likely cause: If you recently renewed your CNIC (updated photo, address, or transitioned to Smart Card format), there can be a brief synchronization window where SVMS data temporarily shows inconsistent results.
Solution: Wait 3-5 business days after CNIC renewal before expecting fully consistent 668 results.
Error 22 — Deceased CNIC Status
Likely cause: If checking a CNIC that has been formally marked as deceased in NADRA’s system (as covered in our deceased CNIC protection guide), 668 may return a different response format than for active CNICs.
Solution: This is expected behavior, not an error — for deceased person SIM verification, the response should still show registered SIMs (if any) for the family’s fraud-checking purposes; if the response seems incomplete, follow up via PTA helpline citing the deceased status context.
Error 23 — Multiple Rapid Successive Queries
Likely cause: PTA’s system may apply rate-limiting to prevent automated abuse if you send multiple 668 queries in quick succession.
Solution: Space out your queries — once per check is sufficient; avoid sending the same CNIC repeatedly within minutes.
Error 24 — B-Form/Minor’s Registration Number Used
Likely cause: B-Form numbers (for minors, as detailed in our minor SIM registration guide) follow the same 13-digit format and generally work with 668, but some edge cases in system handling have been reported.
Solution: If checking a B-Form-registered SIM via 668 produces unexpected results, verify directly with the network operator who processed that specific registration as a more reliable alternative.
Error 25 — NICOP Number Format Confusion
Likely cause: As detailed in our NICOP vs CNIC guide, NICOP and domestic CNIC typically share the same 13-digit number, but format confusion (using a different number than expected) can cause apparent errors.
Solution: Confirm you’re using the correct 13-digit number associated with your identity, checking against your physical NICOP/CNIC card directly.
When to Use Alternative Verification Methods
If 668 troubleshooting does not resolve your issue within a reasonable time, use these alternative verification pathways:
cnic.sims.pk: The web-based equivalent, useful when SMS-specific issues are the bottleneck.
Operator helpline: Each network can confirm your registered SIMs directly from their own systems, bypassing the 668/SVMS pathway entirely.
PTA helpline (0800-55055): For persistent or unusual errors, PTA’s direct support line can investigate system-level issues affecting your specific query.
SimOwner.net.pk’s verification tools: Comprehensive guidance for cross-referencing multiple verification methods when any single method produces inconsistent or unclear results.
For ongoing monitoring when you cannot rely on a single check, the live tracker resources at SimOwner.net.pk help establish patterns across multiple verification attempts over time.
Frequently Asked Questions
Q: Does 668 cost anything even when it doesn’t work properly?
A: No — 668 is designed to be a free service. If you are being charged for SMS sent to 668, this itself is worth reporting to your operator and PTA, as the service should not incur charges regardless of whether you receive a successful response.
Q: I’ve tried all troubleshooting steps and 668 still doesn’t respond after a week. What’s my next step?
A: Call PTA’s helpline at 0800-55055 directly, explain the specific troubleshooting steps you’ve already attempted, and request they manually check your CNIC’s SVMS status and investigate why 668 isn’t responding for your specific number/CNIC combination.
Q: Can VPN usage affect 668 or 667 functionality?
A: VPN affects internet/data traffic, not SMS or voice call routing — 668 and 667 use traditional telecom infrastructure (SMS and voice channels) rather than internet data, so VPN status should not directly impact these services.
Q: Is there a way to check if 668 is experiencing widespread outages versus just my individual issue?
A: No official real-time PTA service status page exists publicly as of June 2026. Checking with friends/family on different networks, or searching recent social media/news for widespread reports, can help distinguish individual versus systemic issues.
Q: Does the 667/668 error pattern change with seasonal SIM registration drives or enforcement actions?
A: Yes — during major PTA enforcement periods (such as compliance sweeps), system load increases as more users check their status, which can result in temporary delays. These periods typically resolve within days as system load normalizes.
Summary: Quick Troubleshooting Checklist
For 668 issues:
- Confirm correct format (13 digits, no dashes)
- Wait 5-10 minutes for response
- Try cnic.sims.pk as alternative
- Check signal strength
- Try different network’s SIM if available
- Call PTA helpline if persistent beyond 24 hours
For 667 issues:
- Confirm dialing (not texting) 667
- Wait up to 10 minutes for PAC SMS
- Check for account holds via operator helpline
- Never share unsolicited PAC codes
- Generate fresh PAC if previous one expired
For Pakistan’s most comprehensive SIM verification troubleshooting and fraud prevention resources, visit Sim Owner Details — Pakistan’s trusted SIM information resource since 2015.
All troubleshooting guidance based on commonly reported user experiences and PTA service documentation as of June 2026. SimOwner.net.pk is not affiliated with PTA or any network operator.
Related Guides on SimOwner.net.pk: