⚠️ Troubleshooting Guide

668 SIM Check Not Working? Here's Why — And How To Fix It

If you've texted your CNIC to 668 and got nothing back, a delayed reply, or an error message, you're not alone — it's one of the most common complaints around PTA's SIM verification shortcode. This guide walks through every real cause, in order of how often each one actually happens, along with the exact fix for each.

🔍 Jump To Causes & Fixes 🌐 Try The Web Portal Instead

Understanding The Problem

Why A One-Line SMS Command Can Fail

On paper, 668 looks like the simplest possible interaction: send 13 digits, get a list back. In practice, that single text passes through several independent systems before you see a reply, and a hiccup at any one of them can leave you staring at an empty inbox.

Every message you send to 668 has to travel through your operator's own SMS gateway first, get handed off to PTA's central subscriber registry, get matched against millions of CNIC records, and then travel back through the same gateway as a reply. That's at least four separate hops, and each one has its own load limits, maintenance windows, and failure modes. Most of the time this happens in a second or two without you noticing any of it — but when one link in that chain is under pressure, congested, or briefly offline, the whole request can silently drop instead of returning an error you'd actually see.

This is different from a typical app crashing, where you at least get a visible message. An SMS that never arrives just looks like nothing happened, which is exactly why so many people assume their phone, their CNIC, or the 668 service itself is permanently broken — when in most cases it's one specific, fixable link in that chain. If you've already read our full guide on how the 668 SIM check works, you'll recognise this as the same flow — this page focuses only on where it tends to break.

You→Operator gateway accepts the SMS

⚠→Possible drop: bundle exclusion or congestion

668→PTA registry receives & queues the query

⚠→Possible delay: registry load or maintenance

Reply→Result routes back through your operator

Start Here

Quick Fixes To Try Before Anything Else

Work through these in order — they resolve the large majority of "668 not working" cases without needing to touch anything technical.

01Re-check your CNIC format

Remove every dash and space so the message body is exactly 13 digits and nothing else — no "CNIC:" prefix, no trailing full stop. This single formatting slip causes more failed checks than every other cause on this page combined.

02Confirm you have standard SMS balance

Shortcodes like 668 are billed at your operator's standard SMS rate, and many promotional or social-media SMS bundles specifically exclude shortcode traffic. Check your balance or package details before assuming the service itself is down.

03Move somewhere with stronger signal

SMS delivery to shortcodes is more sensitive to weak or fluctuating signal than a normal person-to-person text. Step outside, near a window, or to higher ground, then resend once you see full bars.

04Wait a few minutes and resend once

Brief registry congestion, especially during peak evening hours, can delay replies by several minutes without any actual fault. Give it 3–5 minutes before resending — sending repeatedly in a short window can make queuing worse, not better.

05Restart your phone

A stuck SMS queue on the device itself is a surprisingly common culprit, particularly after a recent software update. A restart clears the message queue and forces a fresh connection to your operator's network.

06Switch to the web portal

If none of the above resolves it, use cnic.sims.pk instead. It queries the same PTA registry over a data connection rather than SMS, which sidesteps operator-side SMS issues entirely.

While You Troubleshoot

Do's And Don'ts When 668 Isn't Responding

✅ Do

✓Wait a reasonable interval between retries — a few minutes, not a few seconds.
✓Double-check the destination number is exactly "668" with no extra digits.
✓Try from a second SIM if one is available, to isolate whether it's device- or network-side.
✓Note the exact time you sent the message if you plan to raise a complaint.
✓Fall back to the official web portal if SMS keeps failing.

🚫 Don't

✕Send the same request more than a handful of times in one sitting.
✕Assume a missing reply means you have zero SIMs registered — it usually means the message didn't complete its round trip.
✕Download unofficial "SIM checker" apps that ask for CNIC details outside SMS or the official portal.
✕Pay anyone claiming they can "force" a 668 reply for a fee — no such paid service is legitimate.
✕Assume the fault is permanent — most 668 outages are resolved within hours, not days.

Reading The Symptom

Three Different Ways "Not Working" Shows Up

"668 isn't working" actually covers three distinct symptoms, and each one points toward a different cause — so it's worth being precise about which one you're seeing.

Sent, No Reply

The message left your phone successfully but nothing ever comes back. Usually points to a bundle exclusion, weak signal at the moment of sending, or a temporary registry delay.

Error Reply

You get an automated response, but it says the format is invalid or the request couldn't be processed. This is almost always a formatting issue — dashes, spaces, or extra characters in the CNIC.

Send Failure

The message itself fails to leave your phone, often shown as a red exclamation mark in your messaging app. This points to an SMS balance, package, or device-level issue rather than 668 itself.

Operator-Side Quirks

Does The Problem Vary By Network?

668 itself is a single national shortcode, so the underlying service doesn't behave differently by operator — but each network's own SMS infrastructure can introduce its own point of failure before your message ever reaches PTA.

Jazz

High traffic volume, occasional peak-hour delays

Zong

Some data-only bundles exclude standard SMS

Telenor

Generally reliable; rare gateway maintenance windows

Ufone

