Uptime Kuma is a self-hosted monitoring platform that tracks websites, TCP ports, DNS records, SSL certificates, Docker containers, ping endpoints, and more. While it supports multiple notification channels, it doesn’t include a native SMS notification provider. Teams that need reliable text message alerts typically rely on external SMS services, adding extra setup and maintenance.
Sending SMS alerts usually means integrating a third-party messaging provider through SMTP, webhooks, or an API. This adds another service to manage, along with separate credentials, billing, and configuration outside your monitoring platform.
Legacy carrier SMS gateways are quick to set up, but many carriers have dropped email-to-SMS support, making them unreliable. Delivery delays, inconsistent routing, and carrier-specific limits make them a poor choice for critical uptime alerts.
API-based SMS providers require additional configuration and maintenance. API keys must be secured, integrations monitored, and notification workflows tested whenever credentials are updated or provider settings change.
If multiple monitors fail or repeated notifications are enabled, responders can quickly receive a flood of text messages. Carefully configuring retry intervals, notification frequency, and escalation rules helps reduce alert fatigue and ensures important incidents stand out.
While Uptime Kuma handles monitoring, SMS delivery depends on the external messaging service you choose. SMTP settings, webhooks, API credentials, and notification integrations all require periodic maintenance to keep alerts flowing reliably.
If you’re already using Uptime Kuma’s built-in Email (SMTP) notifications, TextBolt makes SMS delivery straightforward. Instead of building API integrations or maintaining custom workflows, just route your existing email alerts through TextBolt. Your team gets reliable SMS notifications while keeping the monitoring workflows already in place.
TextBolt connects Uptime Kuma to a registered 10DLC business number using the same Email (SMTP) notification your instance already uses. There is no SMS API to build, no API keys to manage, and no additional monitoring platform to deploy. Simply send Uptime Kuma’s email alerts to your TextBolt gateway address, and they arrive as SMS on your team’s phones.
Every alert Uptime Kuma sends is delivered as an SMS within seconds. Whether it’s a website outage, an unreachable TCP service, a failed ping check, or an SSL certificate nearing expiration, the on-call team is notified immediately so they can respond faster.
TextBolt sends messages through a registered 10DLC business number, helping improve delivery reliability for business messaging. You also get a dedicated business sender identity and message history for auditing and troubleshooting.
When someone replies to an alert by text, TextBolt forwards the response to the original email inbox. Everyone monitoring the shared mailbox can see acknowledgements and updates without switching to another communication platform.
TextBolt works with Uptime Kuma’s built-in Email (SMTP) notification. Configure the notification once, point the To Email field to your TextBolt gateway address, and assign it to your monitors. No plugins, custom scripts, or API integrations are required.
There’s no need to create or maintain a separate SMS API integration, secure API keys, or manage per-user SMS accounts. Your team can deliver SMS alerts without adding another layer of infrastructure to maintain.
TextBolt works at the notification stage, so your Uptime Kuma monitors, retry policies, tags, notification rules, and status pages remain unchanged. You continue using the monitoring configuration you already trust while adding reliable SMS delivery.
Up to 98%
SMS Delivery Rate
Two-Way
SMS Replies to Your Inbox
Carrier-Grade
Routes & Infrastructure
Up to 10
Team Members on Shared Account
The hands-on setup takes around 30 minutes. TextBolt works with Uptime Kuma through its existing Email (SMTP) notification system, so nothing needs to be installed on your Uptime Kuma server and no new notification type is required.
Create your TextBolt account and complete the required business setup. Choose your SMS sending number and complete any required 10DLC registration with The Campaign Registry to ensure reliable business messaging.
TextBolt converts incoming emails into SMS messages using a gateway address connected to your phone number.
Example:
+15551234567@sendemailtotext.com
Replace the phone number with the mobile number that should receive Uptime Kuma alerts.
Open Uptime Kuma and go to Settings → Notifications → Setup Notification. Select Email (SMTP) and enter your SMTP details, including your email provider, username, password, and sending address.
In the To Email field, enter your TextBolt gateway address. When Uptime Kuma sends an email alert, TextBolt receives it and converts the notification into an SMS message.
Open the monitors that need SMS notifications and enable your TextBolt notification. Use SMS alerts for critical services while keeping lower-priority alerts on email or other notification channels.
Trigger a test outage or use a test monitor to verify SMS delivery. Adjust retry intervals, resend settings, and message content to prevent unnecessary alerts while ensuring important incidents reach your team.

