Every CPaaS homepage says some version of "direct carrier connections" or "our own network." Those phrases describe genuinely different ownership models, and the difference matters: a message or call that stalls one hop from the handset costs you a failed OTP or a dropped call, and how many resold hops sit between your API call and that handset depends on what a vendor actually operates. This guide gives you a neutral framework for reading a network claim, then lists what six vendors — including Orbit — publicly state about their own infrastructure, each sourced to the vendor's own materials.
Why "owns the network" isn't one thing
"Network ownership" in CPaaS spans a spectrum, not a binary:
- Facilities-based carrier status. A small number of providers hold an actual carrier license — in the US, status as a Competitive Local Exchange Carrier (CLEC) filed with the FCC — meaning they operate switching infrastructure as a regulated telecom carrier, not just a software layer on top of one.
- A privately-owned IP backbone with direct interconnects. A provider can own its points of presence (PoPs) and the private fiber/MPLS links between them, then interconnect that private backbone directly with mobile operators — without holding carrier status itself.
- A wholesale switch with direct operator interconnects. A provider can operate its own switching platform and negotiate direct SS7/SIP interconnects with hundreds of mobile network operators, often built up through acquiring smaller regional aggregators over time.
- A "super network" of many carrier connections. A provider can maintain thousands of carrier relationships and heavily engineer routing/failover across them, without describing itself as a facilities-based carrier.
None of these is inherently "better" in the abstract — a well-run aggregation layer with deep redundancy can outperform a poorly-run owned network. But the ownership model changes who controls the route when something breaks, and it is the single most under-documented fact in CPaaS vendor comparisons.
How to verify a vendor's network claim yourself
Before taking any "we own the network" marketing line at face value, ask for:
- Facilities-based status. In the US, a CLEC is registered with state public utility commissions and the FCC — ask whether the vendor (or its underlying carrier) holds that status, and in which countries it holds equivalent operator/regulatory status.
- Direct interconnect count, by region. "4,800 carrier connections" and "800 direct operator connections" are not the same claim — ask which of the vendor's connections are direct-to-operator versus routed through a sub-aggregator, and get the number broken out for the specific countries you send to.
- What happens on a failed route. Ask for the vendor's own failover/redundancy design (average route depth, automatic re-routing) rather than a headline uptime number.
- The registration path. For US messaging, ask whether 10DLC / toll-free verification is handled through the vendor's own direct carrier relationship or passed through a third party — an extra hop here often mirrors the network's ownership model.
What six vendors publicly state about their own network
The table below is drawn entirely from each vendor's own published materials — not third-party claims about them — so you can verify every line yourself.
| Provider | What it publicly states about its network | Model | Source |
|---|---|---|---|
| Bandwidth | Operates a nationwide, facilities-based Competitive Local Exchange Carrier (CLEC) network across 48 US states, plus a software-integrated voice network reaching 60+ countries | Licensed carrier (facilities-based) | bandwidth.com/company |
| Telnyx | Operates a privately-owned, global, multi-cloud IP network with direct carrier interconnects and private fiber between its points of presence | Owned private IP network | telnyx.com/our-network |
| Sinch | States it owns and operates a Tier-1 voice "Super Network" with direct connections to major US carriers, plus a global messaging "Super Network" with 600+ direct-to-carrier connections | Owned wholesale switch (built via acquisition + direct interconnects) | sinch.com/global-super-network |
| Infobip | States its platform reaches 190+ countries through 800+ direct operator connections | Direct-connect aggregation | infobip.com/sms/international |
| Twilio | States its "Super Network" maintains 4,800+ global carrier connections across 180+ countries, with an average route depth of four carriers per destination | Carrier interconnection (super-network aggregation) | twilio.com/super-network |
| Orbit by Devotel | States that outbound (MT) voice and SMS terminate over Devotel's own wholesale softswitch, connecting directly to 500+ global carriers, rather than a resold aggregator hop | Owned wholesale softswitch | Orbit CPaaS overview |
Read each row as what the vendor states about itself, not an independent audit — the point of the checklist above is that you can put the same four questions to any provider on this list, including Orbit, and compare the answers directly.
Why this is hard to find a neutral answer to
Every vendor is naturally the best-documented, most favorable source on its own network — which is exactly why an independent, neutral comparison is rare. Analyst reports (Gartner, Omdia) evaluate CPaaS vendors on breadth of features and market execution, not network ownership specifically, and vendor "vs." pages are, by design, not neutral. This page exists to collect the vendors' own public claims about their own network model in one place, sourced, so you can go verify the specific ones that matter for your traffic.
Orbit's angle: an owned switch, not a claimed one
Orbit doesn't operate its own mobile network or hold carrier licenses in every market it serves. What Orbit does state, and what you can verify the same way as any row above: outbound voice and SMS traffic terminates over Devotel's own wholesale softswitch, with direct interconnects to 500+ carriers, rather than being resold through a third-party aggregator layer. That single switch carries every outbound channel — AI voice agents, the cloud phone system, and outbound SMS — on the same account and the same bill. See the CPaaS overview, the AI voice agents platform, and current per-minute and per-message rates on the pricing page.
Frequently asked questions
Does "direct carrier connections" mean a CPaaS provider owns a network?
Not necessarily. A provider can hold thousands of direct SS7/SIP interconnects with mobile operators — a genuine engineering achievement — without holding carrier status itself or owning the physical switching fabric. Facilities-based carrier status (like a US CLEC filing) is a stronger, independently verifiable claim than a connection count alone.
Is Bandwidth the only CPaaS provider with FCC carrier status?
Bandwidth publicly describes itself as operating a nationwide, facilities-based CLEC network across 48 US states — a claim you can verify against FCC/state public utility commission filings. Other vendors describe owned IP backbones or direct operator interconnects (see the table above), which are different claims worth verifying on their own terms.
Why does network ownership matter for OTP and 2FA delivery?
Every resold hop between a vendor's platform and the destination handset is another link that can add latency, drop a message, or apply its own rate limits — which shows up directly as failed one-time-passcode deliveries. Asking for a vendor's direct-interconnect percentage for your specific destination countries is a more useful diagnostic than a global connection count.
How does Orbit's network model compare to a reseller?
Orbit's outbound voice and SMS route over Devotel's own wholesale softswitch with direct carrier interconnects, rather than through a resold aggregator layer, and that same switch serves every outbound channel on one account. See Orbit vs Twilio for a direct head-to-head.
Where can I read more about how CPaaS network layers work generally?
See What is CPaaS for how the orchestration, carrier-interconnect, and compliance layers fit together underneath any provider's API.
Sources and further reading
- Bandwidth — Company overview: Bandwidth's own description of its facilities-based CLEC network.
- Telnyx — Our Network: Telnyx's own description of its private global IP network.
- Sinch — Global Super Network: Sinch's own description of its messaging network model.
- Infobip — International SMS: Infobip's own stated direct operator connection count.
- Twilio — Super Network: Twilio's own description of its carrier interconnection model.
Published 26 July 2026. Part of the Orbit resources library — foundational guides for teams building on communications infrastructure.