The Curious macOS Bug That Disconnects Your Internet After 49 Days of Uptime

Unveiling a Peculiar macOS Connectivity Glitch

The tech community has recently been introduced to an unusual bug in macOS, brought to light by software developer Photon. This flaw, which impacts TCP (Transmission Control Protocol) networking—a fundamental component for internet connectivity—manifests in a very specific way: if a Mac remains online and powered on for exactly 49 days, 17 hours, 2 minutes, and 47 seconds, its internet connection will simply stop working. Such bugs, though rare, underscore the inherent complexity of modern operating systems and the intricate dance of network protocols that keep our devices connected.

Delving into the Technical Core: A 32-bit Integer Overflow

Photon's detailed post not only describes the bug's manifestation but also delves into its technical origins. According to the developer, the underlying cause is a 32-bit integer overflow within the macOS XNU kernel. The XNU kernel is the very core of the operating system, responsible for managing hardware resources and facilitating communication between software and hardware. Specifically, the flaw lies in how the kernel tracks Transmission Control Protocol (TCP) timestamps. When a 32-bit counter, which has a finite maximum value, exceeds its capacity after that precise period of uptime, an 'overflow' occurs. This overflow leads to TCP connections failing, illustrating how even minute details in low-level programming can have significant operational impacts.

The Elusive Nature: Why Most Users Remain Unaffected

Despite the existence of this bug, the vast majority of Mac users will likely never encounter it. The reason is quite straightforward: most people routinely restart their Macs. The most common trigger for these restarts is system updates. Apple frequently releases macOS updates, many of which require a system reboot to complete the installation process. For instance, the recent release of macOS 26.4.1, which followed macOS 26.4 by just two weeks, provided two distinct instances where a Mac would likely have been restarted. These restarts effectively reset the uptime counter, preventing the bug from ever manifesting. This cycle of updates and reboots acts as a natural defense mechanism against such time-based system failures.

The Simple Fix and What Lies Ahead

Fortunately, the solution to this highly specific problem is as simple as the problem is precise: a straightforward restart of the Mac. Upon rebooting, all network connections are reset, and the system returns to normal functionality. Crucially, the uptime counter is also reset, meaning the 49-day cycle begins anew. Photon is actively working on a fix for this bug, although their post does not specify whether Apple has been officially notified. However, it is reasonable to anticipate that Apple will address this issue in a future macOS update, given their commitment to system stability. Currently, it remains unclear which specific versions of macOS are affected by this integer overflow.

Guidance for High-Uptime Environments

While the bug is rare, users operating Macs in environments where continuous uptime is critical—such as servers or dedicated workstations that are rarely powered down—should take precautionary measures. It is advisable to restart these systems at a convenient, planned time, simply as a preventative measure. To check how long a Mac has been running, users can open the Terminal application and type the command uptime, followed by pressing Return. This command will display the system's uptime. Additionally, third-party utilities like Particulars and iStatMenus offer detailed uptime statistics and other system parameters, facilitating proactive monitoring and management for those who need it most.