Did Cricket Wireless Email-to-Text Shut Down? Yes, on June 17, 2025

HomeBlogCricket Wireless Email to Text Shutdown
Did Cricket Wireless Email-to-Text Shut Down

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.

Did Cricket Email-to-Text Shut Down?

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:

  • Email → SMS dead: Emails sent to @sms.cricketwireless.net no longer reach a Cricket handset.
  • SMS → email dead: Texts a Cricket subscriber sends toward a former gateway no longer arrive back as email.
  • Gateways blocked: Both the SMS and MMS gateway domains are retired and messages fail silently — the decision was made by AT&T, Cricket’s parent company.

Source: AT&T’s official support notice announcing the end of email-to-text and text-to-email.

When Did Cricket Email-to-Text Stop Working?

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.

Why Did Cricket / AT&T Shut Down Email-to-Text?

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:

  • Spam and abuse: Open email-to-SMS gateways are an easy vector for unauthenticated spam and abuse, with no sender verification.
  • A2P 10DLC compliance: The industry has moved toward registered application-to-person (A2P) messaging over vetted 10DLC, toll-free, and short-code routes — a standard the old free gateways never met.
  • Low usage relative to risk: The legacy gateway carried comparatively little legitimate volume against the abuse and support burden it created.

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.

Who Else Was Affected by the AT&T Shutdown?

The June 17, 2025 shutdown was network-wide. Beyond Cricket Wireless, it also stopped email-to-text and text-to-email for:

  • AT&T Wireless subscribers
  • FirstNet accounts
  • AT&T Business accounts

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.

Does Cricket Email-to-Text Still Work in 2025 or 2026? (Cross-Carrier Status)

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.

CarrierGatewayStatusSource
Cricket / AT&T / FirstNetCricket: @sms.cricketwireless.net, @mms.cricketwireless.net — AT&T’s own gateway: @txt.att.netShut down June 17, 2025 (confirmed by AT&T)https://www.att.com/support/article/wireless/KM1061254
Verizon@vtext.com, @vzwpix.comReported shutdown in progress; completion reportedly targeted by March 31, 2027https://www.verizon.com/support/vtext-vzwpix-shutdown/
T-Mobile@tmomail.netReported active as of last check; no official T-Mobile shutdown date confirmedhttps://www.t-mobile.com/support/devices/device-troubleshooting/messaging-and-email-troubleshooting

How Do I Tell If My Sending Path Has Already Stopped?

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.

What Are the Alternatives to Cricket Email-to-Text?

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:

  • Dedicated mobile messaging apps for person-to-person messaging.
  • SMS APIs such as Twilio, SignalWire, and other 10DLC, toll-free, or short-code A2P platforms for automated, high-volume sending. These require developer integration.
  • A drop-in email-to-SMS replacement that keeps your existing email-out workflow — no API rewrite. This is the closest match to the old gateway for anyone who just wants to swap a dead address for a live one.

Your Cricket Alerts Can Be Live Again Today

Swap one address in the To: field and your Cricket alerts are live again today.

How Do I Migrate Off @sms.cricketwireless.net?

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.com

Same 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.

Who Relied on Cricket Email-to-Text — and Now Needs a Fix?

The shutdown hits automated, alert-driven use cases hardest:

  • IT departments & system adminstrators — Server-down alerts, security breach notifications, backup confirmations, network outage alerts. From Reddit’s r/sysadmin: “My division heavily relies on this email-to-text feature for automated critical notifications from our Windows servers.” (source)
  • Educational institutions — School-closure notifications, emergency alerts, parent notifications, campus event updates. Princeton University: “Members of the Princeton community typically use this service to receive automated alerts from technology systems.” (source)
  • Healthcare providers — Appointment reminders, lab result notifications, refill alerts, and follow-up care messages, where reliable delivery of automated notifications matters most. Automated text reminders have been shown to reduce patient no-shows in multiple studies.

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.

Frequently Asked Questions

Does email to text still work?

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.

Does Cricket allow email to text?

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.

Is Cricket doing away with text messages?

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.

 Are wireless providers going to stop sending emails to SMS messages?

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.

 What is AT&T’s email-to-text gateway?

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.

 How does this change affect developers and applications?

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.

 What information do I need before migrating off the Cricket gateway?

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.

 What are the prerequisites for an SMS API instead of email-to-text?

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.

 What is the fastest way to get my broken Cricket alerts working again?

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.

 How do I update a system that still points at @txt.att.net after the shutdown?

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.

Can more than one person send alerts from the same account?

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.

Written by
Rakesh Patel
Rakesh Patel
Founder and CEO of TextBolt
Rakesh Patel is an experienced technology professional and entrepreneur. As the founder of TextBolt, he brings years of knowledge in business messaging, software development, and communication tools. He specializes in creating simple, reliable solutions that help businesses send and manage text messages through email. Rakesh has a strong background in IT, product development, and business strategy. He has helped many companies improve the way they communicate with customers. In addition to his technical expertise, he is also a talented writer, having authored two books on Enterprise Mobility and Open311.