When I got my Max Transit Cat 18, I signed up for a data plan with a t-mobile reseller first who at the time had positive reviews, and then after a month or so, t-mobile just stopped working.
Then I signed up for cricket since cricket’s IMEI checker said the max transit was compatible and used it for several months without issue. I don’t use tons of data but don’t want to worry about every megabit, so I signed up for the 100 GB simply data plan, but then cricket sent out an email that due to the 3G shutdown, my device would no longer be supported in 2022. I wasn’t sure what to make of this since the Pepwave doesn’t do anything with 3G voice service obviously. But…
In case, I switched to the ATT Prepaid 100 GB data plan since the max transit cat 18’s IMEI said it was an ok bring your own device for the ATT data plan.
Now this morning I just got an email from ATT that says:
Cancellation Notice: It’s urgent you upgrade to a new compatible device. Your current device will stop working any day now and on April 1st AT&T will terminate your account. (the Pepwave Max Transit Cat 18 is the only device on this prepaid data account.)
The Max Transit Cat 18 is an awesome device, but it sure has been a major frustration trying to keep it online in the USA.
Is there any indication in the account itself that it is going away or not compatible? I ask because I’m on the Prepaid $55 100GB plan with a Max Transit Cat 18 (HW2 with an LM960 chip) … I haven’t received an email and I’m logged into my account and everything looks normal. What email address did it come from so I can keep an eye out for it?
I also checked on the device → Advanced → Sim Toolkit → SMS and the messages are all just about processing my monthly payments, nothing saying the device is going to be disconnected.
Nothing in the account itself indicates a problem that I can see.
It just charged me for the next month a few days ago too!
Email came from [email protected]
Well I just received the same email at 1:33PM CST. I wonder what’s up with the day before 3G goes offline emailing cancellation notices. Odd to say the least. In my case it’s only 1 of 3 connections, so I’m going to let it ride and see what unfolds.
Very disappointing. Hopefully it will turn around. Starlink is still a no-show, still delayed to mid-2022 after waiting over a year… a year or three ago there were several new data plans from verizon, att, and t-mobile, so I thought we were finally going to be able to get a basic data plan without trouble. The 100GB plans seemed fairly reasonable in terms of data compared to people watching video on their smartphones. It seems odd that we’re now in 2022 facing the same challenges as two years ago to simply be online at all.
For anyone who received this email, please help identify the product code you are using. I expect the Cat18 transit unit is MAX-TST-GLTE-G-T-PRM, are there users with any other devices who received this email?
I received the message from AT&T as well on our 100/55 plan. We are using the sim in the Max BR1 Pro 5G router. I’m am hoping that we won’t get shut down as there really isn’t another viable option from AT&T for us.
For what it’s worth, an AT&T employee had this response:
Some models of the Netgear Nighthawk MR1100 are impacted by the 3G network shutdown. Out of an abundance of caution and in an effort to be transparent, we notified all customers with models that may be affected. Customers who want to verify the compatibility of their device should call us or visit a store so that we can verify the IMEI.
Thanks
Tim, AT&T Community Specialist
I personally think that email notification went out by accident as they were preparing it. It should have been much more informative and helpful, specific to the 3G shutdown. I’d say it would be a good idea to make sure you are on a 4G or 5G plan, just to be on the safe side. Get your IMEI checked to be even safer.
I haven’t gotten any followup, and am approaching my next billing date. So I guess I’ll renew for another month and hope the February 21 email was a glitch. I don’t see anything in my account itself regarding this still, and data is still working fine.
