Verizon SMS Gateway Address: vtext.com and vzwpix.com in 2026

For engineers maintaining alert systems pointed at vtext.com. The addresses, the status, and the one-line replacement.

Verizon’s SMS gateways still partially work in 2026, but the consumer-era email-to-text path is ending. AT&T’s gateway shut down in June 2025, T-Mobile’s silently stopped delivering in late 2024, and Verizon has set a hard sunset of March 31, 2027. This page lists the literal addresses, the carrier-by-carrier status, and the one-line config change that keeps alert systems firing afterward.

TL;DR

• SMS: <10-digit-number>@vtext.com
• MMS: <10-digit-number>@vzwpix.com
• Status: Phasing out, full Verizon sunset March 31, 2027. AT&T’s txt.att.net shut down June 17, 2025. T-Mobile’s tmomail.net quietly stopped in late 2024.
• Drop-in replacement: +1<phone>@sendemailtotext.com. One-line config change, your alert system stays the same.

The Exact Verizon SMS Gateway Addresses

For reference, here are every form Verizon ever published:

The active format most scripts and apps still use is 1234567890@vtext.com. Note: no plus sign, no country code, no dashes, just the 10 digits and the domain. This format predates E.164 and is one reason the gateways behave inconsistently with non-US numbers.

Why vtext.com Became Unreliable

Three things changed between 2022 and 2025 that broke the old carrier-gateway model:

1. 10DLC enforcement landed. The carriers (Verizon, AT&T, T-Mobile) and The Campaign Registry built a new framework for business SMS. Senders now have to register their business identity to get reliable delivery to US mobile numbers. Email-to-SMS gateways were originally designed for consumer use, friend texts your phone from a desktop, not for application-driven alerts. They sit outside the 10DLC framework and the carriers stopped maintaining them.

2. AT&T pulled the plug first. On June 17, 2025, txt.att.net stopped accepting messages entirely. No grace period. Many companies discovered the outage when their on-call paging system went silent during a midnight incident. AT&T’s announcement was three lines on a support page.

3. T-Mobile silently stopped delivering. Around November–December 2024, T-Mobile’s tmomail.net started failing without bouncing, messages got accepted by the gateway, then dropped on the way to the handset. There was no announcement, no formal sunset date. Engineers found out by paging themselves and watching their phones not buzz.

Verizon is the last of the three majors still partially operating its gateway. Their announced wind-down completes by March 31, 2027, but the experience has already degraded: longer delays, certain originating domains rejected, and unpredictable bouncing during peak hours.

The Three US Carrier Gateways at a Glance

The pattern is clear: the consumer-era carrier gateways are over. Plan for the post-gateway world.

The Drop-In Replacement:  <phone>@sendemailtotext.com

The simplest way to replace a vtext.com integration is to swap the destination address. Everything else in your system, the alert template, the trigger logic, the recipient phone number, stays exactly as it is.

Before:

recipient: 2065551234@vtext.com
subject:   Server-Prod-3 CPU 94%
body:      Threshold exceeded on Server-Prod-3 for 8 min.

After:

recipient: +12065551234@sendemailtotext.com
subject:   Server-Prod-3 CPU 94%
body:      Threshold exceeded on Server-Prod-3 for 8 min.

That’s the full migration. One line of config. Three differences:

1. The domain is sendemailtotext.com instead of vtext.com.
2. The phone number is prefixed with +1 (E.164 format).
3. The recipient’s carrier no longer matters, delivery works to Verizon, AT&T, T-Mobile, regional carriers, and Canadian carriers the same way.

  [Your application]                                  [Phone]
        │                                                ▲
        ▼                                                │
  ┌──────────────┐    ┌──────────────────┐    ┌─────────────────┐
  │ Email alert  │ →  │ sendemailtotext  │ →  │  Registered     │
  │ (SMTP, your  │    │  inbound gateway │    │  10DLC delivery │
  │  existing    │    │  + 10DLC sender  │    │  to US/Canada   │
  │  rule)       │    │  on TextBolt     │    │  mobile carrier │
  └──────────────┘    └──────────────────┘    └─────────────────┘

