The Mystery of Macs Losing Internet Connectivity Every 49 Days

Encountered a strange issue where your Mac suddenly loses internet connectivity? The fix might be as simple as the age-old advice of restarting your device.

Researchers recently uncovered a bug in the macOS networking stack that disrupts all network connections precisely after 49 days, 17 hours, 2 minutes, and 47 seconds of continuous uptime. If your Mac remains operational for that duration, even with intermittent sleep mode, it will fail to communicate over common network protocols.

This peculiar issue is something I personally experienced. Initially, I attempted troubleshooting by toggling Wi-Fi and Thunderbolt Ethernet settings without success. Eventually, a simple reboot resolved the issue. However, this anomaly stems from a design flaw likely introduced in the macOS Tahoe release last year.

The seemingly random timeframe of 49 days, 17 hours, 2 minutes, and 47 seconds holds significance when converted to milliseconds, a unit macOS utilizes internally. This duration aligns with the upper limit of an unsigned 32-bit integer, akin to the infamous “Y2K bug” in a different guise.

Photon, a company managing an open-source framework for iMessage connectivity, first identified this issue. Operating Macs as iMessage gateways, Photon’s systems often surpass the critical 49-day mark triggering the bug. Instead of a simple reboot, they delved deeper into the problem, labeling it a “Ticking Time Bomb in macOS.”

Photon’s detailed blog post, albeit challenging to decipher (John Gruber even suspects it may be AI-generated), outlines the bug’s technical intricacies. Fundamentally, the issue revolves around how macOS networking code handles time.

Understanding the Situation

In essence, macOS stores the duration in milliseconds since the last reboot in an unsigned 32-bit integer with a maximum value of 4,294,967,295. This equates to 49 days, 17 hours, 2 minutes, and 47 seconds. Upon reaching this threshold, the counter resets, disrupting the networking stack’s TCP connections as the system struggles to manage “expired” connections due to the flawed time calculation.

Although the bug’s origin remains unclear, reports indicate that pre-Tahoe macOS versions could operate for extended periods without encountering this issue. An alteration in Apple’s XNU kernel code six months ago hints at a macOS 26 modification, suggesting an oversight that led to the bug’s manifestation.

The recent macOS 26.4.1 update’s effectiveness in addressing this bug remains uncertain. Nevertheless, the straightforward solution of rebooting every 49 days, coupled with Apple’s frequent software updates mandating reboots, minimizes the bug’s impact on most users.

global $wp;
. ‘/’;

?>