Advisory: AT&T 3G Shutdown in February 2022
What do I need to know?
AT&T will shut down its 3G network in the United States on February 22, 2022. If your Super SIM-enabled devices depend on 3G connectivity, they will no longer be able to connect to AT&T after this shutdown. You may be impacted even if your device supports 4G LTE.
What do I need to do?
My devices don’t support LTE or LTE-M
If your devices depend on legacy 2G and 3G networks, you will lose access to AT&T’s network.
- You may be able to use T-Mobile’s 2G and 3G networks if you’re within coverage. However, T-Mobile also intends to shut down its legacy 2G and 3G networks in the near future.
- You should plan to retire or replace your devices that depend on 2G/3G networks in the United States with 4G LTE-enabled devices.
My devices do support LTE or LTE-M
If your devices support LTE but are configured as voice-centric, they may be unable to connect to AT&T’s network as AT&T delivers circuit-switched (CS) voice via the 3G network.
- Refer to AT&T’s document “LTE Device Implications upon 3G Sunset” for a link to download a workbook of approved modules.
- Review your modem’s settings and consult with your modem provider to determine if you can disable all voice and IMS (VoLTE) services on your modem and reconfigure it as data-centric. This will allow it to maintain connectivity on AT&T.
- If your solution uses smartphones or tablets, please refer to this list of devices that should continue to connect after the 3G shutdown.
For devices deployed in the United States, Twilio recommends that you enable both T-Mobile and AT&T on your Network Access Profiles to give your Super SIMs multiple network connectivity. Check your Network Access Profiles and enable T-Mobile and AT&T unless you have specific commercial or technical factors that prevent this.
If AT&T and T-Mobile are already enabled on your Network Access Profiles, you may not need to make any changes.
If you experience connectivity issues with AT&T, especially if your devices only supports 2G/3G, you may be able to resolve the issue by either:
- Blocking AT&T in your Network Access Profile.
- Moving impacted devices to a different Fleet that uses a different Network Access Profile with AT&T disabled.
Need some help?
We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Stack Overflow Collective or browsing the Twilio tag on Stack Overflow.