If your server alerts, cron job notifications, or on-call pages stopped arriving as text messages sometime in late 2024, you already know something broke. You just might not know what.
Verizon quietly started shutting down its @vtext.com email-to-SMS gateway, the free service that let any system capable of sending email also send a text message. For more than a decade, IT teams pointed Nagios, Zabbix, Grafana, PRTG, and dozens of homegrown scripts at addresses like [email protected] and relied on Verizon to convert that email into an SMS. No API keys. No monthly bill. No code beyond a one-line SMTP call.
That’s over. And Verizon wasn’t alone. AT&T killed @txt.att.net on June 17, 2025; T-Mobile’s @tmomail.net silently stopped delivering in late 2024; and the entire carrier email-to-SMS ecosystem is gone. Verizon’s full shutdown is scheduled for March 31, 2027, but delivery is already unreliable enough that waiting is a risk most ops teams can’t afford.
This article covers what happened, why carriers killed these gateways, and what IT teams have migrated to, without ripping out their monitoring stack.
What VText Actually Was (And Why IT Teams Loved It)
VText was Verizon’s email-to-SMS gateway. You’d send an email to a 10-digit phone number at @vtext.com, and Verizon’s infrastructure converted it into an SMS delivered to that Verizon subscriber’s phone. The MMS variant used @vzwpix.com for picture messages.
The appeal for IT teams was the zero-friction setup. Any system that could send email monitoring platforms, backup scripts, CI/CD pipelines, EHR systems, and SCADA controllers could send SMS alerts without touching an API. The “integration” was literally one email address in a config file.
Every major carrier offered the same thing. AT&T had @txt.att.net. T-Mobile had @tmomail.net. Sprint had @messaging.sprintpcs.com. For IT teams running 24/7 operations, these gateways were the invisible glue between infrastructure monitoring and the on-call engineer’s pocket.
Why Every Carrier Killed Email-to-SMS
The gateways died for five interconnected reasons, and understanding them matters because it explains why no carrier is bringing the service back.
Spam and smishing abuse scaled out of control. Anyone on the internet could email any phone number at @vtext.com with no sender verification. Attackers exploited this to send phishing SMS at massive scale. Verizon’s own filtering (outsourced to Cloudfilter/Proofpoint) started aggressively blocking messages in response, which killed legitimate alerts alongside the spam.
No sender authentication existed. Modern business messaging requires 10DLC registration; carriers need to know who is sending, what they’re sending, and that recipients opted in. The legacy gateways predated all of this. There was no way to bolt authentication onto a system designed in the early 2000s.
Delivery became unpredictable. As carriers tightened spam filters, legitimate IT alerts started failing silently. No bounce message. No error code. The monitoring tool showed “email sent successfully” while the on-call engineer’s phone stayed quiet. Healthcare IT teams reported delivery success rates dropping to roughly 33% before they migrated off.
Carrier infrastructure costs climbed. Maintaining a free, unauthenticated relay that primarily attracted abuse wasn’t economically viable. Carriers chose to retire the service rather than invest in upgrading it.
The industry moved to regulated A2P messaging. The CTIA and major carriers now require businesses to register their sending numbers through 10DLC (10-Digit Long Code) campaigns. This framework is incompatible with the anonymous, unauthenticated nature of the old email gateways.
The bottom line: the gateways weren’t deprecated because of a business decision. They were deprecated because the architecture was fundamentally broken for modern use.
The Shutdown Timeline IT Teams Need to Know
Here’s the carrier-by-carrier status as of mid-2026:
T-Mobile (@tmomail.net): Silently stopped delivering in late 2024. No official announcement. DNS resolution for the gateway became intermittent, then failed entirely. If you’re still pointing systems at @tmomail.net, your messages are not arriving.
AT&T (@txt.att.net, @mms.att.net): Officially discontinued June 17, 2025. AT&T updated their support page with a brief notice: “Say goodbye to email-to-text and text-to-email.” No migration guide. No recommended alternatives. Cricket Wireless and FirstNet subscribers were also affected as AT&T subsidiaries.
Verizon (@vtext.com, @vzwpix.com): Phase-out began in late 2024. Full shutdown scheduled for March 31, 2027. Delivery is already degraded; messages are filtered, delayed, or silently dropped. Verizon is steering enterprise customers toward EMAG (Enterprise Messaging Access Gateway), a paid service designed for large organizations with dedicated IT resources and carrier contract budgets. EMAG is not a practical replacement for most IT teams.
Sprint (@messaging.sprintpcs.com): Died with the T-Mobile merger. Non-functional since early 2022.
If your alerting still works on any of these gateways, consider it borrowed time.
Who Got Hit the Hardest
The shutdown didn’t affect everyone equally. The teams that relied on carrier gateways the most were the ones with the least resources to build API-based alternatives.
IT operations and SRE teams. Server-down alerts, disk-space warnings, SSL certificate expirations, backup failures, all routed through email-to-SMS as a last-resort escalation channel. When the gateway died, the on-call engineer stopped getting paged.
Healthcare IT: EHR systems, lab result notifications, appointment reminders, and emergency codes are often routed through @vtext.com or @txt.att.net. One healthcare IT team reported their on-call rotation was effectively blind for three days before they realized the gateway had failed.
Broadcast engineering. Off-air alerts for TV and radio stations frequently used email-to-SMS. When a transmitter goes down at 2 AM, the engineer needs a text, not an email sitting in a spam folder.
Small businesses. Auto shops, dental offices, salons, and tutors used carrier gateways for appointment reminders, often configured by a tech-savvy friend and never touched again. These systems failed silently with no one monitoring them.
Manufacturing and SCADA. Industrial control systems and environmental monitoring equipment (temperature sensors, pressure gauges, flow meters) frequently used SMTP-based alerting. Many of these systems can send email but cannot run modern SMS APIs.
What IT Teams Migrated To
The replacement landscape splits into three categories, and the right choice depends on your use case, volume, and technical resources.
Option 1: Modern Email-to-SMS Gateways
This is the closest drop-in replacement for the old carrier gateways. You send an email to [email protected], and the provider converts it to SMS via 10DLC-registered carrier routes. Replies thread back to your email inbox.
The key advantage: zero code changes. If your monitoring tool, ERP system, or script sends email today, it can send SMS tomorrow. You change one email address in the config; the old @vtext.com address is swapped for the new provider’s domain.
For teams evaluating this approach, several alternatives to Verizon VText now offer 10DLC-compliant routing, delivery confirmation, and two-way reply threading that the old carrier gateways never had.
Modern email-to-SMS providers differ from the old carrier gateways in important ways: Sender verification prevents abuse, 10DLC registration ensures carrier trust, delivery receipts confirm message arrival, and per-message analytics let you debug failures instead of guessing.
Option 2: Full SMS APIs (Twilio, Plivo, Vonage)
If you have developers on staff and need programmatic control, message templates, conditional routing, webhook callbacks, and multi-channel orchestration, a CPaaS (Communications Platform as a Service) like Twilio is the standard choice.
The trade-off: setup complexity. You need API keys, a Twilio account, 10DLC registration, a sending number, and a code to handle the API calls. For a team that just wants “server down → text to phone,” this is overkill.
Twilio’s pricing model (per-message fees plus carrier surcharges plus number rental) can also surprise teams used to a free gateway. Monthly costs for a mid-volume alerting setup typically run between $50 and $150 after all surcharges.
Option 3: Dedicated Alerting Platforms (PagerDuty, Opsgenie, OnPage)
For mature SRE teams, incident management platforms handle the full escalation lifecycle, not just SMS delivery but also on-call schedules, escalation policies, incident timelines, and post-mortems.
These are the right choice when your alerting needs have outgrown “send a text when something breaks.” But they come with significant monthly costs ($20–50 per user), onboarding overhead, and a learning curve that doesn’t make sense for a 5-person IT shop that just needs its Nagios alerts to reach phones.
How to Choose: A Decision Framework
The simplest way to pick:
Choose email-to-SMS if your systems already send email alerts and you want SMS delivery without code changes, new software, or per-user licensing. This covers most IT teams, healthcare orgs, broadcast engineers, and small businesses.
Choose a full SMS API if you’re building SMS into a product, need programmatic message composition, or send more than 10,000 messages per month with complex routing logic.
Choose an incident management platform if you have a formal on-call rotation with escalation policies, and SMS is just one channel alongside voice calls, push notifications, and Slack integration.
For the vast majority of teams that lost their @vtext.com workflows, the first option, a modern email-to-SMS gateway, is the path of least resistance. One config change, same workflow, better delivery.
Migration Checklist
If you’re ready to move off the dead carrier gateways, here’s the practical sequence:
1. Audit every system sending to @vtext.com, @txt.att.net, or @tmomail.net. Search email server logs, monitoring tool configs, cron jobs, EHR notification settings, and any scripts in /etc/ or /opt/. The addresses are often buried in config files that haven’t been touched in years.
2. Pick a replacement provider. Compare pricing, 10DLC compliance, delivery reporting, and whether they support two-way replies. If you need help comparing, published reviews cover the major options side by side.
3. Sign up and verify your business. 10DLC registration typically takes 24–48 hours. The provider handles the carrier registration, you supply your business name, EIN, and a description of your messaging use case.
4. Swap the addresses. Replace every instance of @vtext.com (or @txt.att.net, @tmomail.net) with the new provider’s domain. This is literally a find-and-replace in most systems.
5. Test before cutover. Send test alerts to 3–5 phone numbers across different carriers (Verizon, AT&T, and T-Mobile) and confirm delivery within 30 seconds.
6. Monitor for a week. Check delivery logs daily for the first week. Flag any failures and resolve before they become silent gaps in your alerting.
The entire migration typically takes a single afternoon for small teams or a coordinated week for enterprises with dozens of systems pointing at old gateway addresses.
The Bigger Picture
The death of carrier email-to-SMS gateways isn’t an isolated event. It’s part of a broader shift toward regulated, authenticated business messaging. The free, anonymous relay was a product of a different era, before smishing was a billion-dollar problem, before 10DLC existed, and before carriers decided that message authentication was non-negotiable.
For IT teams, the practical takeaway is straightforward: the old way is gone, it’s not coming back, and the replacements are better. Delivery rates on 10DLC-registered routes consistently exceed 95%, compared to the sub-50% rates many teams experienced on the dying carrier gateways. You get delivery confirmation instead of silent failures. You get audit trails instead of black boxes.
The hardest part isn’t the migration itself; it’s finding every system that was quietly sending to @vtext.com in the background, waiting to fail at the worst possible moment.
Start the audit today. The shutdown isn’t coming. For most teams, it already happened.
