Key Takeaways
- gateway server how to incident response for outage is a control-plane runbook: TLS, reverse proxy, pairing last-seen — then the SIM.
- Most “server outages” are Doze or empty airtime. Check the phone before rebuilding nginx.
- API-worker IR and Android-app IR are sibling runbooks. Do not mix pages.
- We do not refund operator minutes burned while you debug TLS.
- Priced by devices and SMS send volume. You use your own phone and operator SMS credit. A spare still meters as a device.
- This is not a penetration guide. NIST SP 800-61 is roles and comms only.
Server plane vs radio plane
Search intent for android sms gateway server how to incident response for outage is what you do when the hosted or proxied control plane looks dead. Service pricing is based on device count and total SMS sent through the gateway. Hub: Android SMS gateway server. API worker IR: API incident response. Handset IR: Android incident response.
If last-seen is six hours old, you do not have a reverse-proxy incident. You have a phone in a drawer.
NIST incident handling is a floor for roles and comms (SP 800-61). This page does not teach exploits, bypasses, or payload crafting.
Detect: TLS, last-seen, queue
Split “cannot POST” from “accepted but never sent.” Watch pairing last-seen, queue depth, webhook message.failed. Webhooks setup. Docs: docs.sms-gateway.app.
| Plane | Symptom | First move |
|---|---|---|
| TLS / reverse proxy | Clients 502/timeout; phones still last-seen fresh | Cert, upstream, clock — defensive checks only |
| Android radio | Last-seen stale; queue grows | Power, Doze, pairing, SIM, spare |
| Your workers | Duplicate OTP after 502s | Idempotency-Key; stop the retry loop |
| Operator | One SIM fails; others deliver | Balance, AUP, destination canary |
Contain without a retry storm
Pause bulk. Pin OTP with deviceIds to a charged spare. Failover troubleshooting. Idempotency-Key on the auth event so 502 retries do not mint two codes.
Reverse proxy is not the SMSC
TLS termination and upstream health are ops hygiene — not radio physics. Reverse proxy and HTTPS. Do not “open the firewall” as a substitute for a paired phone.
What you tell customers
Honest: delayed OTP, not “unlimited cloud SMS is down.” Priced by devices and SMS send volume. You use your own phone and operator SMS credit. We do not cash out unused operator airtime.
Server IR checklist
- Name the plane: TLS vs radio vs worker vs operator.
- Pause campaigns; pin OTP to a spare.
- Stop client retry storms (Idempotency-Key).
- Staff canary after recovery — not a customer blast.
- Write the timeline; do not skip the phone check.
Next steps
Recover, then prove on a cold SIM. Pricing. Setup.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- SMS API documentationLive endpoint reference
- device and SMS volume pricingPlans and allowances
- Android SMS gateway product guideDefinition, product, and how to buy
- download the Android gateway appGet the APK
