4 ms·
I considered switching APNs, but didn't want to run afoul of any AT&T rules. I went ahead and gave it a try anyway, switching from `broadband` to `NXTGENPHONE`
by acaloiar 4y ago
I considered switching APNs, but didn't want to run afoul of any AT&T rules.
I went ahead and gave it a try anyway, switching from `broadband` to `NXTGENPHONE`. I wasn't able to authenticate with `NXTGENPHONE`, so I switched it back to `broadband`.
After re-authenticating, I'm no longer being throttled. I'm both happy and deeply dissatisfied with this outcome because I think now I'm less likely to get to the bottom of it.
I'll add this to my updates and keep monitoring the situation.
Thanks, I think!
- kevin_nisbet 4y agoYou're welcome. This just reminded me of the IT Crowd... Have you tried turning it off and on again. By disconnecting / reconnecting by trying the APN switch, it might've just put you on a different P-GW that has a different traffic shaping configuration or current state.
- acaloiar 4y agoIt'll never get old or become poor advice :)
- neurostimulant 4y agoThe only way to get to the bottom of this is probably just applying for a relevant job at AT&T, get accepted by whatever means necessary (low asking salary, nepotism, etc), check their network configuration yourself, then immediately submit your resignation once you're satisfied. I think I read somewhere about someone who did exactly like this in a software company. A new employee showed up, immediately fixed a long-standing bug, then submit their resignation.