+254 722 117 850 Support Login
Why Sozuri Reliability
Why Sozuri · Reliability

The rails that don't drop a message when Friday hits.

Kenyan businesses run their cash flow on the messages we deliver. We treat that like a sacred trust — redundant infrastructure, transparent incident response, an API success rate that matches the carrier's. Black-Friday SMS bursts and end-of-month payroll runs included.

Multi-region redundancy 400 TPS aggregate Postmortems published
API
99.999%
SMS delivery
99.6%
Payments webhook
99.99%
WhatsApp
99.95%
last 90 days
99.999%API success rate, all-time
400 TPSplatform aggregate throughput
< 10mmedian incident response
Publishedpostmortems on every incident
How we stay up

Four habits that compound into trust

Redundant by default

Every critical path runs across multiple cloud regions and direct-peering paths. No single carrier outage takes us with it.

Always watching

Synthetic checks fire against every endpoint every 30 seconds. Carrier deliverability is monitored per network, per hour, with auto-rerouting on drop.

Honest incidents

If something breaks, we say so — on the status page, in the customer dashboard, and via email. Then we publish a postmortem within five business days.

SLAs that match the bill

Enterprise customers can get contractual SLAs with credits keyed to outage minutes. We'd rather pay credits than ship excuses.

How we talk about it

Every incident, every postmortem, on the record

A representative timeline of how an incident moves through Sozuri — from first alert to public postmortem.

T+0 minutes Detected

Synthetic monitor flags carrier dropout

Automated check on Safaricom SMS route notices delivery rate dipped below 95%. On-call engineer paged within 60 seconds.

T+3 minutes Investigating

Status page updated; investigation banner posted

Customers see the issue on status.sozuri.net and inside the dashboard. No-one has to ask whether something's wrong.

T+12 minutes Mitigated

Auto-reroute to backup carrier path triggers

Traffic shifts to the redundant peering link; delivery rate recovers above 98%. Customers see no further impact.

T+90 minutes Resolved

Primary path restored; monitoring confirms steady state

Traffic balanced back across both paths. Resolution notice posted; affected customers contacted individually.

T+5 days Postmortem

Full postmortem published on the blog

What happened, what we learned, what we're changing. Linked from the original status page notice forever.

live · auto-rerouting active
Your move

Build on something that stays up.

Watch the live status page. Read the postmortems. Ask hard questions. We'd rather earn your trust than claim it.

Chat on WhatsApp
Your first SMS in the time it takes to brew coffee. Start building in minutes