Thursday, April 9th 2026
Apple MacBooks Lose Network Connectivity After 49.7 Days Due to macOS "Time Bomb" Bug
Apple's MacBook Neo, MacBook Air, and the latest MacBook Neo series of laptops are now susceptible to a significant performance drop if they remain powered on for 49.7 days without a reboot. Specifically, after exactly 49 days, 17 hours, 2 minutes, and 47.296 seconds of continuous operation, the entire TCP/IP networking stack shuts down and stops establishing new connections. This unusual bug stems from a kernel-level issue in Apple's XNU kernel involving tcp_now, a 32-bit unsigned integer that tracks elapsed milliseconds since boot for the TCP stack. When it reaches its maximum value of 4,294,967,295, the counter stalls instead of resetting, disrupting the arithmetic macOS uses to expire and discard closed connections.
These inactive connection sessions accumulate quickly, increasing CPU usage as the system struggles to handle an ever-growing backlog. Once the available port pool, typically around 16,384 ports, is fully used, no new connections can be opened. Applications that rely on network access begin to fail, although already-established sessions continue to function, and the machine still responds to pings, albeit much more slowly. This initially delayed the diagnosis of the bug. A reboot resets the counter and restores normal operation, but the issue will recur on the same schedule after another 49.7 days of continuous use. There are potential solutions to fix the bug by using larger 64-bit integers, but this would require more extensive code changes, performance testing, and additional work compared to a simple fix.The Photon team that discovered this issue notes that anyone managing a long-running MacBook should keep in mind the 49.7-day mandatory reboot until a fix is delivered. This is particularly important in enterprise environments, where managing machines is crucial for ensuring smooth operation without disrupting the workflow. The Photon team is also preparing a targeted workaround with the tcp_now that will address the connection freeze without requiring a restart, likely in the form of a live kernel patch or something similar. We need to wait and see how this will be implemented before the patch is delivered.
Sources:
Photon, via Tom's Hardware
These inactive connection sessions accumulate quickly, increasing CPU usage as the system struggles to handle an ever-growing backlog. Once the available port pool, typically around 16,384 ports, is fully used, no new connections can be opened. Applications that rely on network access begin to fail, although already-established sessions continue to function, and the machine still responds to pings, albeit much more slowly. This initially delayed the diagnosis of the bug. A reboot resets the counter and restores normal operation, but the issue will recur on the same schedule after another 49.7 days of continuous use. There are potential solutions to fix the bug by using larger 64-bit integers, but this would require more extensive code changes, performance testing, and additional work compared to a simple fix.The Photon team that discovered this issue notes that anyone managing a long-running MacBook should keep in mind the 49.7-day mandatory reboot until a fix is delivered. This is particularly important in enterprise environments, where managing machines is crucial for ensuring smooth operation without disrupting the workflow. The Photon team is also preparing a targeted workaround with the tcp_now that will address the connection freeze without requiring a restart, likely in the form of a live kernel patch or something similar. We need to wait and see how this will be implemented before the patch is delivered.

28 Comments on Apple MacBooks Lose Network Connectivity After 49.7 Days Due to macOS "Time Bomb" Bug
Well done Apple, maybe start vibe coding like MS so you can make modern day fuck ups instead?
It's not like 99% of the industry already know why that is a bad idea...
Keeping my browser up to date is way more relevant, security-wise.
This is the apple version of it.
not rebooting or using cold boots in 50 days for a portable device?
samsung tablet fake android even annoyed me with the pop up message when i intend to let it automatically reboot? at 2am was the default.
windows will quite often crash and therefore most often never hit 50 days. or will annoy you with forced reboot because of a update.
a small issue compared to afaik rockchip having a 30th february in their date chip of their processors.
(To be fair, there are security updates as well. Just the first thing mentioned in the release notes is "8 new emoji").
To be fair, it's minor glitch. It's a not a security issue, or stability problem. Save whatever needs to be saved, reboot and one is up and running fine.
While this is amusing, I think the Apple reputation for a rock solid MacOS experience is safe..
I can't think of a consumer tech company that performs more major updates than Apple.
How's that Windows for ARM coming along? After what, 15 years or so now? :roll:
Welcome to TPU!
Windows on ARM? I think that already went the way of the Windows Phone tbh. But its not unlike MS to revive that zombie a half dozen times in the near future. I can't wait for them to reintroduce, say, 'Zune' for music, now called CoZune or some stupid shit because it can detect what song you want to hear by taking all your data. And then, again wonder why it won't fly.
Maybe don't listen to every single "possible" threat in the shadows when you're not even a target. If my Server Core and Windows 10 ProWD builds are fine, we're good.
We've gone from WITH-LOVE-FROM-AMERICA.txt appearing on desktop from Unity Hub mid-2022 and getting to CPUID downloads getting pwned for a day in April 2026.
There are definitely threat actors targeting many of us based on the interests we have that fall under wrongthink (we own our hardware) and it does appear to be getting worse.
At the end of the day, only stupid people get catastrophically pwned and the only real threats that make their way onto hardened systems are through supply chain disruptions.
It's funny that it took this long for an Apple bug of this nature to make itself known because there are Apple servers and I'm sure many of them are running from some Macbook.
All this thread tells me is that almost none of them make it to 50 days of uptime and either that's something these customers find okay or they actually use computers like normal.
Can anyone elaborate on who the "Photon" team are? I assume security researchers?