Key Takeaways
- Open-source GitHub SMS stacks still fail like radios: offline phones, empty prepaid, OEM killers.
- Separate panel/SMSC outages from handset outages before you restart the wrong layer.
- Spare charged devices beat brochure SLAs during incidents.
- Link the OSS hub; do not rewrite the overview here.
- Platform SaaS path meters devices + volume; Free is 1 device / 300 SMS lifetime; airtime is always yours.
Outage on OSS + phones
Incident response for an open-source GitHub Android SMS gateway is mostly radio triage dressed as software ops. Your panel may be up while every handset is asleep. Hub: open source.
“If OTP is down, check device last-seen and prepaid before you rebuild the SMSC container.”
Triage pulse
Panel
Queue
Radio
Severity matrix
| Symptom | Likely layer | First action |
|---|---|---|
| API 5xx / panel down | Self-hosted control plane | Host health, roll back deploy |
| Accepted, never leaves phone | Device / OEM | Wake phone, spare device |
| Pending forever | Carrier / SIM | Airtime, signal, test SMS |
| Duplicate OTP | Client retries | Stop blind POST; idempotency |
Response steps
- Declare severity; name incident lead.
- Freeze non-OTP bulk.
- Fail over to spare charged handset.
- Canary staff OTP before customers.
- Write timeline; fix the root layer.
Comms
Tell stakeholders the radio truth — not “API flaky.” SaaS alternative: maintained gateway.
Cost during incidents
Retries burn airtime. SaaS Free is 1 device / 300 SMS lifetime if you compare paths. Pricing.
Next steps
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





