Verizon is retiring its vtext.com and vzwpix.com email-to-text gateways - the carrier email-to-SMS gateway IT teams have leaned on for years - 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-09-30
For now, yes - but not for long. vtext.com and vzwpix.com - Verizon's email-to-text gateways, also called the Verizon SMS gateway - still deliver as of 2026, but Verizon has scheduled them for shutdown on March 31, 2027. After that date, emails sent to number@vtext.com or number@vzwpix.com will stop being delivered with no bounce or error. Because the two earlier carrier shutdowns already broke cross-carrier delivery, most teams are migrating ahead of the deadline. SigSpan is a drop-in replacement that keeps those alerts delivering without changing how your tools send email.
Status, checked 2026-09-30: vtext.com and vzwpix.com still have live mail servers, and Verizon's notice still gives March 31, 2027. Verizon also warns that some users may lose access before that date.
Someone texted your email address from a Verizon phone. When a Verizon customer sends a picture message, a group text, or a longer message to an email address - or replies to a text that was sent from email - Verizon delivers it as an email from their number, like 5551234567@vzwpix.com. The part before the @ is the sender's 10-digit phone number.
That is the reverse direction of the shutdown. Verizon's notice covers the other way: after March 31, 2027, no one can send texts by emailing number@vtext.com or number@vzwpix.com. If your systems send alerts to either address, that is what stops working - the rest of this page covers what breaks and how to replace it.
For decades, IT teams have routed text 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.
Verizon runs two separate email-to-text gateway domains - one for plain text and one for picture and longer messages. They are different addresses for the same phone number, and Verizon has scheduled both to retire on the same date, March 31, 2027.
Plain text messages, capped at the standard SMS length. This is the address most monitoring tools and scripts use for short alerts and pages.
Address format: 5551234567@vtext.com
Picture messages and text that exceeds the SMS length limit. Used when an alert carries an image or a longer body than a plain SMS can hold.
Address format: 5551234567@vzwpix.com
Both take an email addressed to a 10-digit Verizon number and deliver the body to that phone as a text - until the March 31, 2027 shutdown, after which neither address delivers. If your alerts route to either domain, both paths need to move to a real text-message path before then.
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 text-message path before then - otherwise the alerts simply stop arriving.
After the shutdown the failure is silent - no bounce, no error - so find every reference now, while the addresses still deliver and you can test the replacement side by side. Search for both Verizon gateway domains, vtext.com (SMS) and vzwpix.com (MMS):
# Search common locations for Verizon gateway addresses grep -rInE '@(vtext|vzwpix)\.com' /etc /opt /home /var/spool/cron 2>/dev/null # Check the current user's crontab crontab -l | grep -E '@(vtext|vzwpix)\.com'
Anything you find still delivers today, and stops on March 31, 2027 - or sooner, since Verizon notes some users may lose access before the official date.
If you need a vtext.com replacement - or a Verizon email-to-text alternative before the March 31, 2027 shutdown - there are three honest categories, 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 text 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 text delivery. No SDK, no code changes, no new integrations. Free trial, no card required.
Pay per text: $0.10 for the first 1,000 each month, $0.07 up to 5,000, $0.05 after that. No platform fee.
vtext.com and vzwpix.com are Verizon's email-to-text (email-to-SMS/MMS) gateways - free carrier domains that turn an ordinary email into a text message. You address an email to number@vtext.com for SMS (or number@vzwpix.com for picture and longer MMS messages), and Verizon delivers it to that phone. They still work as of 2026, but Verizon has scheduled both for retirement on March 31, 2027.
Someone texted your email address from a Verizon phone. When a Verizon customer sends a picture message, a group text, or a longer message to an email address - or replies to a text that was sent from email - Verizon delivers it as an email from their 10-digit number at vzwpix.com (for example 5551234567@vzwpix.com). The part before the @ is the sender's phone number. If you don't recognize the number, treat it like any other unexpected email.
Yes, for now. vtext.com and vzwpix.com still deliver as of 2026 - but Verizon has set a fixed retirement date of March 31, 2027, after which messages to number@vtext.com will no longer arrive. In practice, cross-carrier delivery is already unreliable: T-Mobile (December 2024) and AT&T (June 2025) have already shut their gateways down, so a Verizon-gateway alert sent to a T-Mobile or AT&T number may be failing today. Teams that depend on it are migrating ahead of the deadline rather than waiting for it to go dark.
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.
For now, yes. vtext.com and vzwpix.com are the Verizon SMS gateways (the carrier email-to-SMS gateways), and they still deliver as of 2026 - but Verizon has scheduled them for retirement on March 31, 2027. Whether you call it the "Verizon SMS gateway," the "email-to-text gateway," or just "vtext," it is the same service. Because the shutdown date is fixed and the other Big Three carriers have already gone dark, teams that rely on it are migrating before the deadline rather than waiting for messages to stop. SigSpan is a drop-in replacement that preserves your existing email-based workflow.
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.
Verizon is not providing a replacement gateway address, so the closest drop-in is an email-to-text bridge: you keep sending the same alert email, and the bridge delivers it as a text over a registered A2P sender. That preserves your existing setup - no SDK, no code changes - while keeping delivery to Verizon numbers working past the March 31, 2027 shutdown. Direct SMS APIs and full incident-management platforms are also options, but both require more integration than repointing an email address. SigSpan is an email-to-text bridge built for exactly this migration.
These are two different services. This page is about vtext.com and vzwpix.com - Verizon's email-to-text SMS/MMS gateways, scheduled to retire March 31, 2027 - not verizon.net email inboxes, which is a separate consumer email product with its own history. If your question is whether alerts sent to a phone number at @vtext.com will keep working, that is the gateway, and the answer is: only until March 31, 2027.
Shutdown dates, official sources, and migration guidance for every major US carrier gateway - T-Mobile, AT&T, Verizon, and US Cellular.
AT&T already shut down txt.att.net and mms.att.net in June 2025. See what breaks and how to replace it.
T-Mobile retired tmomail.net back in December 2024 - the first of the Big Three to go dark. See what breaks and how to replace it.
Still delivering, but now owned by T-Mobile, which already shut down its own gateway. No retirement date announced.
Pay per text: $0.10 for the first 1,000 each month, $0.07 up to 5,000, $0.05 after that. No platform fee.
See an error or have a more recent source? Email admin@sigspan.com - we update this page as soon as we can verify changes.