Modem drops internet connection to router

It's most likely Cox rolled out IPV6 to your area recently and those changes aren't agreeing with your Apple Airport. Two options: change your IPV6 settings in Airport Utility to "link-local only" or switch DNS servers from Cox to Google. There's several threads here on Cox's support forums as well as Apple's. I have an AirPort Extreme and just went through this about a month ago. If you want to do "link-local only" (you'll lose IPV6 compatibility and possibly some speed): open Airport Utility, tap on the icon of your Airport, tap edit, advanced, IPV6, configure IPV6, change this from "automatically" to "link-local only" and tap "done". Keep tapping "done" on each screen. The Airport will reboot. To go with option 2 and switch DNS servers (this will maintain IPV6 compatibility and speed): Open Airport Utility app. Tap on your Airport basestation's icon. Tap "Edit" in the upper right hand corner of the screen. Tap "Internet Connection". DHCP should be highlighted in blue at the top of the screen. Under "DNS Server" you will see a primary and secondary set of numbers. These are the Cox DNS server numbers. If you are using Google, you'll enter the following. There are other public DNS servers you can use like Level 3 and others. Do an internet search for it. For Google: tap in the field next to "Primary" under "DNS Server". Type in "8.8.8.8" (without the quotation marks). In the "Secondary" field, type "8.8.4.4" (again, without quotation marks). Go down to "IPv6 DNS Server" and type in the "Primary" field "2001:4860:4860::8888" (no quotation marks and notice the double colon between 4860 and 8888). Now go to the "Secondary" field and type "2001:4860:4860::8844" (no quotations and again notice the double colon). This switches you to Google servers (after the unit reboots). "IPv6 mode" should be "Native". "Share IPv6 Connection" should be on. "Block incoming IPv6" should be on. Keep tapping "Done" at every screen to save your changes and reboot. Once rebooted, you should be able to go back to the screen where the DNS settings are and see that they are now pointing to Googles servers. At this point, power off both the cable modem and AirPort for about two minutes. Power the modem back on first and let it boot. This could take a minute or two. Then power up the AirPort. Once everything is back up and running, go back into AirPort Utility. We are going to check that you have a functioning IPv6 connection. Tap on your AirPorts icon. Tap "Edit" in the upper right hand corner of the screen. Tap "Advanced" then "IPv6". You should see an IPv6 WAN address and an IPv6 Delegated Prefix assigned. Now open up Safari and go to www.test-IPv6.com. This site will test the state of your connections' IPv6 readiness. You should now have a working IPv6 connection. For some, these changes may seem a bit intimidating. But, there's nothing here that can't be undone with a hard reset of the AirPort (the tiny button on the back that you have to press in with a paper clip for 10 seconds). This would completely reset the AirPort to factory defaults like it was when you first unboxed it when it was new. Best of luck.  Hope this helps. 

Im not so sure it's a IPv6 issue. I think you may be projecting your problem onto the OP.  I don't see why a connection issue every 14 hours would be related to IPv6. The lease on both IPv4 and IPv6 are longer. Also, OP gives no mention of having a Airport router and his previous post reveals a issue up to a year ago.

My first guess would be T3 errors caused by signal issues. These short disruption can cause issues with the NAT connection between modem and router. Do you have to reboot the modem to fix? Or just the router? Both? Also what model modem and router do you have?

Last, what are the modem's signal levels? You can usually find them at 192.168.100.1 unless you have a gateway. If so, respond and I can give specific instructions.

He hashtagged Apple Airport. That's how I knew it was an Apple Airport. 14 hours seems strange, but it could be they're not home during the day so they don't notice the fact that's it's dropping more frequently. And I'm not projecting anything. I solved my issue and have helped others with the same issue over on the Apple forums. Just trying to be helpful, you know? ✌

Thanks Jedie24!!

I am having the same problem  which began Feb. 26 when Cox evidently made some changes in the Rhode Island market.  I have had a Cox technician come out and he was unable to solve the problem.  I have spent two hours on the phone with Apple and still the internet dropping is happening, now more frequently.

I will try this suggested solution when I return from business travel, but I am irate that Cox made this change and seems absolutely oblivious to the problems created---

Why is Cox so indifferent to this enormous problem?

Jedie24 said:
He hashtagged Apple Airport.

Missed that, sorry. So many people put random hashtagges that I don't read them anymore. I take it back, if Airport, IPv6 would be the first think I suggest checking too.