iPhone 12 Pro Max Software Version 14.4.2 Modem Fimrware 1.42.03 has intermittent WiFi. Constantly have to turn WiFi "Off and On" for every iPhone we have that is version 13 or higher. There are zero problems with any other WiFi devices such as all the other popular brand phones, game consoles, computers, laptops, iPads and iPhones running IOS 9, or anything else. This is a nightmare, and I am very upset that this problem has not been identified and corrected with the latest software updates. I just completed some testing. iPhone Wifi shows connected, later after being home, no internet at some random time later as usaual. I was unable to ping the gateway / router from iPhone while using Joe's network utility. Zero packets can be captured from a live packet sniff from the router's interface when attempting to ping from the iPhone to the router's gateway IP when this occurs. However, I just noticed that if I "Turn Off" the Personal Hot Spot on the iPhone, WOW I am immediately able to access the internet as well as ping and then everything is working again as usual until the next time. There is also zero delay after disabling Personal Hot Spot and starting any network communication ping tests and the Safari browser on the iPhone was working as soon as the Personal Hot Spot is turned off on the iphone. I believe this issue is being caused by specifically due to wireless encryption keys no longer matching on both ends. Turning off and on the WiFi causes it to rekey the encryption. Also, another test I did with Joe's network utility which had some very odd results. Ping tested the network with a broadcast packet when unable to ping the gateway / router. I was getting a reply but only from the iPhone's DHCP IP obtained via DHCP on WiFi. That indicates the iPhone only detected it's own IP even though it was WiFi connected. Makes sense, because to talk to the local iPhone IP, it doesn't have to encrypt any of the wireless packets destined for the onboard wireless card! A packet sniff from the router's LAN interface on the network detected nothing from the iPhone, basically indicating that nothing was properly encrypted / keyed to match the access point, so nothing was received. Anytime I have ever seen this in the past when troubleshooting wireless issues is when there are no communication due to LACK of WIRELESS ENCRYPTION MATCHING ON BOTH ENDS! In the old days, you used to be able to manually type in the static encryption keys on both ends, Access Point and Wireless Client. Not matching these keys would result in NO PACKETS SENT or RECEIVED due to lack of matching encryption. After turning off the Personal Hot Spot on the iPhone, the same ping test with a broadcast packet, example pinging 192.168.0.255 returned ping results from all the other IP addresses on the network as expected. I suspect as soon as I turn off the Personal Hot Spot that the wireless encryption is immediately re-keyed to match both on both ends. This same type of scenario used to happen back in the days if you manually typed in your IPSEC security keys on both sides of a VPN and they did not match the expected value on both sides, basically making it impossible to decrypt the received data on both sides. I suspect that we could easily prove this issue by simply #1 changing the wireless access point's setup for Key Renewal to ZERO seconds. This basically disables the key from changing after initial connection. That is not something I recommend for anything but temporarily testing / identifying the problem. Leaving Key Renewal disabled would allow someone to easily sniff and attack the wireless. However if the original disconnect problem goes away after changing the key renewal, this would clearly indicate that the problem is related to not Renewing the Keys so they are the same on both sides. Since I only have this problem on Apple Devices running version 13 and 14, I suspect a software encryption / decryption matching issue with the WiFi drivers, etc. This could be a Key Renewal Calculation error or possibly a missed key exchange due to being out of wireless range. However, in my experience this isn't a range issue, but is more of a mismatch that isn't detected by the wireless driver to trigger another re-connection. To me, this is like there is no WiFi setting on the iPhone for Roaming Agressiveness, and somehow it holds on to the same WiFi connection regardless of if it is able to accurately encrypt the data with the correct matching keys.