Underneath, TextBolt registers your business as a legitimate sender through The Campaign Registry. The form takes about 10 minutes to fill out during signup; carrier review of the 10DLC registration typically takes 1 to 2 business days. Once approved, every text that hits the recipient’s phone goes through the carrier-trusted 10DLC pipeline, not the deprecated consumer-gateway path that broke.

If you’re moving off vtext.com or vzwpix.com specifically, the Verizon vText to TextBolt migration page is the canonical product reference for the swap.

Why This Matters for Alerts Specifically

The biggest users of email-to-SMS gateways were never people texting each other. They were systems sending alerts. We see this every day at TextBolt, customers migrating from vtext.com are almost always doing one of these:

• IT monitoring, Datadog, PagerDuty, UptimeRobot, Nagios, Zabbix, Prometheus Alertmanager, Sensu, New Relic, AWS CloudWatch SNS-to-email forwarders
• Building / facility alarms, Honeywell, ADT, DSC, Tyco, SimpliSafe Pro, Bosch, Notifier panels with SMTP modules
• Industrial / SCADA, WIN-911, Ignition, Wonderware, ClearSCADA, Rockwell FactoryTalk
• Broadcast monitoring, Inovonics 610/611/635, Burk ARC Plus, Broadcast Tools SSM-1, Davicom DV-Mini, Nautel NX transmitters
• VoIP / PBX voicemail-to-email, RingCentral, 8×8, Nextiva, Vonage, Zoom Phone, Allworx, 3CX
• Healthcare appointment reminders, Practice Management software (Athenahealth, Epic MyChart-adjacent), Mindbody, SimplePractice
• CRM / marketing automation triggers, HubSpot workflows, Zapier, Make, n8n, custom webhooks
• Server scripts / cron jobs, bash mail/sendmail/msmtp, Python smtplib, Node nodemailer, PowerShell Send-MailMessage

For all of these, the migration is the same: change the destination from a carrier gateway to <phone>@sendemailtotext.com. The source system doesn’t need new software, new credentials, or a new integration. It already speaks SMTP, that’s how it was talking to vtext.com in the first place.

How Quickly Does It Actually Work?

The honest answer: typing speed, plus carrier delivery time.

Customers who were sending billions of alert emails to vtext.com for years move over in an afternoon. The longest part is filling out the 10DLC registration, and even that is shorter than the email you sent to the AT&T support team in June 2025 asking what happened to txt.att.net.

What Happens if You Do Nothing?

If you have a production alert system pointed at vtext.com today, here is the realistic timeline:

• Now through Q4 2026, increasing intermittent failures. A monitoring email that triggered an SMS yesterday silently doesn’t trigger one tomorrow. Customers tell us “it worked fine until last Tuesday.” This is the carrier wind-down in progress.
• By March 31, 2027, Verizon’s announced full sunset. Hard cutover.
• For MMS via vzwpix.com, already worse than SMS. Image attachments get stripped at random.

The risk for engineering teams is not the planned 2027 date; it’s the unplanned silent failure between now and then. Off-hours pagers don’t fire. Alarm-panel notifications don’t arrive. The fault is hard to debug because the email “sent successfully” from the source system’s point of view, it just never became a text on the other end.

A 10DLC-registered alternative removes the silent-failure mode entirely. Either the text gets delivered (95–98% of the time, per industry-typical delivery on registered 10DLC senders), or you get a clear bounce telling you why.

Step-by-Step: Replacing vtext.com in 15 Minutes

If you have a typical alert system in mind, say, a Datadog monitor or a PagerDuty escalation step, here’s the literal migration:

