SMS Alerting That Still Works When the Internet Doesn't
Server, network and environmental alarms leave through a 4G modem on a separate path from production. If the internet or the cloud monitoring tool is down, the text still arrives.
What out-of-band means here
The alert path is physically separate from the path it monitors. A monitoring server writes to the SMS gateway, the gateway drives a 4G modem, and the message leaves over the mobile network.
When the office internet fails, the VPN drops or the cloud dashboard is unreachable, that path is unaffected. The failure you are being told about does not also disable the messenger.
This is not a replacement for your monitoring platform. It is the last mile that platform cannot provide when its own network is the thing that broke.
Three trigger paths
Use the one your existing system already speaks.
HTTP webhook
Any script or monitoring tool that can POST to a URL can raise an alert.
SQL table
Write a row from your own job or trigger. The listener polls every few seconds and sends.
Command line
Call the CLI from a batch file, a cron job or a backup script. Exit codes tell you whether the message was queued.
Hardware in the rack
Three practical choices decide whether the alert path survives.
Industrial LTE module
DIN-rail or RS-232 module with an external antenna. More stable than a consumer stick in a metal cabinet.
A dedicated Android phone
Cheap, easy to replace, and works on a shelf near a window. Disable battery optimisation for the gateway app.
Separate power
Put the gateway PC and modem on the UPS, or on a small independent supply so a rack outage does not silence the alert.
Signal and power are the two failure causes we see most. Check the antenna before the software. If you are choosing a device, start with what a GSM modem is; the full feature set is on the desktop software page.
Routing, dedupe and escalation
An alerting system that pages too often gets muted. A few rules keep it useful.
| Rule | Why | How to apply it |
|---|---|---|
| On-call routing | The right person gets the message | Send to a rota number, or post to a Telegram group with per-country topics |
| Duplicate merge | One outage should not produce forty texts | Group by device and message text within a time window before sending |
| Quiet window | Non-critical noise at 03:00 gets the system muted | Split critical and non-critical templates with different windows |
| Escalation | A missed acknowledgement needs a second recipient | Resend to a secondary number after a delay if no reply arrives |
Environmental alarms follow the same pattern: cold chain temperature alerts. For shop-floor stock and checklist messages, see retail SMS.
Capability and limits
Supports
HTTP, SQL and CLI triggers, two-way replies, Telegram forwarding, per-device routing, local logs.
Not supported
No paging SLA, no guaranteed delivery, no monitoring platform replacement, no uplink you do not own.
Depends on
Signal quality, SIM plan, carrier routing and the reliability of the triggering system.
Alerting questions
Does this replace our monitoring system?
No. It replaces the notification step. Keep your monitoring platform and add SMS as a delivery channel that does not depend on the internet.
Can it send when the whole site is offline?
If the PC, modem and SIM have power and signal, yes. Put them on a UPS and use a second carrier SIM if uptime matters.
How fast is an alert?
The gateway queues within seconds. Delivery time is set by the carrier; typical delivery is a few seconds, but congestion can stretch it.
Can we send to a rota of on-call staff?
Yes. Configure a distribution list and change the number when the rota changes, or forward replies to a Telegram group.
Which database can trigger a send?
MySQL, SQL Server and Oracle are supported by the SQL listener. Any system that can insert a row can raise an alert.