Skip to content
Request rates
Menu
Request a test routeContact on Telegram

DraftThis page is a draft. Values set in grey monospace are placeholders and are not confirmed yet.

Network & Quality

How we route, measure and answer.

What keeps high-volume traffic moving: coverage quoted per destination, route classes defined by outcome, committed TPS per bind, and a named NOC.

Request ratesRequest a test route
NAMED_ROUTING_LEADROUTING_LEAD_TITLEContact on Telegram

Destinations

Coverage, quoted per destination.

We quote coverage destination by destination on your rate deck, with the route class and sender-ID rule for each network. We publish a country count only when we can define and date it.

DIRECT_CONNECTIONS direct connections across COUNTRIES_COVERED countries, as of COVERAGE_DATE, with multiple redundant route sources.

Routing quality

Failover, pinning and route-change notice.

Routes
operator-grade connectivity, with multiple redundant route sources. CONFIRM_BEFORE_PUBLISH
Failover
FAILOVER_POLICY. You can pin a destination to one class if you prefer predictability over failover. CONFIRM_BEFORE_PUBLISH
Route-change notice
if a destination changes class, we tell you within ROUTE_CHANGE_NOTICE.
Sender-ID registration
we tell you which destinations require it before you send. CONFIRM_BEFORE_PUBLISH

Measurement

What we measure, and how.

Delivery rate
Delivered DLRs from the network ÷ messages submitted, per destination and route class, over MEASUREMENT_PERIOD
Latency
Submit to handset, measured on a TelQ-class tester over MEASUREMENT_PERIOD; median (LATENCY_P50) and p95 (LATENCY_P95) per destination and route class
Throughput
Committed TPS per bind under load
Availability
SLA_UPTIME, measured MEASUREMENT_METHOD
Incidents
Count and time to resolve, in your monthly report CONFIRM_BEFORE_PUBLISH

Check our figures on your own tester.

Run your own TelQ test on our routes, or use any independent tester. Test traffic gets no special handling. CONFIRM_BEFORE_PUBLISH

We have no commercial relationship with any testing vendor. CONFIRM_BEFORE_PUBLISH

Connectivity

How your platform connects to ours.

Protocols
SMPP SMPP_VERSIONS and HTTP API
Security
CONNECTIVITY_OPTIONS
Access
IP allow-listing CONFIRM_BEFORE_PUBLISH
Endpoints
BIND_ENDPOINTS bind endpoints for redundancy

Support

How to reach our NOC.

NOC hours, response targets, channels and escalation
HoursNOC_HOURS
P1 (traffic down or degraded on a live route)Response within P1_RESPONSE_TIME
P2 (partial degradation, DLR anomalies)Response within P2_RESPONSE_TIME
Channels
  • Email NOC_EMAIL
  • Telegram TELEGRAM_HANDLE
  • WhatsApp WHATSAPP_NUMBER
  • Teams TEAMS_CONTACT
EscalationNOC_LEAD, then ESCALATION_CONTACT
Status pageSTATUS_URL

Talk to the team.

Ask for rates on the destinations and traffic you send, request a test route, or pick a time to meet.

Request ratesRequest a test route