@makkahn28, it is not an APN related issue. With whatever APN we had on our phones, everything was working up until a few days ago. The APN settings didn't self corrupt on all our phones. Anyway, the techs are on it.
Update: I just receive a phone call from Public Mobile tech support. I learned a little about the two APNs and their differences at the network end. Apparently isp.mb.com was supposed to be the "official" tethering APN. Those wanting to use tethering were supposed to be asked to use this APN. This APN incorporated some information logging on tethering for monitoring, potentially marketing purposes. The non tethering APN sp.mb.com also supports tethering as they don't block it. So unless customers "got the memo" about using the tethering APN, it is really a free for all. Recently, the network problem they have been having was with the isp.mb.com APN. People were to migrate over to the sp.mb.com. I guess the problem grew and tethering is being affected on the sp.mb.com. I tried a tethering session with the tech. He did some diagnostics and got some data points. The traffic bung up is definitely at the network end. He detected some brief requests to websites and then things stopped. Its back to the drawing board. Stay tuned. If I get any more information, I will post it. @sheytoon, if you are around, we sure could use some of your expert networking knowledge here.
Update 2: I just received another call back from tech support. They believe that they have found and resolved the problem that is breaking tethering. I don't have a device to do a tethering test at the moment and so I will try at home tonight. Others who had problems with tethering, please try and report status. Use the sp.mb.com APN, include default,dun in the APN type.