Weaker signal in some regions slows delivery

SCOM

Limited coverage areas see the most frequent delays

None of this means one operator is "better" for checking your SIMs — it just means that if your first attempt fails, trying again from a second network's SIM (borrowing a friend's phone, for instance) is a genuinely useful diagnostic step, since it tells you whether the fault sits with your own operator's gateway or with the shared PTA registry itself.

Your Backup Option

SMS Retry vs. The Web Portal — Which Fixes It Faster?

📩 Keep Retrying 668

Worth doing once or twice if the cause looks temporary — weak signal, a brief registry delay, or a stuck device queue you've just cleared with a restart. It costs nothing beyond a standard SMS and works without any data connection. It's the wrong move, though, if you've already confirmed a formatting error or a bundle exclusion, since repeating the same broken request won't change the outcome.

🌐 Switch To cnic.sims.pk

The more reliable fallback when SMS keeps failing, because it queries the same PTA registry over a data connection instead of routing through your operator's SMS gateway — removing an entire link from the chain that could be causing the problem. It needs a working internet connection and a browser, but it typically shows more detail per SIM and gives you a result you can screenshot for a complaint if needed.

For the complete rundown of every official channel — including operator-specific "my number" codes — see our PTA SIM Check Online guide.

The Full List

Every Known Cause Of "668 Not Working" — And The Fix

This is the complete list, ordered from most to least common. Find the symptom closest to yours and apply the matching fix.

⚠CNIC entered with dashes or spaces

Fix: type only the 13 digits with nothing else in the message body — no dashes, spaces, or labels.

⚠SMS bundle excludes shortcodes

Fix: check your active package details; if it's a social-media or data-only bundle, top up standard balance instead.

⚠Weak or fluctuating signal

Fix: move to an area with full signal bars before resending, ideally away from thick walls or basements.

⚠PTA registry under heavy load

Fix: wait 5–10 minutes and try again once, especially during evening peak hours nationwide.

⚠Scheduled maintenance on the shortcode

Fix: switch to cnic.sims.pk, which runs on separate infrastructure from the SMS shortcode.

⚠Message stuck in your phone's outbox

Fix: restart the device to clear the local SMS queue, then resend from a fresh state.

⚠Sending while roaming outside Pakistan

Fix: 668 only works on a local Pakistani SIM with in-country signal — use the web portal while abroad instead.

⚠The SIM you're sending from is itself blocked or suspended

Fix: a blocked SIM may not be able to send SMS at all; borrow another working SIM to run the check.

⚠Reply split across two messages and one was missed

Fix: check your full inbox rather than just the notification preview, or use the web portal to see everything on one screen.

⚠Recently issued or updated CNIC not yet synced

Fix: allow 24–48 hours after any NADRA update before the PTA registry reliably reflects the change, then retry.

⚖️

A note on persistence: if 668 and the web portal both consistently fail for you specifically — while working for others around you — that's worth escalating rather than continuing to retry indefinitely. Contact your operator's official helpline first, since they can confirm whether the SMS ever reached their gateway at all. If you suspect the CNIC record itself has been tampered with or an unfamiliar SIM shows up once the check does go through, don't attempt to resolve it informally — follow the process in our guide on removing an unauthorized SIM, and file a formal report with the NCCIA if fraud is confirmed.

Questions

Frequently Asked Questions

Why did 668 work last month but not today?

The service itself doesn't change, but temporary registry load, a maintenance window, or a change to your SMS package can all cause it to fail intermittently even if it worked fine before.

Is there a way to know if 668 is down nationwide right now?

There's no official live-status page, so the most reliable test is trying the web portal at cnic.sims.pk — if that also fails to load or return results, the issue is more likely on PTA's side than your phone's.

I sent it correctly and still got an "invalid format" reply — why?

Double-check for autocorrect or predictive text inserting a space, and confirm you're not accidentally including a leading zero or country code that isn't part of your printed CNIC.

Does restarting my phone really make a difference?

Yes — a surprising number of "no reply" cases trace back to a message that silently failed to leave the device's outbox rather than any issue with 668 itself.

Can low phone storage cause 668 to fail?

Indirectly, yes — extremely low storage can prevent the messaging app from queuing or receiving new SMS correctly on some devices.

Should I contact my operator or PTA directly if nothing works?

Start with your operator's helpline, since they can confirm whether your message reached their SMS gateway; PTA is the right escalation point only if your operator confirms the message left their network successfully.

Is the web portal ever down at the same time as 668?

It's uncommon but possible during a wider PTA system update — if both fail together, the most reliable option is simply waiting a few hours and trying again.

Will retrying too many times get my number flagged?

There's no evidence of a penalty for retrying, but sending the identical request rapidly and repeatedly can worsen queuing for everyone, so spacing retries out is the better approach.

Does a factory-reset phone affect whether 668 works?

No — 668 depends entirely on your SIM, network, and PTA's registry, not on any app or setting stored on the device itself.

What's the very first thing I should check if 668 fails?

Your CNIC formatting — remove all dashes and spaces first, since that single fix resolves the majority of failed checks before you need to try anything else on this page.

Keep Reading