What is an OCN?
An Operating Company Number (OCN) is a 4-character identifier assigned to each telecommunications carrier by NECA (National Exchange Carrier Association). It uniquely identifies the company that provides service for a phone number.
While carrier names can vary in formatting ("Verizon Wireless", "Verizon", "VZW"), the OCN is consistent and reliable for programmatic decisions.
OCN Format
OCNs follow a specific pattern:
- 4 characters — Always exactly 4 characters
- Alphanumeric — Letters and/or numbers
- Unique per carrier — Each OCN maps to one company
Example OCNs
| OCN | Carrier | Type |
|---|---|---|
| 6006 | Verizon Wireless | Wireless |
| 6529 | T-Mobile | Wireless |
| 6664 | AT&T Mobility | Wireless |
| 7018 | AT&T | Landline |
| 9208 | Bandwidth.com | VoIP |
| 7850 | Twilio | VoIP |
Why Use OCN?
Reliable Carrier Identification
Carrier names vary in how they're reported:
- "Verizon Wireless" vs "Verizon" vs "Cellco Partnership"
- "AT&T Mobility" vs "Cingular" vs "AT&T Wireless"
The OCN is always consistent, making it ideal for:
- Routing logic and switch statements
- Billing and rate calculations
- Analytics and reporting
- Carrier-specific handling
Get OCN with every lookup. Reliable carrier identification for any number.
Get Free API KeyUsing OCN in API Responses
curl -X POST https://api-service.verirouteintel.io/api/v1/lrn \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"phone_number": "15551234567"}'
# Response
{
"data": {
"phone_number": "15551234567",
"lrn": "5551230000",
"carrier": "Verizon Wireless"
},
"success": true
}
Implementation Example
# Route based on OCN for reliable carrier matching
CARRIER_ROUTES = {
"6006": "verizon_direct", # Verizon Wireless
"6529": "tmobile_direct", # T-Mobile
"6664": "att_direct", # AT&T Mobility
}
VoIP_OCNs = {"9208", "7850", "8825", "6718"} # Bandwidth, Twilio, etc.
def get_route(phone_lookup):
ocn = phone_lookup['lrn']['ocn']
# Check for direct carrier routes
if ocn in CARRIER_ROUTES:
return CARRIER_ROUTES[ocn]
# Check for VoIP (may need special handling)
if ocn in VOIP_OCNS:
return "voip_route"
# Default route
return "general_route"
OCN vs. SPID
You may also encounter SPID (Service Provider ID):
| Identifier | Purpose | Length |
|---|---|---|
| OCN | General carrier identification | 4 characters |
| SPID | Number portability operations | 4 characters |
In practice, OCN and SPID often refer to the same carrier. VeriRoute Intel returns the OCN for consistent carrier identification.
Maintaining OCN Lists
If you're building routing logic based on OCN, consider:
- Start with major carriers — Top 10 OCNs cover most traffic
- Group by carrier type — Wireless, landline, VoIP
- Update periodically — New carriers emerge, mergers happen
- Have a default route — Handle unknown OCNs gracefully
Frequently Asked Questions
What does OCN stand for?
OCN stands for Operating Company Number. It's a 4-character identifier assigned by NECA (National Exchange Carrier Association) to uniquely identify each telecommunications carrier in the United States.
Why use OCN instead of carrier name?
Carrier names vary in formatting across different data sources ("Verizon Wireless" vs "Verizon" vs "Cellco"). The OCN is always consistent, making it reliable for programmatic carrier identification, routing decisions, and analytics.
Where can I find a list of OCNs?
NECA maintains the official OCN registry. VeriRoute Intel returns the OCN with every LRN lookup, so you can build your carrier list organically from your actual traffic. Major wireless carriers (Verizon, AT&T, T-Mobile) cover most consumer numbers.