How long does a number port take with timelines explained

Takeaways

• Standard number ports take 3 to 7 business days. Telnyx FastPort completes eligible ports in 1 to 4 business days.
• Complex ports involving multiple numbers or carriers take 1 to 2 weeks. International ports can take up to 6 weeks depending on the country.
• Most delays come from documentation errors, account mismatches, or unpaid balances on the losing carrier side, not the porting process itself.
• Your number stays active during the entire porting process. There is no downtime.
• You can track porting status in real time through the Mission Control Portal or the Telnyx Porting Orders API.

How long does it take to port a number?

A standard number port takes 3 to 7 business days. Telnyx FastPort completes eligible ports in 1 to 4 business days. Complex ports with multiple numbers or carriers take 1 to 2 weeks. International ports vary by country and can take up to 6 weeks. Your number stays active until the transfer completes.

The exact timeline depends on three variables: the type of number you are porting, how quickly your current carrier responds, and whether your documentation matches their records. The table below breaks down each port type.

Wireless and VoIP numbers move fastest because carriers process them through automated systems. Toll-free numbers follow a separate RespOrg transfer process, which adds a few days. If you plan to run toll-free SMS on a ported toll-free number, factor in messaging re-verification after the port completes.

Landline and virtual phone numbers sit in the middle. Their timelines depend on how quickly the losing carrier releases the number. For a step-by-step walkthrough of the submission process, see our guide on how to port a number.

Why porting takes time and what slows it down

Porting is a two-party process. Telnyx submits the request, but the losing carrier controls part of the timeline. Losing carriers have no financial incentive to release a number quickly, and many still process port-out requests through manual review queues. Regulatory rules set minimum response windows, and carriers often use every day of them.

The largest delays are within your control. Documentation errors are the most common cause of porting rejections, and every rejection restarts the clock on that request.

Common rejection triggers and how to fix them:

• Account name or address mismatch. Copy the details exactly as they appear on your current carrier's records, not your billing memory.
• Unpaid balance. Settle any outstanding amount before submitting. Carriers can hold a number until the account is current.
• Missing or unsigned LOA. The Letter of Authorization must be signed by the account holder listed on the account.
• Wrong PIN or passcode. Confirm the port-out PIN with your current carrier. Some carriers generate one on request.
• Complex features on the line. Call forwarding, hunt groups, and voicemail bundles can block a port until they are removed from the account.

Fix the flagged issue, resubmit, and the port resumes. Telnyx surfaces the specific rejection reason in the Mission Control Portal so you know exactly what to correct.

Porting timelines by country

International ports follow each country's telecom regulations, and timelines vary widely. The figures below are estimates based on typical carrier processing times, not guaranteed SLAs. Source: Telnyx porting operations data.

If you need coverage in a market before a port completes, you can buy phone numbers in 140+ countries with instant activation and run them alongside your porting order. That keeps your business reachable while the transfer works through local regulation.

How to check your porting status

Every Telnyx porting order is trackable in the Mission Control Portal. Open the Porting section to see the current stage of each order, the FOC date once it is set, and any rejection details that need action. You do not have to email a support queue to find out where your port stands.

Developers can pull the same data programmatically through the Porting Orders API. The snippet below retrieves the status of a porting order in Python.

import requests

TELNYX_API_KEY = "YOUR_API_KEY"
PORTING_ORDER_ID = "your-porting-order-id"

response = requests.get(
    f"https://api.telnyx.com/v2/porting_orders/{PORTING_ORDER_ID}",
    headers={"Authorization": f"Bearer {TELNYX_API_KEY}"},
)
response.raise_for_status()

order = response.json()["data"]

print(f"Status: {order['status']['value']}")
print(f"Customer reference: {order.get('customer_reference')}")

for detail in order["status"].get("details", []):
    print(f"Issue: {detail['description']}")

You can also subscribe to porting webhooks to get notified the moment an order changes state, then forward alerts by text through the SMS API, which supports 10DLC, toll-free, and shortcode traffic. For a complete working project combining status webhooks with SMS alerts, see the Telnyx number porting status tracker example.

Port your numbers to Telnyx

Start by checking FastPort eligibility in the Mission Control Portal. Eligible numbers complete in 1 to 4 business days, and your service stays live for the entire transfer. Because Telnyx holds direct carrier licenses and owns its network, there are no intermediary resellers adding days on the receiving side of your port.

Once your numbers arrive, route calls over elastic SIP trunking with a 99.999% uptime SLA, or build programmable calling with the Voice API and its event-driven Call Control model. New to trunking? Read what is SIP trunking for a primer.

Frequently asked questions