Porting Status Check: Where Your Number Is

To check the status of a number port, ask your new (gaining) carrier — their porting desk or customer portal is the only source of truth. The carrier you are leaving will not give you meaningful status, because the port is an order sitting in the gaining carrier’s queue, not theirs. There is no public lookup tool where you can type in a phone number and see port progress; status lives with the carrier that submitted the port request.

That answer frustrates people mid-port, so it is worth being blunt about why. A port is a carrier-to-carrier transaction: your new carrier submitted an order, your old carrier validated it, and a scheduled release date came back — or a rejection did. Every one of those events is visible to your new carrier and nearly invisible to you unless someone relays it. A good carrier relays it without being asked. If yours does not, this guide tells you what to ask for, what each answer means, and when a quiet port has crossed the line into a stalled one.

Who actually knows your port status

Your new carrier knows everything. They submitted the port order — formally an LSR, the carrier-to-carrier order form — and every response comes back to them: validation results, rejection codes, the committed release date, activation confirmation. When you contact their porting desk, ask three specific questions: Has the LSR been accepted or rejected? Is there a FOC date, and what is it? If it was rejected, what is the reason code?

Your old carrier knows almost nothing useful. The losing carrier sees an inbound port request against your account, but their support reps typically cannot tell you where it stands, and they have no incentive to chase it for you. Calling them for status wastes a day. The one thing the losing carrier is good for: confirming the exact account details on file — authorized name, account number, service address, PIN — which matters enormously if your port was rejected.

Third-party lookup sites know nothing. Port orders are not public records. Any site claiming to show live port status for an arbitrary number is guessing from carrier-of-record data, which only updates after a port completes.

The stages your port moves through

Every port passes through the same sequence, and “what stage am I in” is the real question behind every status check:

Stage 1 — Submitted. You signed the LOA, and your new carrier generated and submitted the LSR, the inter-carrier port order, to your current carrier. Nothing is committed yet.

Stage 2 — Validation. The losing carrier checks the LSR against its customer records. This ends one of two ways: acceptance, or a rejection with a reason code. Most port anxiety lives in this stage, because a rejection silently restarts the clock.

Stage 3 — FOC issued. The losing carrier commits to a release date — the FOC date, the anchor the whole cutover hangs on. Once you have a FOC date, your port has a real schedule. Before the FOC, any date anyone quotes you is an estimate.

Stage 4 — Activation. On or around the FOC date, your new carrier activates the numbers in the NPAC, the national portability database, and routing cuts over to the new network. This is the moment calls start arriving on the new carrier — a distinct event from the FOC date itself.

For pacing: simple business ports of 1-10 local numbers typically run 7 to 14 business days end to end. If you have heard that the FCC requires one-business-day ports, that rule (FCC Order 09-41) clocks only the losing carrier’s turnaround on a complete, accurate LSR for a narrowly defined “simple port” — a single-line account, no reseller — and most multi-number business ports fall outside it. The timeline section of our number porting guide breaks down where the real days go.

What each delay reason actually means

When your status check comes back “delayed” or “rejected,” the reason code tells you what to fix:

LSR rejection — data mismatch. The single biggest cause of port delays. Some field on the order — authorized name, account number, service address — did not match the losing carrier’s customer service record (CSR). “100 Main St” fails against a CSR that reads “100 Main St, Suite 210.” The fix is mechanical: call the losing carrier, read back the exact CSR details character by character, and have your new carrier resubmit. Each rejection-and-resubmit cycle costs days, and what happens inside an LSR rejection is worth understanding if you hit one twice.

Missing or wrong port-out PIN. Many carriers — nearly all wireless carriers, and a growing share of VoIP providers — require a PIN or number-transfer code before releasing a number. This PIN is often separate from your regular account password, and on wireless accounts it is usually generated on demand and expires. If your status says “PIN validation failed,” get a fresh port-out PIN from the losing carrier and resubmit.

Pending order on the account. An open order at the losing carrier — a feature change, an address update, a pending disconnect — can block the port until it clears. Ask the losing carrier to close or expedite the open order.

BTN conflict on a partial port. If you are porting the account’s main billing number while other numbers stay behind, the losing carrier must assign a new BTN first. Flag this up front; discovered late, it resets your FOC date.

Supplement in progress. Any change to the order after submission — corrected data, added numbers, a new requested date — reissues the order and can reset an already-issued FOC. If your date moved and nobody told you why, ask whether a supplement was filed.

When to escalate — and to whom

A port that is merely slow and a port that is stuck look identical from the outside. Use these thresholds:

No FOC date after 5-7 business days on a simple local port: ask your new carrier’s porting desk directly whether the LSR was rejected. Rejections sometimes sit unworked in a queue; a status check forces the resubmission.

The FOC date passed and your calls still route to the old carrier: escalate to your new carrier, immediately. Activation is the gaining carrier’s job — they trigger the NPAC update — and the carrier you are leaving has no reason to chase it. This is the single most common mid-port support ticket, and it is almost never the losing carrier’s fault at this stage.

Repeated rejections with shifting reasons, or silence past 15-20 business days on a simple port: ask your new carrier to escalate carrier-to-carrier. If the losing carrier is genuinely obstructing a valid request, an FCC complaint is the backstop — losing carriers cannot lawfully refuse a valid port, even over an unpaid balance. SIPNEX escalates through carrier-to-carrier channels on customers’ behalf and walks you through the FCC complaint if it comes to that.

One thing you should not do while waiting: cancel anything with the old carrier. The port itself terminates service for the ported numbers; canceling early can kill the numbers before they move.

Frequently asked questions

Most porting anxiety comes down to a carrier that does not communicate. SIPNEX, an FCC-licensed carrier, manages the LSR submission, tracks every rejection and FOC response, and tells you where your port stands without being asked — with no port-in or port-out fees on US numbers, and new DID numbers you can dial on the same day while the port runs in the background. Start your port or call (833) 665-2220 and ask the porting desk directly.