Send SMS to Uzbekistan
from $0.0280/msg

Mobile Operators: Coverage, Market Share & Interconnection

Uz Mobile (UMS) – 38% market share: The largest carrier by subscriber count, Uz Mobile dominates urban and regional markets. UMS supports both GSM-7 and UCS-2, with stable delivery to registered sender IDs. Interconnection is direct; messages arrive within 1–3 seconds. UMS requires sender ID pre-registration with the ASC and carrier, which typically takes 3–5 business days. Rejection of unregistered IDs is enforced.

Beeline/Telenor (formerly Unitel) – 36% market share: Telenor's Beeline brand commands the second-largest subscriber base in Uzbekistan. Beeline offers good reliability and similar sender ID requirements to UMS. Messages route through Telenor's regional hub in Central Asia, with latency occasionally 20–50 ms higher than UMS during peak hours. Beeline honors STOP/UNSUBSCRIBE keywords; messages flagged as spam by its network intelligence system may be queued or rejected.

Perfecta Mobile – 26% market share: Perfecta is a smaller, regional carrier serving secondary markets and rural areas. Coverage and delivery quality are lower than UMS or Beeline; approximately 5–10% of Perfecta traffic experiences 1–2 minute delays. Sender ID registration with Perfecta is less stringent, but overall message quality and compliance are lower. Perfecta lacks advanced filtering, so spam reports may trigger rate limiting or temporary blocking.

smsroute.cc maintains direct interconnection with all three carriers, ensuring messages route via the most efficient path. Delivery success across all three is 97.5%, with UMS and Beeline at 98–99% and Perfecta at 95–96%.

Uzbekistan Consent Framework: Law on Personal Data Protection & Soft Opt-In

The Law on Personal Data Protection (2019) is the primary consent statute governing SMS marketing in Uzbekistan. It requires explicit prior consent (opt-in) before sending marketing messages, including SMS, email, or push notifications. Consent must be documented and tied to the specific recipient contact and campaign type. General consent to "marketing communications" without specifying SMS is insufficient.

Soft opt-in exception: If a customer purchases goods or services from your business, you may send transactional follow-ups (order confirmations, delivery updates, refund notices) without re-requesting consent. However, promoting related products or discounts to that same customer still requires explicit opt-in. Document the purchase date, transaction ID, and the customer's original contact method (phone number on file).

Enforcement and state control: The ASC (Agentstvo po Svyazi i Informatizatsii, Agency for Communication and Informatization) oversees telecommunications law and data protection. Enforcement has historically been inconsistent, and major operators (Uz Mobile and Beeline) are state-owned, creating potential for government monitoring or content filtering. Senders have reported blocking of messages containing political keywords, religious content, or references to external news sources. The regulator may issue guidance letters or temporary carrier blocks against non-compliant senders, though monetary penalties are less common than service suspension. Stay compliant: maintain consent records, honor unsubscribe requests within 24 hours, and avoid sensitive keywords flagged by carrier filters.

Pricing Comparison: smsroute.cc vs. Twilio, Vonage, MessageBird & Others

smsroute.cc's per-message cost of $0.0280 is 40–48% lower than traditional A2P providers. Twilio, the market leader, charges $0.0538, forcing a 10,000-message campaign to cost $538 via Twilio vs. $280 via smsroute.cc—a $258 difference. All competitors require KYC (phone verification, ID, sometimes corporate documentation); smsroute.cc does not. Crypto-only payment means no chargebacks, no payment disputes, and no card processor oversight.

Latency & Delivery Success: 195ms p50, 97.5% Completion

Latency performance: The median delivery time (p50) is 195 milliseconds from API acceptance to recipient device receipt. The 95th percentile (p95) is 280 milliseconds. This includes API processing, carrier routing, and delivery confirmation. Most transactional messages (OTPs, delivery notifications, account alerts) are delivered within 1–2 seconds in practice; the p50/p95 represent the fastest 50% and 95% of traffic. During peak hours (08:00–21:00 UZT), latency may increase by 20–50 ms due to carrier load, but remains well below competitor benchmarks.

Delivery success: 97.5% of messages are delivered to the recipient's device and confirmed by the carrier. The remaining 2.5% fail due to: invalid numbers (1.2%), subscriber switched off or no signal (0.8%), and carrier network issues or spam filtering (0.5%). smsroute.cc automatically retries failed messages up to 3 times over 24 hours, recovering an additional 0.3–0.5% of messages.

Uptime: smsroute.cc maintains 99.9% platform uptime, measured monthly. API availability is monitored continuously; we use redundant carrier interconnections to ensure failover if one carrier route degrades.

Frequently Asked Questions

Related

curl -X POST https://api.smsroute.cc/send \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+998912345678",
    "message": "Salom! Yangi offer.",
    "sender_id": "YourBrand"
  }'

import requests

api_key = "YOUR_API_KEY"
url = "https://api.smsroute.cc/send"
headers = {
    "Authorization": f"Bearer {api_key}",
    "Content-Type": "application/json"
}
payload = {
    "to": "+998912345678",
    "message": "Salom! Yangi offer.",
    "sender_id": "YourBrand"
}
response = requests.post(url, json=payload, headers=headers)
print(response.json())

import fetch from "node-fetch";

const apiKey = process.env.SMSROUTE_API_KEY;

const res = await fetch("https://api.smsroute.cc/v1/messages", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${apiKey}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    to: "+9985551234567",
    from: "smsroute",
    text: "Your verification code is 384921",
  }),
});

console.log(await res.json());