SMS Alerts
SMS alerts are downtime and recovery notifications delivered as plain text messages to a mobile number. MonitorUrs sends them through the Vonage/Nexmo SMS API the moment a monitoring check fails, so a critical incident reaches you even when you have no data connection and no monitoring app open.
Last updated: June 2026
Why SMS alerts matter
When a production system goes down, the cost of finding out late is measured in lost revenue and lost trust. App notifications and chat messages are convenient, but they all share one weakness: they need a working data connection and an open, signed-in app to reach you. The moment you are on a patchy mobile network, on a flight that just landed, or simply away from your laptop, those channels can go quiet exactly when you most need them.
A text message does not have that problem. SMS rides on the cellular network rather than your data plan, so it arrives even when mobile data is off, weak, or unavailable, and it does not depend on any app being installed or running. That reliability is exactly why SMS is the channel teams reach for when an alert absolutely cannot be missed. MonitorUrs treats SMS as your last line of defence — the notification that gets through when everything else might not.
Because text messages carry a real cost and command immediate attention, SMS is best reserved for the most critical alerts. Used sparingly, every SMS you receive means something genuinely urgent, which keeps the channel trustworthy instead of noisy.
How SMS alerts work in MonitorUrs
MonitorUrs delivers SMS through the Vonage/Nexmo SMS API. From a fired alert to a text on your phone, the path is straightforward:
- Enable SMS: SMS delivery is handled through the platform's Vonage/Nexmo SMS integration, so there is no gateway for you to run.
- Add a number: you enter the mobile number that should receive alerts on your SMS contact.
- Compose the message: when an alert fires, the alert subject and body are combined into a single text message.
- Queue it: the message is placed on a central outgoing-message queue rather than being sent inline, so a slow gateway never blocks the monitoring engine.
- Process and track: the queue is processed continuously — roughly every 15 seconds — with delivery-state tracking and automatic retry on failure.
- Deliver: the SMS is handed to the Vonage/Nexmo API and lands on your phone as an ordinary text message.
What an SMS alert contains
An SMS is intentionally short and direct. MonitorUrs combines the alert subject and body into the body of the text message, so a single message tells you what happened and where, without requiring you to open anything. A typical alert identifies:
- The affected target — the probe or server the alert relates to.
- The reason — for example a failed check, a server detected offline, or a metric threshold that was crossed.
- The state — whether this is a new incident or a recovery message confirming the issue has cleared.
That is enough to triage from your phone in seconds and decide whether to act immediately or check the full detail in the incident history when you reach a screen.
When alerts fire
SMS alerts are not sent on a timer — they are triggered by the monitoring engines whenever a real condition is met. MonitorUrs raises an SMS alert for:
- Probe failures — once a probe reaches the configured consecutive-failure threshold, so a single transient blip does not page you.
- Server offline detection — when a monitored server stops reporting and is detected as offline.
- Metric threshold rules — when a server metric, such as CPU, memory or disk usage, crosses a threshold rule you defined.
Crucially, recovery is handled too: when the failing condition returns to normal, a recovery message is sent automatically. You get both the warning that something broke and the all-clear that it is fixed, closing the loop without anyone having to remember to follow up.
SMS vs Telegram vs Email
MonitorUrs sends the same alerts across three channels, and each has a natural role. The table below shows where SMS fits relative to the alternatives so you can route notifications sensibly:
| Channel | Needs data / app? | Best for | Detail level |
|---|---|---|---|
| SMS | No — works on the cellular network without data | The most critical, can't-miss incidents | Short — subject and body in one message |
| Telegram | Yes — needs the Telegram app and a connection | Fast team-channel alerting and collaboration | Rich — formatted messages to people or channels |
| Yes — needs a mail client and a connection | Detailed records and non-urgent notifications | Full — long-form detail with retry and bounce handling |
A common pattern is to send everything to Telegram and Email for visibility, then reserve SMS for the severe incidents that justify interrupting whatever you are doing.
Common use cases
- On-call engineers — get paged by text when a production server goes offline at night, without relying on a chat app staying connected.
- E-commerce owners — receive an instant SMS if the checkout flow fails a check, so a revenue-critical outage never goes unnoticed.
- Small teams without a NOC — let the founder or lead developer carry the critical alerts on their phone instead of staffing a monitoring desk.
- Travel and field work — stay reachable for major incidents even with mobile data switched off or roaming disabled.
How it fits your monitoring
SMS is one delivery channel within a single monitoring platform. The checks that decide whether to send an SMS come from your uptime monitoring probes and server rules, and every alert is recorded in your incident history for review afterward. Most teams pair SMS with Telegram alerts for everyday awareness and email alerts for the full paper trail, then lean on SMS as the channel that guarantees the most important incidents reach a human — fast.
Frequently asked questions
What are SMS alerts in MonitorUrs?
SMS alerts are downtime and recovery notifications delivered as text messages to a mobile number. MonitorUrs sends them through the Vonage/Nexmo SMS API the moment a monitoring check fails, so you are notified even when you have no data connection or monitoring app open.
How do I set up SMS alerts in MonitorUrs?
You add the mobile number you want to receive alerts on as an SMS contact in MonitorUrs, and once saved, matching alerts are sent to it automatically through the Vonage/Nexmo SMS API.
What does an SMS alert contain?
Each SMS combines the alert subject and body into a single text message. It identifies the affected probe or server and the reason the alert fired, such as a failed check or a metric threshold being crossed. Recovery messages are sent the same way when the issue clears.
When does MonitorUrs send an SMS alert?
Alerts are triggered by the monitoring engines: a probe failure after the configured consecutive-failure threshold is reached, a server being detected offline, or a server metric threshold rule being crossed. A recovery message is sent automatically when the condition returns to normal.
Are SMS alerts reliable?
SMS messages flow through a central outgoing-message queue that is processed continuously, roughly every 15 seconds, with delivery-state tracking and automatic retry on failure. Because text messages do not depend on a data connection or an open app, SMS is well suited to your most critical, can't-miss alerts.
Should I use SMS for every alert?
SMS is best reserved for the most critical alerts. Many teams route high-volume or informational notifications to Telegram or Email and keep SMS for severe incidents such as a production site going offline, so the text messages they receive always demand attention.