Ready to Get Uptime Kuma Alerts by SMS?
Connect Uptime Kuma with TextBolt in minutes and make sure critical downtime alerts reach your team wherever they are.
Connect Uptime Kuma directly with SMS providers like Twilio or ClickSend to send alerts through an API connection. This method provides reliable delivery and works well for teams already using SMS platforms. However, it requires managing provider accounts, API credentials, and message costs alongside your monitoring setup.
Use Uptime Kuma’s built-in Email (SMTP) notifications to send alerts through TextBolt’s Email-to-SMS Gateway. Simply route monitoring emails to your TextBolt gateway address, and downtime or recovery alerts are converted into SMS messages. This approach avoids API setup, plugins, and custom scripts while keeping your existing Uptime Kuma workflow unchanged.
Connect Uptime Kuma alerts to custom tools, automation platforms, or self-hosted SMS systems using webhooks. This method provides more flexibility for advanced workflows but requires additional configuration and maintenance. It is best suited for teams with existing automation infrastructure that need complete control over how alerts are processed and delivered.
Five common monitor categories where a text to the on-call person replaces a Twilio API key, a per-seat plugin, or a retired carrier gateway. Every one uses the same Email (SMTP) notification. TextBolt is built for operational alerts to your own staff, not for customer marketing.
You get a text when an HTTP or HTTPS monitor goes down, returns the wrong status code, or fails a keyword check. A marketing site, an internal app, or a client’s storefront dropping offline at 2 AM reaches the on-call phone in seconds.
Uptime Kuma’s TCP Port monitors text you when a service stops answering on its port, whether that is a database, a message broker, an SSH daemon, or a game server. The same notification covers every one of them.
Ping monitors text the on-call person when a host, switch, router, or VM stops responding to ICMP. A bare-metal box or a network device falling off the map reaches the phone before anyone opens a laptop.
DNS monitors text you when a record changes or resolution fails, and Uptime Kuma’s certificate expiry warnings text you before an SSL certificate lapses. Certificate expiry is the strongest case for SMS, since the failure is scheduled and completely preventable.
Uptime Kuma’s Docker container and database monitors text you when a container stops, a health check fails, or a database becomes unreachable. One TextBolt account covers the whole self-hosted stack.

10DLC Compliant
Carrier Approved
Complete Audit Trail
There are three common ways to send SMS alerts from Uptime Kuma. You can connect a native SMS provider, use an Email-to-SMS solution like TextBolt, or integrate with a full incident response platform. The right choice depends on how much setup, maintenance, and alert management your team needs.
Direct SMS delivery through an API connection
Uptime Kuma supports integrations with several SMS providers, allowing alerts to be sent directly through an SMS API. Teams can connect services like Twilio or ClickSend, configure their provider credentials, and send monitoring alerts through the connected messaging platform.
This approach works well for organizations that already use an SMS provider and need direct control over messaging infrastructure.
Recommended
Convert existing Uptime Kuma email alerts into SMS
TextBolt works with Uptime Kuma’s built-in Email (SMTP) notification system. Instead of creating an API integration, simply route Uptime Kuma alerts to your TextBolt gateway address, and TextBolt converts those notifications into SMS messages.
Your existing monitors, alert rules, and notification settings stay unchanged. TextBolt adds the SMS delivery layer without requiring plugins, custom scripts, or additional monitoring software.
Full alert management beyond SMS
Incident response platforms combine SMS notifications with advanced features such as on-call schedules, escalation rules, incident tracking, and team workflows. They are designed for organizations that need a complete incident management process rather than SMS delivery alone.
These platforms are a strong fit for larger teams with structured escalation procedures, but they may add additional cost and complexity when the main goal is simply receiving Uptime Kuma alerts by text.
CUSTOMER REVIEWS
Three teams share how TextBolt helped them turn Uptime Kuma notifications into reliable SMS alerts without custom integrations, API maintenance, or another incident management platform.

