Verizon is retiring its vtext.com and vzwpix.com email-to-SMS gateways on March 31, 2027. If your monitoring stack, on-call rotation, or alerting scripts route text messages through Verizon's email gateway, those alerts will stop being delivered — silently. This page explains what breaks, how to audit your exposure, and the honest replacement options.
Last updated: 2026-06-05
For decades, IT teams have routed SMS alerts by emailing 5551234567@vtext.com — no SMS provider, no SDK, no contract. Verizon offered the gateway as a courtesy, never as a contracted service. On March 31, 2027, that gateway goes away.
The teams affected are the ones who built operational messaging around the gateway and largely forgot about it: monitoring stacks paging on-call engineers, cron jobs and runbooks that text via mail or sendmail, and inventory systems that store a Verizon gateway address as a contact method. Verizon owns the domain, so there is no customer-side migration path — the addresses simply stop working on the announced date.
Verizon is the last of the Big Three to retire its gateway. T-Mobile shut down tmomail.net in December 2024, and AT&T retired txt.att.net in June 2025 — so cross-carrier delivery is already broken in practice. March 2027 is the hard deadline for the Verizon path specifically.
A reasonable starting point is to check your environment and any alerting equipment — room-temperature sensors, UPS units, generator monitoring, and similar devices — that has an email address pointing to a phone number at @vtext.com or @vzwpix.com.
After March 31, 2027 you can no longer address an email to a phone number on the Verizon network. Any device, script, or monitoring tool still configured to send to one of those addresses needs its destination updated to a real SMS path before then — otherwise the alerts simply stop arriving.
There are three honest categories of replacement, each with real tradeoffs:
Maximum flexibility, but every piece is yours to build and maintain. Standing up a direct SMS API means writing the email parser, deduplication, rate limiting, on-call routing, opt-out handling, and audit logging yourself — an engineering project, not a configuration change. The right answer only if you have spare engineering capacity and unusual requirements.
Comprehensive on-call platforms with schedules, escalations, and incident timelines. They do far more than replace an SMS gateway — and you pay for all of it. If your only need is to get alert emails delivered as text messages, this is usually overkill, and the pricing reflects the much broader platform you would not be using.
A drop-in replacement that preserves your existing email-based integration pattern. The only change is pointing your alerting mechanism at your unique SigSpan email address — your monitoring tools keep sending email exactly as they do today, and SigSpan handles the parsing and SMS delivery. No code changes, no new integrations, and nothing else in your environment changes, which makes it the lowest-migration-cost option for teams whose only goal is to keep existing alerts flowing.
SigSpan is a drop-in replacement — your monitoring tools keep sending email, SigSpan handles the SMS delivery. No SDK, no code changes, no new integrations. Free trial, no card required.
Verizon has scheduled the retirement of its email-to-SMS gateway for March 31, 2027. After that date, messages sent to number@vtext.com no longer deliver. The domain remains operational until then, but the prior T-Mobile and AT&T shutdowns mean cross-carrier delivery through these addresses is already unreliable in practice.
Yes. Verizon is retiring both gateways together on the same date — vtext.com (SMS) and vzwpix.com (MMS) both stop delivering on March 31, 2027. If any of your alerts route to vzwpix.com for image or longer-message delivery, they are affected too.
No. Verizon owns the vtext.com and vzwpix.com domains and controls their MX records. Once the gateway is retired there is no DNS-level or SMTP-level forwarding option available to customers. The addresses have to be changed at the source — in your monitoring config, your scripts, and your device inventory.
If you send application-to-person SMS through a US long code, yes — A2P 10DLC registration is required by the carriers, not by the SMS provider. Your replacement provider handles the registration mechanics, but you supply brand and campaign details. Registration typically takes days to weeks, so start it before your cutover. Toll-free and short codes follow separate registration processes.
Inventory first: check your monitoring config, scripts, and any alerting equipment — temperature sensors, UPS units, generator monitoring — for addresses pointing at @vtext.com or @vzwpix.com, so you have a complete list of every reference. With a bridge replacement like SigSpan, the migration is a find-and-replace of the destination address rather than a rewrite — your tools keep sending email, so you change only where the alert is addressed, not how it is generated. Validate end-to-end with low-volume test traffic before cutting over production alerts, and stage the change during a planned maintenance window before the March 31, 2027 deadline.
See an error or have a more recent source? Email admin@sigspan.com — we update this page as soon as we can verify changes.