Replication breaks silently, and replicas keep serving stale data to users while every dashboard looks fine. TextBolt is an email to SMS service that turns your replication monitoring alerts into text messages for DBAs, SREs, data platform engineers, and on-call engineers. Whether the alert comes from Datadog DBM, AWS RDS CloudWatch, Percona PMM, or Prometheus, it reaches the right phone as a text instantly.
Up to 98%
Delivery Rate
~30 min
Setup Time
Up to 10
Team Members (Multi-User Access)
Challenges
DBAs, SREs, and data platform engineers hit the same problems on any stack. Small issues turn into big outages fast. Here are the reasons replication alerts often arrive too late to help.
A replica can look completely healthy and still be wrong. The dashboard shows green and queries run fine, but the replica is behind and serving old data. Nobody notices until a customer complains.
Lag tends to spike right when a system is already stressed, during traffic surges, deploys, or outages. A few seconds of delay can grow into minutes, and engineers end up firefighting with stale data.
When a tool like Debezium or Kafka Connect stops reading, its replication slot stays open. Postgres keeps every WAL file that slot might need. Left alone, that slot fills the disk, and writes stop entirely.
A transaction run only on a replica, or a stalled schema change, can make it inconsistent with no error. The SQL thread stops, and it may be unsafe to promote by the time anyone checks.
Failover only works if replication is healthy, which often goes unchecked. A degraded primary can fail to trigger failover, or an early failover can cause split-brain. Teams usually learn this during a real incident.
DBAs spend much of their week firefighting instead of planned work. Alert fatigue is real, so most alerts get tuned out, even the ones that matter. A missed 2 AM alert costs sleep and money, the same pattern behind most IT alert systems failing at the worst possible time.
Solution
TextBolt sits between your replication monitoring tools and your team’s phones, so the DBAs, SREs, and engineers who need to know are the ones who find out first. Keep the stack you already use, Datadog DBM, Percona PMM, pganalyze, AWS RDS, Azure SQL, MongoDB Atlas, Patroni, or Prometheus. Here are the reasons teams switch to TextBolt for replication alerts.
When a replica falls behind, a slot fills up, or a failover isn’t ready, you get a text within 10 to 30 seconds of the alert firing. It reaches your phone directly, not a Slack channel muted for the night or an inbox nobody checks until morning. No app to open, no laptop needed, just a text you can act on right away.
Datadog DBM, New Relic, SolarWinds DPA, Percona PMM, pganalyze, AWS RDS, Aurora CloudWatch, Azure SQL, Google Cloud SQL, MongoDB Atlas, Prometheus, Snowflake, Zabbix, Nagios, Patroni, repmgr, MySQL Orchestrator, Severalnines, AWS DMS, Debezium, and Kafka Connect.
A single alert can reach the on-call DBA, the SRE, the data platform engineer, and the team lead at the same time, so nobody’s waiting on someone else to forward it. Up to 10 people can be added on Standard and Professional plans, at no extra cost per person.
TextBolt never touches your database or your replicas. Setting it up means adding one email address to an alert rule you already have, whether that’s in Datadog, AWS RDS, Patroni, or Prometheus. No software to install, no credentials to hand over, nothing new to maintain.
Every text is logged with the time, the recipient, and the full details from the original alert, exactly as your monitoring tool sent them. That record is there if you ever need to walk back through what happened during an incident or a near-miss.
Getting Started
Setting up replication monitoring alerts takes about 30 minutes, covering account creation, number selection, business verification, and connecting your monitoring tool. Nothing to install, no agent to deploy, and no database credentials shared with TextBolt. Have your business name, EIN, website, and team phone numbers ready before you start.
Create your account and add the DBAs, SREs, data platform engineers, and on-call engineers who should get replication alerts. Account creation takes 2 to 3 minutes, and you can add more team members later as your monitoring coverage grows.
TextBolt issues a dedicated business toll-free number and a matching gateway address, in the format +1[phone]@sendemailtotext.com . Use this same address across every monitoring tool, HA tool, and CDC pipeline alert rule you plan to connect.
Submit your legal business name, EIN, business website, and contact details so SMS sends from a 10DLC-compliant, carrier-trusted sender rather than a flagged short code. Forms take 15 to 20 minutes, and carrier approval typically lands within 24 to 48 hours.
Add +1[phone]@sendemailtotext.com as the email recipient on your lag, slot-bloat, SQL-thread-stopped, or GTID-drift rule, whether that lives in Datadog DBM, an AWS RDS SNS topic, Azure SQL geo-replication, Percona PMM, pganalyze, a Patroni callback, a Snowflake alert or task, or Prometheus Alertmanager.
Set thresholds so only meaningful events trigger SMS, such as replica lag above 5 seconds for OLTP or 60 seconds for analytics, retained WAL above 1 GB, or a stopped SQL thread. Force a test event and confirm the SMS arrives within 10 to 30 seconds.
Add +1[phone]@sendemailtotext.com recipients for anyone else who should know, the secondary on-call DBA, the SRE watching read-path SLOs, the data platform engineer running CDC, or the engineering team lead. Most monitoring tools accept a comma-separated list or one recipient per row.
Process
Pick the method that fits your setup, whether your monitoring tool can email directly, your platform locks down outbound alerts, or you just need to send one by hand.
Your tool detects a lag spike, slot bloat, broken SQL thread, GTID drift, or unsafe failover state, whether that’s Datadog DBM, AWS RDS, Azure SQL, MongoDB Atlas, Patroni, MySQL Orchestrator, or Prometheus. Point the alert email at +15551234567@sendemailtotext.com, and every alert becomes an SMS automatically.
If your platform can only route alerts to a fixed inbox or a Slack-only setup, add a forwarding rule there instead, in Office 365, Google Workspace, or your engineering mail server. Alerts land, forward to TextBolt, and convert to SMS with no platform changes needed.
For smaller teams or one-off escalations, compose a replication alert from any email client, Gmail, Outlook, Apple Mail, or Thunderbird, and address it to +15551234567@sendemailtotext.com. Useful for a team lead paging a manager when a planned cutover needs a post-failover handoff.
Use Cases
Whatever you run, PostgreSQL streaming replication, multi-region fintech databases, or a CDC pipeline, TextBolt routes replication alerts to the DBAs, SREs, and engineers who can act on them fast.
Teams running PostgreSQL with streaming replication and Patroni HA get lag-spike and slot-bloat SMS the instant pg_stat_replication or pganalyze breaches threshold. DBAs and on-call SREs reach the cluster before backend developers see stale-read tickets pile up.
Compliance-driven teams running multi-region PostgreSQL or SQL Server Always On route lag-SLA breaches, GTID drift, and failover-readiness alerts to the on-call DBA and engineering team lead. The audit trail documents reach-time for SLA records and post-incident reviews.
Catalog and checkout reads serve from replicas to handle traffic. DBAs and backend developers get SMS the instant lag spikes during a sale or an Aurora replica falls behind, so team leads can shed traffic to the primary before conversions drop.
Teams running Debezium, Kafka Connect, AWS DMS, Fivetran, Airbyte, or Striim on Postgres logical slots or MySQL binlog get SMS the instant a connector stops reading or a slot retains too much WAL, before the primary disk fills.
Managed database providers route per-tenant replication alerts from RDS, Aurora, Cloud SQL, Azure SQL, or MongoDB Atlas to the DBA on duty for that customer, so tenant-specific lag or slot-bloat events get fixed before support escalates.
Founder-led teams running a single PostgreSQL primary with one or two replicas use RDS Event Notifications via SNS to email, and TextBolt converts that to SMS, so the founder catches overnight breakage before users see stale data.
Comparison
TextBolt is not a replication monitoring tool and is not a full on-call platform. It sits between the two and handles reliable SMS delivery for replication alerts, replacing per-tool SMS gateways and shutdown carrier gateways.
Free or per-message billed, plus chat-throttled
Each tool handles alerts its own way, and coverage is inconsistent. Datadog and RDS can send SMS, Percona PMM only reaches Slack, and pganalyze has no SMS option at all. Some tools still rely on shutdown carrier gateways.
Recommended
Flat monthly plan, no per-node license
One gateway address works with every tool you already use, and turns each alert into a text that reaches your whole team. Nothing in your stack gets replaced, a capability gets added.
$21-79 per user per month
A full on-call platform with schedules and escalation steps, built for teams managing incidents at scale. Often more than you need if replication alerts are all you’re after.
Benefits
Reliable SMS delivery, multi-engineer fan-out, and flat pricing that doesn’t penalize you per DBA seat.
Up to 98%
Delivery Rate
~30 min
End-to-End Setup
Up to 10
Team Members (Standard Plan)
10-30 sec
Alert Arrival Time
Got questions? We’ve got answers.
Yes, essentially always. The tool only needs to send an email when a replication signal fires (lag breach, slot bloat, SQL thread stopped, GTID drift, unsafe failover, CDC connector failure), which every modern replication monitoring or HA tool can do (Datadog DBM, pganalyze, Percona PMM, AWS RDS + Aurora CloudWatch, Azure SQL geo-replication, MongoDB Atlas, Patroni, MySQL Orchestrator, AWS DMS, Debezium, Prometheus + postgres_exporter / mysqld_exporter). If you can trigger a test event and get an email, you can turn it into an SMS.
Replication monitoring covers replication-specific signals: lag spikes, slot bloat, GTID drift, errant transactions, unsafe failover readiness, and stale-read risk. Database-failure alerts cover DB-engine unavailability. Database-performance alerts cover slow queries. System- and application-downtime alerts cover host or app unavailability. Disk-usage alerts cover OS-level disk fill. Same audience overlap, different signals. Many teams configure several through the same TextBolt gateway with separate audit trails.
TextBolt is not a replication monitoring tool, not an on-call platform like PagerDuty, and not an SMS API like Twilio. Keep your detection stack (Datadog DBM, pganalyze, RDS CloudWatch, Patroni, Prometheus). TextBolt adds reliable SMS delivery: your tool’s email becomes an SMS at up to 98% from a 10DLC-compliant business number. Unlike RDS SNS SMS, TextBolt has no AWS region restrictions and routes alerts from AWS, Azure, and GCP into the same DBA inbox.
No. TextBolt does not connect to your primary or replicas, does not require DB credentials, and does not query pg_stat_replication or SHOW SLAVE STATUS. Your monitoring tool detects the signal and emails the TextBolt gateway; TextBolt only sees the email subject and body. No credentials shared, no extra attack surface.
No. TextBolt is an SMS delivery layer, not a detection tool. Configure lag thresholds, max_slot_wal_keep_size, GTID-set inconsistency rules, oplog window thresholds, and SQL-thread-stopped detection in your monitoring tool. TextBolt then delivers those tuned alerts as SMS so DBAs get woken up only for real replication breaches.
Configure separate alert rules. Lag-spike alerts (Datadog DBM, RDS CloudWatch ReplicaLag, postgres_exporter pg_replication_lag) route to the SRE plus on-call DBA. Slot-bloat alerts (pg_replication_slots, Debezium connector lag, max_slot_wal_keep_size breach) route to the data platform engineer plus DBA. GTID-drift alerts (MySQL Orchestrator, Severalnines drift report) route to the DBA plus engineering team lead. Each rule sends to a different gateway recipient for triage clarity.
Yes. A single alert fans out in parallel to the on-call DBA, SRE, data platform engineer, platform engineer, and engineering team lead.
Yes. AWS RDS Event Notifications (replica failure, ReplicaLag breach, replica promotion) route via SNS-to-email to one TextBolt recipient (typically the platform engineer). Patroni callback events route to another (typically the DBA). Debezium / Kafka Connect failures route to the data platform engineer. Each rule sends to a different gateway recipient with separate audit trails.
SMS reaches phones directly while chat platforms throttle. When a replica falls behind during a traffic surge and cascades into hundreds of lag-breach alerts in minutes, Slack throttles webhook posts and the alerts you most need to see go silent. TextBolt SMS hits the engineer phone with system-level priority regardless of chat-channel state.
It is silently failing. T-Mobile’s @tmomail.net shut down in late 2024, AT&T’s @txt.att.net shut down on June 17, 2025, and Verizon’s @vtext.com is phasing down through March 2027. Many DBAs piped Nagios check_postgres or Zabbix replication templates to those gateways for years and the SMS path broke unnoticed. Replace the recipient with +15551234567@sendemailtotext.com. Same phone, different domain, registered carrier-trusted business sender.
Yes. Set up a Snowflake alert or task to email you when replication lag or failover status crosses a threshold, then point that email at your TextBolt gateway address to get it as a text.
No. Your replication monitoring tool sends an email, the engineer’s phone receives a text. Phone numbers sit in the TextBolt account configuration and are not published to anyone outside the account. Audit trail entries record sender, recipient, and delivery status without exposing personal details to third parties.

Database failure text alerts to DBAs and SREs from Datadog, AWS RDS, Percona PMM, Patroni, Prometheus. Connection pool, failover, and deadlock alerts.

Performance monitoring text alerts to SREs and developers from Datadog APM, New Relic, Dynatrace, Honeycomb. P99 spikes and SLO burn rate, no code needed.

Get incident alerts via text. Notify your on-call team instantly from any monitoring tool (Grafana, Datadog, Nagios). Up to 98% delivery, no code needed.