Using an Apple Mac as an always-on server often presents some interesting challenges. Even though macOS has deep roots in the stable Unix environment, Apple never really designed the software for unattended, around-the-clock use. Most normal computer users naturally reboot their machines every few days or weeks, so they never notice any deep system flaws. However, if a user leaves their Mac running continuously for exactly 49 days, 17 hours, 2 minutes, and 47 seconds, a bizarre mathematical bug triggers and completely breaks the computer’s ability to connect to the internet.
A technology company called Photon discovered this highly specific problem entirely by accident. The company uses a large fleet of Mac computers specifically to monitor Apple’s iMessage services 24 hours a day. Suddenly, several of their monitoring machines completely stopped responding to incoming network connections. The crash looked incredibly strange because the computers still responded to simple “ping” requests, making it seem as if the machines were awake and functioning perfectly.
To make the mystery even more confusing, the affected computers actually kept all their existing open network connections intact. The machines simply refused to establish any brand new connections. Because the failure was invisible and completely unexplainable, the frustrated systems administrators at Photon had no choice but to reboot the broken machines to get them working again. However, rebooting a computer never actually solves the underlying problem. The team knew that if the crash happened once, it would inevitably happen again.
The engineering team noticed a pattern and decided to test a specific theory. They realized that another group of Mac computers in their fleet was rapidly approaching the 49.7-day uptime mark. They quickly wrote a script to create new network connections constantly and sat back to watch what happened. Exactly as they predicted, the moment the uptime clock hit that fateful number, the Mac stopped making new network connections without displaying a single warning or error message.
The engineers started digging deep into the operating system code and quickly found the culprit. The crash stems directly from an internal networking timer called “tcp_now.” The entire job of this specific counter is to track exactly how many milliseconds have passed since the computer first booted up. The problem is that the operating system stores this number as a 32-bit unsigned integer. This specific type of digital storage has a hard mathematical limit. It can only count up to 4,294,967,295 before it wraps back around to zero. If you calculate that number in milliseconds, you get exactly 49.7 days.
The actual crash happens because of how the Mac cleans up old internet traffic. Whenever you visit a website or send an email, your computer opens a temporary network connection. By standard design, operating systems clear out these closed connections after a short wait, which takes about 30 seconds on macOS. However, when the “tcp_now” clock reaches its mathematical limit, a bug in Apple’s core kernel code causes the clock to freeze. When the system tries to calculate whether a connection is 30 seconds old, the frozen clock ruins the calculation. The computer always decides the answer is “no,” and it refuses to delete the old connection.
Because the computer never discards old connections, the system’s memory simply fills up with useless data. The network stack eventually runs completely out of available ports, and the computer’s internet access grinds to a sudden, permanent halt. How quickly a user notices the crash depends entirely on how heavily they use the internet. A busy server opening thousands of connections will crash almost instantly when the clock freezes. While this specific bug seems strange, computer history is full of similar mathematical errors, such as the famous Windows 98 crash that occurred at the same 49.7-day mark.
Right now, the only way to fix a frozen Mac is to completely reboot the machine and reset the 49-day clock to 0. The team at Photon mentioned they are actively working on a temporary software patch, but the true fix must come directly from Apple. Engineers noted that Apple’s core code simply ignores the established industry standards for handling these specific timestamp clocks. Since the tech community widely publicized this embarrassing bug, Apple will likely release an official software update to fix the math very soon.
