BroadNet
The JournalProduct
Product

Two billion SMS in a month — what we learned operating BroadNet at this scale.

We just routed 2,000,000,000 A2P SMS in February 2026. Behind the milestone: hard-earned lessons about deliverability, regulators, and operating the wire.

BroadNet Engineering
AuthorEditorial standards
10 min read
Product · Issue 44
10 min read

n February 2026, BroadNet routed two billion A2P SMS for the first time. The milestone matters less than what it took to get here. Three lessons that might be useful to others operating at scale.

1. Deliverability ≠ throughput

Most operators can sustain high throughput. Few can sustain high deliverability at high throughput. The bottleneck isn't TPS — it's keeping every operator route at 95%+ deliverability while pushing tens of thousands of TPS through it. That requires per-operator monitoring, automatic route rotation on quality degradation, and real-time price/quality optimization. We've built the routing engine specifically around this.

2. Regulators are partners, not obstacles

TDRA, CST, NTRA — when we work with regulators as partners, we get better outcomes than when we treat them as obstacles. Pre-registering sender IDs proactively, sharing fraud intelligence with regulator-facing operators, helping shape new frameworks (we contributed to the GSMA IR.71 v8 revision) — these compound. Regulators-as-partners is a strategic position.

3. The wire is still hard

SS7 didn't go away. Diameter didn't simplify. SMPP 3.4 is still the protocol everyone speaks because no one has solved the protocol-replacement coordination problem. The companies that ship reliable A2P SMS in 2026 are the same ones that did it in 2010 — just better at it. There's no platform that abstracts away the telco stack; there are platforms that operate it really well, and platforms that pretend to.

Was this useful?

How we write and review content

Written by

BroadNet Engineering

Engineering operates the wire: SMPP binds, SS7 stacks, routing engines, the boring infrastructure that makes one-billion-message months possible. They write here when something is worth writing down.

About BroadNetEditorial standardsTalk to the team

Keep reading

Three more from the journal.

See every essay
S
Engineering

SMS throughput and TPS planning: sizing SMPP binds for high-volume campaigns.

SMS TPS is governed by SMPP window size divided by round-trip latency. Here is how to size binds, plan for OTP and campaign bursts, and hit real throughput.

BroadNet Engineering
10m
S
Product

SMPP window size: why your bind is slower than the rate you pay for

An operator agrees 100 messages per second, the bind delivers twelve, and everyone blames the network. Nine times out of ten the cause is a window left at its default. Here is what windowing really does on an SMPP session, and how to size it.

BroadNet Engineering
11m
B
Engineering

Bulk SMS in a crisis: the architecture you need before the emergency.

When a national emergency happens, the messaging layer is the last thing that should be improvised. Here's the bulk-SMS infrastructure pattern that holds up under load — and the regulator-grade audit trail that follows.

BroadNet Engineering
6m
The Journal, by email

One essay a month. Nothing else.

Subscribe and we'll send the next piece — engineering, regulation, or industry — the day it ships. No drip campaigns, no product pitches, no third-party sharing. Unsubscribe in one click.

We send one email a month. Unsubscribe anytime. See our privacy policy.

What you'll get
  • Long-form, not link bait
    Six to eleven minutes of focused writing on a single topic.
  • Written by operators
    Engineers, regulatory leads, and product writing in-house.
  • Region-aware
    MENA-grounded view on regulators, operators, and channel mix.
  • Once a month
    No drip campaign. One essay when there is one to share.
Stop reading. Start shipping.

Most of what we write we learned in production.

If this piece made you nod, we should probably talk. Bring the use case, the volumes, the markets — we'll come back with routing, pricing, and a reference customer you can call.

Talk to the teamRead the API docs
$ curl -X POST https://api.broadnet.me/sms/sendSms