Replace Your Dead Cricket Address in Minutes

Yes. Cricket Wireless shut down its email-to-text and text-to-email services on June 17, 2025, as part of a network-wide shutdown by its parent company, AT&T. You can no longer send or receive text messages through Cricket’s email gateways such as number@sms.cricketwireless.net. If you relied on this for automated alerts, you need a replacement sending path.
Yes. Both directions were retired: email-to-text (sending an email that arrives as an SMS on a Cricket phone) and text-to-email (a text arriving back as an email) stopped working. Because Cricket runs on AT&T’s network, this was not a Cricket-only decision. It was part of AT&T’s broader gateway shutdown, and the same ATT migration path applies to Cricket lines.
What no longer works as of June 17, 2025:
Source: AT&T’s official support notice announcing the end of email-to-text and text-to-email.
The service ended on June 17, 2025. From that date forward, messages sent to Cricket’s SMS/MMS gateways no longer deliver.
The affected gateway address formats were:
+1XXXXXXXXXX@sms.cricketwireless.net (SMS)+1XXXXXXXXXX@mms.cricketwireless.net (MMS)Sending to either address after June 17, 2025 no longer reaches the recipient.
AT&T retired the email-to-text and text-to-email gateway across its entire network for several reasons commonly cited around this class of shutdown:
The result: automated systems that quietly emailed a Cricket or AT&T phone number for years now fail silently unless they are moved to a compliant sending path.
The June 17, 2025 shutdown was network-wide. Beyond Cricket Wireless, it also stopped email-to-text and text-to-email for:
Cricket Wireless and FirstNet are both AT&T-network brands covered under the same shutdown. Trade coverage of the change, including Yahoo Tech’s report, confirmed the discontinuation reached all AT&T Wireless subscribers — FirstNet, Business, and Cricket accounts included.
No — Cricket’s gateways have been fully off since June 17, 2025, and there is no reactivation. If your systems also send to other carriers via email, the status differs by carrier. Dates for other carriers below are drawn from reporting and may change — verify each against the carrier’s own official notice before relying on it.
| Carrier | Gateway | Status | Source |
|---|---|---|---|
| Cricket / AT&T / FirstNet | Cricket: @sms.cricketwireless.net, @mms.cricketwireless.net — AT&T’s own gateway: @txt.att.net | Shut down June 17, 2025 (confirmed by AT&T) | https://www.att.com/support/article/wireless/KM1061254 |
| Verizon | @vtext.com, @vzwpix.com | Reported shutdown in progress; completion reportedly targeted by March 31, 2027 | https://www.verizon.com/support/vtext-vzwpix-shutdown/ |
| T-Mobile | @tmomail.net | Reported active as of last check; no official T-Mobile shutdown date confirmed | https://www.t-mobile.com/support/devices/device-troubleshooting/messaging-and-email-troubleshooting |
Confirm whether your specific sending path has already stopped, and check each carrier’s official page before depending on any gateway. Verizon senders can follow the Verizon migration guide for the address swap.
Teams still routing through tmomail.net should start with the T-Mobile migration.
Anyone who relied on the Cricket gateway — especially for automated alerts — must move to a dedicated messaging app or an SMS API on a compliant A2P route. Common options:
Your Cricket Alerts Can Be Live Again Today
Swap one address in the To: field and your Cricket alerts are live again today.
The migration path off Cricket’s retired gateways is a direct address swap. Any system that could email @sms.cricketwireless.net is already sending an email to reach a phone — so it can be redirected through a drop-in email-to-SMS provider without changing how the system works. The only change is the destination address.
TextBolt is one such drop-in replacement. Every account gets a unique inbound address in the format +1XXXXXXXXXX@sendemailtotext.com. Instead of the dead Cricket domain, format the address as the recipient’s phone number followed by the TextBolt domain:
+1XXXXXXXXXX@sendemailtotext.com
That replaces, one-for-one:
+1XXXXXXXXXX@sms.cricketwireless.net → +1XXXXXXXXXX@sendemailtotext.com+1XXXXXXXXXX@mms.cricketwireless.net → +1XXXXXXXXXX@sendemailtotext.com+1XXXXXXXXXX@txt.att.net (AT&T equivalent) → +1XXXXXXXXXX@sendemailtotext.comSame email-out mechanism, a live delivery path instead of a shut-down one — no new integration, just the new address in the “To:” field. The switch is typically completed in minutes: add the forwarding noreply@ address in the Co-Worker/Alert Module, then replace the To: address with +1XXXXXXXXXX@sendemailtotext.com.
TextBolt is already the migration destination at scale: 261,000+ installations to date on the Google Workspace Marketplace, and 200+ enterprise customers — including FedEx and GE Aerospace — have moved their email-to-text alerting onto the service.
The shutdown hits automated, alert-driven use cases hardest:
Stop Sending Alerts Into a Shut-Down Gateway
Every TextBolt account includes a live inbound email address that works with Gmail, Outlook, or any email client.
It depends on the carrier. Cricket, AT&T, and FirstNet email-to-text stopped working on June 17, 2025, and messages to those gateways now fail silently. Verizon’s gateways (@vtext.com, @vzwpix.com) are reportedly shutting down with completion targeted around March 31, 2027, and T-Mobile’s @tmomail.net was reported active as of last check — verify each against the carrier’s official notice.
No. Cricket Wireless retired both its SMS gateway (@sms.cricketwireless.net) and MMS gateway (@mms.cricketwireless.net) on June 17, 2025, as part of parent company AT&T’s network-wide shutdown. Emails sent to those addresses no longer reach a Cricket handset, and there is no reactivation.
No — Cricket is not ending normal text messaging; it retired only the email-to-text and text-to-email gateway services on June 17, 2025. Regular SMS/MMS between phones still works. What stopped is the ability to reach a Cricket phone by emailing an address like number@sms.cricketwireless.net.
AT&T — including Cricket and FirstNet — ended email-to-text and text-to-email support on June 17, 2025, and Verizon’s gateway shutdown is reportedly in progress with completion targeted by March 31, 2027 (verify against Verizon’s official page). The industry is moving toward registered application-to-person (A2P) messaging over vetted 10DLC, toll-free, and short-code routes that the old free gateways never met. T-Mobile’s gateway was reported active as of last check with no official shutdown date confirmed.
AT&T’s email-to-text gateway is @txt.att.net, which let an email reach a phone as an SMS. This gateway — along with Cricket’s equivalent @sms.cricketwireless.net — was shut down on June 17, 2025, and messages sent to it now fail silently.
Automated systems that quietly emailed a Cricket or AT&T phone number for years now fail silently unless moved to a compliant sending path. Developers can migrate to an SMS API such as Twilio or SignalWire on a 10DLC, toll-free, or short-code A2P route, or use a drop-in email-to-SMS replacement that keeps the existing email-out workflow with no API rewrite.
You need the recipient’s phone number and a live drop-in email-to-SMS provider to replace the dead Cricket domain, since the migration is a one-for-one address swap. With TextBolt, you add the forwarding noreply@ address in your Co-Worker/Alert Module, then reformat the destination as +1XXXXXXXXXX@sendemailtotext.com in the To: field. No new integration is required because your system is already emailing to reach a phone.
An SMS API such as Twilio, SignalWire, or another 10DLC, toll-free, or short-code A2P platform requires developer integration to use. These platforms operate on compliant application-to-person routes, unlike the old free email-to-text gateways.
The fastest path is a one-for-one address swap: replace the dead Cricket domain in your To: field with a live drop-in email-to-SMS address and your alerts are sending again — no API rewrite. With TextBolt, format the destination as +1XXXXXXXXXX@sendemailtotext.com; the switch is typically completed in minutes.
AT&T’s own gateway address (+1XXXXXXXXXX@txt.att.net) is equivalent to Cricket’s and was shut down in the same June 17, 2025 event, so it needs the same fix. Redirect the destination through a drop-in email-to-SMS provider — for example +1XXXXXXXXXX@txt.att.net becomes +1XXXXXXXXXX@sendemailtotext.com — changing only the To: address while keeping the same email-out workflow.
Yes. Any system that could email the old Cricket gateway can be redirected to the new address without changing how it sends. The only change is the destination address in the “To:” field.