1. Sign up. Visit my.textbolt.com/signup. Email + phone. Free 7-day trial, 10 test credits, credit card required at signup to prevent spam accounts.
2. Complete the business verification. Five-step wizard, about ten minutes. You’ll need your legal business name, EIN (US) or BN (Canada), and a representative email address. See our 10DLC compliance overview for the why.
3. Send a test text. From whatever email account, address an email to +1<your-cell>@sendemailtotext.com. Subject is optional. Body is the message. It should arrive on your phone within a few seconds.
4. Update your alert system’s destination. Wherever you have  <phone>@vtext.com (or tmomail.net, txt.att.net), replace with +1<phone>@sendemailtotext.com. Save.
5. Trigger a test alert. Force the underlying condition that fires the alert (or use your monitoring system’s “test rule” button). Confirm the SMS arrives.
6. Document the change. Tell your team. Update the runbook. Note that the recipient’s carrier no longer matters.

That’s it. Total elapsed time: 15 minutes plus the 1–2 business day carrier review window for the 10DLC registration.

TextBolt Plans and Pricing

One credit = one SMS segment (160 GSM-7 characters, or 70 Unicode characters). A typical 80-character monitoring alert is one credit. Most teams running off vtext.com send fewer than 500 alerts per month, so the Basic tier ($29) covers them comfortably. Pay-as-you-go top-up packs are available for spike months.

See the full TextBolt pricing plans for annual discounts and Enterprise tiers.

A Word on Toll-Free vs Shared Numbers

By default, TextBolt sends from a shared toll-free number, a pool of carrier-registered numbers managed for SMB customers. For most alerting use cases, this is exactly what you want: instant delivery, no per-number setup.

If your recipients need to see a consistent business number, for two-way conversations, for trust, or for compliance, a dedicated toll-free number is available as an add-on at $45 / year. Same registration, same delivery, your number on every send. See /account/addons after signup.

What About the WebSMS / Verizon Wireless Web Tool?

A frequent secondary question: “Can’t I just use Verizon’s web-based SMS tool to send a text from my computer?”

That tool (messages.vzw.com and earlier messages.verizonwireless.com) is for Verizon Wireless customers texting from their browser instead of their phone. It’s a consumer feature tied to a specific Verizon line. It cannot be used as an alerting API, it has rate limits, and it cannot send to non-Verizon recipients reliably.

If you need to send SMS programmatically, from a server, an app, an alert rule, you need an actual SMS provider that’s registered with the carriers. That’s the whole point of 10DLC and the post-vtext.com world.

How TextBolt Is Different From the Carrier Gateways It Replaces

Start Your Migration

Setup is the same regardless of which carrier gateway you’re leaving:

• Moving from vtext.com or vzwpix.com: swap your alert system’s destination to +1<phone>@sendemailtotext.com after your 10DLC registration clears.
• Comparing options: Our Top 5 Verizon vText alternatives breakdown compares the main paid replacements on price, delivery, and 10DLC support.
• Coming from AT&T’s txt.att.net: The gateway is fully off since June 17, 2025, so this is the most urgent move. See the AT&T email to text migration page, or email support@textbolt.com for a hand-held migration call.
• Coming from T-Mobile’s tmomail.net: Texts stop arriving without bouncing, so test first. See the T-Mobile email to text migration page for the address swap.
• Ready to start: Create your TextBolt account and use the 7-day trial with 10 test credits to verify delivery before touching production.

If you have a specific alarm panel, monitor, PBX, or automation tool you want help wiring up, email support@textbolt.com with what you’re using. We’ve migrated customers off vtext.com who were running everything from a Bash script cron-ing once a minute to enterprise SCADA stacks with ten years of alert history. The destination address swap is the same in every case.

Migrate Before the Silent Failures Hit

The Verizon SMS gateway address (vtext.com and vzwpix.com) had a 20-year run as the default way for systems to text their humans. That era is over. Verizon’s announced full sunset is March 31, 2027, and AT&T’s and T-Mobile’s gateways are already gone.

The replacement is the same shape, an email-to-SMS gateway, but built on the 10DLC framework that the carriers actually support. The configuration change is one line. The benefit is that it keeps working past 2027.

Migrate before the silent failures find you in production.

Start your migration with TextBolt