 |
| MacBooks should be restarted at least every 49 days. |
If you own a MacBook Neo (just $599 on Amazon), a MacBook Pro, or even a powerful iMac, you’ve probably noticed a frustrating pattern: after a few weeks of smooth sailing, your machine starts feeling sluggish. Apps take forever to open. Web pages hang. Video calls stutter. And a simple restart magically fixes everything – for a while.
You’re not imagining it. And it’s not just “Macs being Macs.”
Security researchers at Photon have uncovered a genuine, ticking time bomb buried deep inside macOS’s networking code. The bug acts like a digital countdown: exactly 49 days, 17 hours, 2 minutes and 47.296 seconds after you boot up your Mac, network connections stop terminating properly. The result? A slow, painful death by a thousand open ports – until you restart.
Let’s break down why this happens, who’s affected, and what you can do about it.
The Countdown That Apple Never Told You About
Most Mac users rarely restart their computers. We close the lid, open it back up, and keep working. Days turn into weeks. But behind the scenes, macOS is running a hidden timer – a 32-bit counter that tracks the lifespan of network connections in nanoseconds.
That seemingly random number – 49 days, 17 hours, 2 minutes, and 47.296 seconds – isn’t a coincidence. It’s the maximum value a 32-bit integer can hold when measured in nanoseconds (2³² = 4,294,967,295 nanoseconds). Once that limit is hit, the counter overflows. And that’s when the trouble begins.
According to Photon’s detailed technical report, the bug prevents the operating system from correctly terminating old network connections. Instead of closing them cleanly, macOS leaves them hanging. Over time, your computer accumulates hundreds – sometimes thousands – of zombie connections.
What Happens When the Bomb Goes Off
At first, you might notice your CPU fan spinning up for no reason. That’s your processor working overtime to manage a growing list of connections that should have been closed. As the hours pass, the situation worsens.
macOS has a limited number of available network ports – typically 16,384 for outgoing connections. Once those ports are exhausted, your Mac can’t establish any new connections. Existing ones (like an active Zoom call or a file download) may continue working, but anything new fails.
You’ll see symptoms like:
- Safari or Chrome unable to load new websites
- Email clients failing to send or receive
- Slack, Discord, or Teams showing “no internet”
- App Store updates hanging indefinitely
- Terminal commands like
curltiming out
Strangely, ping still works. So does any connection that was established before the counter overflowed. That’s what makes this bug so deceptive – it doesn’t look like a total network failure. It looks like your Mac is just… tired.
A Blast From the Past: Windows 95 Had the Same Problem
Veteran tech users might feel a chill of recognition. Windows 95 and Windows 98 famously crashed after 49.7 days of uptime due to a similar 32-bit counter overflow in the TCP/IP stack. Microsoft eventually patched it, but not before countless servers and desktops fell victim to the “49-day crash.”
Linux derivatives face their own version of this problem – the Year 2038 issue, where systems using a 32-bit counter for seconds since January 1, 1970 will roll over on January 19, 2038. That’s a disaster still waiting to happen for older embedded systems.
But on macOS? This bug has apparently flown under the radar for years. Photon’s team discovered it while investigating mysterious performance complaints from users who rarely reboot. Their analysis confirms that the overflow affects any Mac running recent versions of macOS – from the budget-friendly MacBook Neo (yep, that $599 Amazon favorite) to the highest-end Mac Studio.
Why Restarting Is the Only Fix (For Now)
Here’s the good news: a simple restart resets the 32-bit counter. Your Mac goes back to zero and behaves perfectly for another 49 days. No data loss, no permanent damage.
The bad news? Apple hasn’t publicly acknowledged the bug yet. There’s no permanent patch as of this writing. If you’re the kind of user who keeps their Mac running for weeks or months at a time – maybe you’re running a home server, a creative studio workstation, or you just hate waiting for boot times – you will hit this wall. Every time.
What You Can Do Today
Until Apple rolls out a fix, you have two options:
- Restart your Mac every few weeks. Set a calendar reminder for every 45 days. It’s a blunt instrument, but it works.
- Monitor your uptime. Open Terminal and type
uptime. If you’re approaching 49 days, schedule a restart before things go south.
Photon’s team has also released a small script that can detect when the counter is nearing overflow, giving you a heads-up before your network ports fill up. Check their full write-up for the technical deep dive and mitigation steps.
The Bottom Line
This isn’t a conspiracy or a hardware defect. It’s a classic programming oversight – a 32-bit counter where a 64-bit one should have been – hiding in plain sight. And it’s affecting millions of Macs worldwide, from the entry-level MacBook Neo to the pro-level workstations that cost ten times as much.
So the next time your Mac feels like it’s running through molasses after a few weeks of uptime, don’t blame yourself. Don’t reinstall your OS. Don’t buy a new laptop (unless you really want that MacBook Neo on Amazon for $599 – it’s a great deal). Just restart.
And maybe send this article to a friend who never turns off their Mac. They probably think they’re going crazy. Now you know they’re not.
*Have you experienced this 49-day slowdown? Let us know in the comments. For more deep dives into weird OS bugs, bookmark Photon’s blog and follow their research.*