Two real carriers. Very different postures.
Bandwidth is a publicly-traded Tier-1 with Fortune-500 customers and a 12-month MSA as the default. We are a contact-center-focused Tier-1 with published pricing and month-to-month terms. Both own OCNs. Both sign at A-level. On carrier quality, we're a tie. On commercial posture and operational focus, we aim at different teams.
Where we overlap. Where we diverge.
Bandwidth doesn't publish a retail rate card, so the right-column numbers reflect typical contract rates for mid-market customers (10–100M minutes/year). Large-enterprise contract rates go lower. Your Bandwidth bill tells you exactly where you sit on their rate surface.
| VICICarrier | Bandwidth | Δ | |
|---|---|---|---|
| Carrier tier | Tier-1 · owns OCNs, STI-PA chain | Tier-1 · owns OCNs, STI-PA chain | TIED |
| Published rate card | Yes · public, downloadable | No · quote-based, per-customer contract | VC WINS |
| Outbound US/CA per-minute (published vs typical) | $0.0100 · flat published | ~$0.0075–0.0095 · contract-negotiated, varies | TIED |
| DID (local, US/CA) | $5 /mo · published | $0.35–1.00 /mo · contract, volume-tiered | BANDWIDTH WINS |
| Toll-free DID | $10 /mo · published | $2–5 /mo + usage, contract | TIED |
| Contract minimum | None · month-to-month | Typically 12 months + minimum commit ($5k–10k/mo) | VC WINS |
| Time from contact to test trunk | Same day · 15-min provisioning | 2–6 weeks · MSA, procurement, implementation | VC WINS |
| A-level STIR/SHAKEN | Every eligible call, signed under our OCNs | Every eligible call, signed under Bandwidth OCNs | TIED |
| E911 + Ray Baum's Act | Included · dispatchable address via REST | Included · Emergency Address Manager product (more granular) | BANDWIDTH WINS |
| Dispatchable-address enterprise features | REST API · per-DID address | Full enterprise product (locations, mapping, notifications) | BANDWIDTH WINS |
| SMS A2P 10DLC | $0.0065 / segment | Contract-negotiated (typically $0.0055–0.0075) | TIED |
| Custom MSA / procurement theatre | Standard MSA · editable at enterprise scale | Full custom MSA · procurement-tier default | VC WINS |
| Contact-center-specific ops | Hopper pacing · FreeSWITCH-tuned · dialer CDR streams | Generic carrier-grade trunk · BYOC into any softswitch | VC WINS |
| Uptime SLA | 99.99% · 99.998% trailing | 99.99% (contract-specified) | TIED |
| Credit for SLA breach | 10–100% of affected monthly fee | Contract-negotiated (typically capped at 25%) | VC WINS |
| BYOC / bring your own DIDs | Yes | Yes | TIED |
| Brand maturity (Fortune 500 procurement) | 2026 brand launch · established operator team | Public company (NASDAQ: BAND) since 2017 | BANDWIDTH WINS |
| Porting fee | Free · +1 month DID credit per ported number | Typically free per contract | TIED |
How a Bandwidth-to-VICICarrier move actually happens.
01 · Read your existing Bandwidth contract
Bandwidth contracts typically include a 30–60 day notice clause for termination and per-number porting-out processes. Read the MSA and the Statement of Work before you start — the cheapest time to find out about a $5/port exit fee or a 90-day notice is now, not two weeks into the migration.
02 · Request a rate quote against your current traffic
Email [email protected] with your last three months of Bandwidth CDR + DID inventory list. We model our published rate card against your actual traffic volume and return a side-by-side Δ. Bandwidth's contract rates may be lower than ours on a per-minute basis at high volumes — we'll tell you when that's the case. If the switch is purely cost-driven and Bandwidth is cheaper, stay put.
03 · Day-one test trunk on our OCN
Once you sign up we provision a test trunk on the onboarding call — IP-auth, digest, or TLS. Your existing softswitch routes a small fraction of outbound at the new trunk while Bandwidth carries the rest. Run the comparison for 7–14 days before any DID porting.
04 · Port DIDs in batches
US/CA local: 5–7 business days per batch. Toll-free: 4–8 hours. International per market. Bandwidth's porting desk is experienced and FOC-compliant — the losing-carrier side of these ports is usually clean. We handle LOAs, FOC coordination, and failback routing.
05 · Hand back the E911 dispatchable-address workflow
Bandwidth's Emergency Address Manager is a genuinely good product. If your deployment depends on it — distributed contact-center agents, frequent moves, auto-notification to building security — that's an integration rebuild on our side using our per-DID REST address update. Plan for 1–2 engineering days if you're coming from a tight EAM integration.
Three reasons to move. Three reasons to stay.
Move: you want published pricing
Your procurement doesn't need SEC filings. You just want to see the rate card without a three-week contract cycle. We publish ours. Bandwidth doesn't.
Move: dialer-specific operations
Hopper pacing, FreeSWITCH-tuned routing, ViciDial-native CDR streams, campaign-level trunk routing. Bandwidth's trunk is generic carrier-grade. Ours is built for dialers.
Move: month-to-month, no minimum commit
Bandwidth typically defaults to 12-month MSAs with committed monthly spend. We default to month-to-month at any volume. Flexibility has a cost on the per-minute rate at large scale — we're usually 5–15% above a negotiated Bandwidth contract. That's the trade.
Stay: your procurement requires public-company vendors
If your legal team has a hard requirement for SEC-registered, publicly-traded suppliers with analyst coverage, stay. We're a 2026 brand and won't clear that bar for some time.
Stay: E911 Emergency Address Manager is load-bearing
Bandwidth's EAM product is more mature than our per-DID dispatchable-address REST endpoint. If you run distributed contact centers with frequent agent moves and you've integrated EAM into your facilities workflow, the rebuild cost may exceed the pricing gap.
Stay: you clear Bandwidth's volume-tier economics
At 10M+ minutes/month, Bandwidth's contract rate almost certainly beats our published rate on the per-minute line. If cost is the only factor and you're at that volume, stay and negotiate.
The questions buyers comparing the two actually ask.
+Is Bandwidth actually a carrier, or a CPaaS dressed up?
Bandwidth is a real Tier-1 carrier — they own IP infrastructure, have direct BGP peering, run their own E911 PSAP connections, and hold OCNs. They are publicly traded on NASDAQ (BAND) and have been since 2017. On the carrier-posture question, we and Bandwidth are in the same tier. The differences are in commercial posture (public pricing vs contract), customer base (contact centers vs Fortune 500), and product focus (dialer operations vs enterprise E911).
+Why would I pick VICICarrier over Bandwidth?
Three reasons cover most of it. One: you want published pricing without a 3-week procurement cycle. Two: you run a dialer-first operation and you need carrier-side ops (hopper pacing, FreeSWITCH-tuned routing, dialer-specific CDR streams) that Bandwidth's generic trunk doesn't ship. Three: you don't have the volume to clear Bandwidth's minimum commit economics ($5k+/month) and you're paying retail anyway on their standard MSA.
+Why would I pick Bandwidth over VICICarrier?
Also three. One: your procurement team requires a publicly-traded vendor with SEC filings and analyst coverage — we're a 2026-born brand and won't clear that test. Two: your E911 workflow depends on Emergency Address Manager's enterprise features (distributed address management, per-location notifications, Teams/Zoom integrations). Three: you're at a volume where Bandwidth's contract-negotiated rates genuinely beat ours on the per-minute line, which is real at 10M+ minutes/month. None of these reasons are fake.
+Are the A-level attestation policies actually identical?
Close enough to call it a tie. Bandwidth signs at A-attestation on every eligible call under their OCNs; we sign at A-attestation on every eligible call under ours. The STI-PA cert chains land in different CAs (Sectigo on our side, Bandwidth uses Sectigo too as of last update), but downstream carriers treat both cert chains as valid. If your customer base includes carriers running aggressive analytics on sign-chain reputation (some smaller regional carriers do), test both with sample traffic.
+How does porting work between two OCN-owning carriers?
Cleaner than porting from a CPaaS, in our experience. Both sides know the LNP process cold, both honor FOC dates, and the losing-carrier release window is usually at the shorter end of the FCC's 4/10 business day statutory floor. Bandwidth's porting team is well-staffed; we haven't seen the stalling behavior that shows up sometimes with CPaaS-layer vendors. Plan for 5–7 business days per local batch and expect it to complete on the FOC.
+What about the BYOC option — can I use both?
Yes. Some of our larger customers keep Bandwidth trunks for specific use cases (enterprise-E911 deployments, specific terminating-carrier routes where Bandwidth's peering is stronger) and route the bulk of outbound through us. Both trunks live on the same softswitch; the decision is per-call or per-campaign in your routing table. We have customers who've been multi-carrier for two years without consolidating.
We'll price your Bandwidth contract against our card.
Send your last three months of Bandwidth CDR and contract summary. We model your actual traffic against our published deck and return the Δ — including the rows where Bandwidth wins. If cost parity doesn't pencil at your volume, we'll say so.