AT&T retired its txt.att.net and mms.att.net email-to-SMS gateways on June 17, 2025. If your monitoring stack, on-call rotation, or alerting scripts route text messages through AT&T's email gateway, those alerts have already stopped 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@txt.att.net — no SMS provider, no SDK, no contract. AT&T offered the gateway as a courtesy, never as a contracted service. On June 17, 2025, that gateway went 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 an AT&T gateway address as a contact method. AT&T owns the domain, so there is no customer-side migration path — the addresses simply stopped working on the effective date.
AT&T's shutdown was part of the wider carrier retirement. T-Mobile shut down tmomail.net in December 2024, and Verizon has scheduled vtext.com for March 31, 2027. If you have not already migrated off txt.att.net, those alerts are dark right now.
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 @txt.att.net or @mms.att.net.
You can no longer address an email to a phone number on the AT&T 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 — 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.
AT&T retired its email-to-SMS gateway on June 17, 2025. As of that date, messages sent to number@txt.att.net no longer deliver. There was no grace period — delivery stopped on the effective date.
Yes. AT&T retired both gateways together on the same date — txt.att.net (SMS) and mms.att.net (MMS) both stopped delivering on June 17, 2025. If any of your alerts route to mms.att.net for image or longer-message delivery, they are affected too.
No. AT&T owns the txt.att.net and mms.att.net domains and controls their MX records. With the gateway 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 @txt.att.net or @mms.att.net, 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.
Shutdown dates, official sources, and migration guidance for every major US carrier gateway — T-Mobile, AT&T, and Verizon.
Verizon retires vtext.com and vzwpix.com on March 31, 2027. See what breaks and how to replace it before the 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.