Port — Number Portability in Minutes, Not Weeks

Port

Download Playbook Run a Test Port

Live Migration Dashboard

API-first number portability for telecom operators, MVNOs, and enterprise IT. Migrate thousands of lines without a single minute of dead air.

Run a Test Port — Free Download Migration Playbook

port.io/dashboard — migration-control

LIVE

Numbers Ported Today

12,400of 14,000

89% complete · ETA 4 min

0%

AT&T→T-Mob

BATCH 4471

0%

VZW→MVNO-X

BATCH 4472

0%

Completed

BATCH 4470

Batch ID	Migration Path	Numbers	Progress	Status
BATCH-4471	AT&T → T-Mobile	3,200	100%	COMPLETE
BATCH-4472	Verizon → MVNO-X	5,800	97%	IN FLIGHT
BATCH-4473	Sprint → Metro	2,000	0%	QUEUED
BATCH-4474	T-Mobile → AT&T	3,000	0%	QUEUED

Last sync: 0.3s ago · 99.97% uptime · API v3.1

REST APIWebhooksNPAC Direct

12,847 numbers ported today99.97% uptime SLA< 7 min average migration350+ carrier connections0 ms service downtimeFCC · CRTC · Ofcom compliantDirect NPAC gatewaySOC 2 Type II certified12,847 numbers ported today99.97% uptime SLA< 7 min average migration350+ carrier connections0 ms service downtimeFCC · CRTC · Ofcom compliantDirect NPAC gatewaySOC 2 Type II certified

The Problem

Legacy porting is a
14-day hostage situation.

Every day a number sits in limbo is a customer who can't be reached, a transaction that can't close, and a support ticket that shouldn't exist. The legacy porting bureau process was designed in 1996. It shows.

Day 0

Manual CSV Upload

Operator exports numbers into a spreadsheet, manually formats fields per carrier spec, uploads to bureau portal.

Human error rate: 12%

Day 1–2

Carrier Acknowledgment

Losing carrier receives request. Confirmation window: 24–48 hours. No API. No webhook. Email only.

No programmatic confirmation

Day 3–4

Regulatory Hold

FCC/NPAC validation queue. Each number validated individually. Batch of 5,000 takes 36 hours minimum.

Avg hold: 38 hours

Day 5–7

Manual Carrier Coordination

Gaining and losing carriers must manually align on a Firm Order Commitment (FOC) date. Phone calls involved.

FOC rescheduled 34% of the time

Day 7–14

Cutover Window

Numbers go dark during cutover. Industry standard: 2–6 hours of service disruption per batch.

Avg downtime: 3.4 hours

Day 14+

Exception Handling

Failed numbers require manual resubmission. No batch retry. Each exception is a fresh ticket.

8.7% of numbers fail first attempt

Total Legacy Cost Per Migration

14 days average · 3.4 hrs downtime · 8.7% failure rate

See the Alternative →

The Solution

Same journey.
7 minutes.

Port replaces every manual step with a direct API call, every email with a webhook, and every 36-hour regulatory hold with a parallel validation engine connected directly to NPAC.

0:00

API Request Submitted

Automated

POST /v3/port/batch — JSON payload with number list, gaining carrier ID, and FOC preference. No CSV.

< 200ms response

0:01

NPAC Validation

Parallel

Direct NPAC gateway connection validates all numbers in parallel. Batch of 5,000 in under 60 seconds.

60s for 5,000 numbers

0:04

Carrier Coordination

Zero Manual

Automated FOC negotiation via carrier API. No phone calls. Gaining and losing carriers confirm programmatically.

FOC in < 4 minutes

0:06

Cutover Executed

Zero Downtime

Numbers switch carriers with sub-second routing handoff. Service continuity maintained throughout.

0ms service gap

0:07

Webhook Confirmation

Automated

POST to your endpoint: batch complete, all numbers resolved, carrier routing confirmed. Retry logic built in.

Real-time callbacks

< 7 min

Total migration time

vs 14 days legacy

0 ms

Service downtime

vs 3.4hr average

< 0.1%

Error rate

vs 8.7% legacy

5,000

Numbers/minute

parallel processing

Run a Test Port — Free See Full Comparison →

Head-to-Head

Every cell is
a verdict.

We're not asking you to take our word for it. Compare latency, error rates, batch limits, and API availability against legacy porting bureaus and manual carrier processes.

Metric	Port	Legacy Bureau	Manual Carrier
Average port time	< 7 minutes	3–5 business days	10–14 days
Service downtime	0 ms	2–6 hours	3–8 hours
Batch limit	Unlimited	500/batch	100/batch
API availability	REST + GraphQL	Web portal only	None / CSV
NPAC connection	Direct gateway	Via intermediary	Manual submission
Error rate	< 0.1%	4–6%	8–12%
Webhook callbacks	Real-time	Email only	None
Retry automation	Automatic	Manual resubmit	Manual resubmit
Regulatory compliance	FCC + CRTC + Ofcom	US FCC only	Carrier-dependent
SLA uptime	99.97%	99.5%	N/A
Support channel	API + Slack + 24/7	Ticketing (48h)	Carrier phone queue
Pricing model	Per number ported	Monthly flat + fees	Carrier rate card

Run a Test Port — Free Download Migration Playbook

Integration Architecture

REST in.
Webhooks back.

Port exposes a clean REST API with real-time webhook callbacks. No SDKs required. Direct NPAC gateway access. Carrier connections pre-negotiated. Your integration is a single afternoon.

API Reference — v3.1

Base: api.port.io

Sample Request

// POST /v3/port/batch
{
  "numbers": ["+14155552671", "+14155552672", ...],
  "gaining_carrier": "tmobile-us",
  "losing_carrier": "att-us",
  "webhook_url": "https://your.app/callbacks/port",
  "foc_preference": "immediate"
}

POST/v3/port/batchSubmit a number batch for migration< 200ms

GET/v3/port/batch/{id}Poll batch status and progress< 50ms

POST/v3/port/validatePre-validate numbers before porting< 100ms

DELETE/v3/port/batch/{id}Cancel a pending batch< 150ms

GET/v3/carriersList supported carrier integrations< 30ms

Webhook PayloadReal-time

{
  "event": "batch.completed",
  "batch_id": "BATCH-4472",
  "ported": 5647,
  "failed": 0,
  "duration_ms": 387240,
  "status": "success"
}

Pre-connected Carriers

AT&TT-MobileVerizonSprintMetro PCSBoost MobileCricketUS CellularLumenBandwidth+340 more →

FCC Part 52

SOC 2 Type II

CRTC CLNPC

Ready to port your first number?

Free single-number test port. No credit card. No carrier agreements to sign. Proves speed and reliability in under 10 minutes.

Run a Test Port — Free Download Playbook