On Google Workspace Marketplace, with
263K+ installs
We already had Uptime Kuma monitoring our infrastructure, but email alerts were easy to miss during after-hours incidents. TextBolt gave our on-call team a faster way to see critical issues and respond before they impacted users.

Infrastructure Manager
SaaS Operations Team
We wanted SMS alerts from Uptime Kuma without adding another complicated system to maintain. TextBolt worked with the email notifications we already had configured and gave our team a simple alerting workflow.

DevOps Lead
Software Company
Our team manages multiple services, and knowing about downtime quickly is critical. TextBolt helped us deliver Uptime Kuma alerts directly to the people responsible for resolving issues without building custom SMS integrations.

IT Operations Manager
Managed Services Provider
The benefits that matter when adding SMS alerts to your Uptime Kuma monitoring workflow.
Up to 98%
SMS Delivery Rate
30 min
End-to-End Setup
Up to 10
Team Members on Standard Plan
4.4★
Workspace Marketplace (483+ reviews)
You add an Email (SMTP) notification under Settings > Notifications, set the To Email to a TextBolt gateway address like +15551234567@sendemailtotext.com, and assign the notification to your monitors. Setup takes about 30 minutes. Set retries and a resend threshold on each monitor before the first outage.
No Twilio account is needed with an email-to-SMS gateway. Uptime Kuma’s Twilio notification requires a Twilio account, a number, and an API key in your config, while TextBolt uses the Email (SMTP) notification Uptime Kuma already supports. You point the To Email at a gateway address and skip the provider entirely.
The gateway address goes in the To Email field of an Email (SMTP) notification, under Settings > Notifications. Uptime Kuma sends the alert email to that address and TextBolt converts it into a text. You then assign that notification to each monitor that should text you.
Carrier gateways are being retired and should not be used for new Uptime Kuma alerting. AT&T and T-Mobile have already shut theirs down, and Verizon ends vtext.com service on March 31, 2027. A notification pointed at a retired gateway fails silently, so the alerts stop without any error in Uptime Kuma.
Yes, and the reply arrives as an email in the sending mailbox. Anyone watching that alert inbox sees the acknowledgement. The reply does not change the monitor state inside Uptime Kuma, which still updates from its own checks.
Any monitor that fires a notification can become a text, including HTTP and HTTPS, keyword, TCP port, ping, DNS, SSL certificate expiry, Docker, and database monitors. If the monitor sends the Email (SMTP) notification, TextBolt delivers it as SMS.
TextBolt delivers to United States and Canada numbers only. Every gateway address uses the +1 country code. Teams with on-call people outside North America need a different gateway for those numbers.
TextBolt replaces the SMS delivery part, not the scheduling part. It sends texts from your existing Email (SMTP) notification without per-user licensing. If you need on-call rotations, escalation chains, and phone calls, an incident platform still does more.
Yes, as long as the instance can reach an outbound SMTP service to send the notification email. A fully air-gapped host with no outbound email cannot use TextBolt and needs a local GSM modem or a hardware SMS gateway instead.
Text the On-Call Person Without Wiring In an API Key
Add SMS to your Uptime Kuma monitors in about 30 minutes. Point one Email (SMTP) notification at a gateway address and your monitors, retries, and status pages keep working exactly as configured.