Tech
Restart your phone every week to fight malware, NSA says
Twenty-five years ago, the world trembled in the fear at the coming of the new millennium. A lot of people thought that computers all over the world would just stop working when the calendars rolled over from 1999 to 2000. Because computers were supposedly incapable of distinguishing 2000 from 1900, the so-called Y2K bug would break critical machines from functioning.
As you might have guessed, the world didn’t end in 2000. However, if everyone in 2000 feared how the world depended heavily on technology, imagine what a world-breaking bug can do in 2024. Now, thanks to a major mishap last weekend, you don’t need to imagine anymore.
In case you missed all the systems going down all over the world, a CrowdStrike incident caused an unprecedented number of PCs to crash, taking down essential services and companies.
What happened?
CrowdStrike is a cybersecurity company that ships important security updates to a vast number of systems operating through the cloud. It helps companies detect and prevent potential security threats. Because the service operated mainly in the cloud, most people, like you and me, probably have no idea how much the entire world relies on it.
Over the weekend, however, we all got a taste. On Friday, the company rolled out a security update to all its customers on Windows-based PCs and servers. The update contained a piece of software that caused PCs to enter a boot loop, preceded by the dreaded blue screen of death.
Almost immediately, systems crashed. Though a lot of essential services went down, the most visible effects came through flight delays and cancellations at airports all over the world. Bank services also went down. If a service you rely on is down today, chances are that they are still reeling from the error.
If you’re worried about your own machines, the error does not affect personal devices. It’s also only affecting Windows-based devices, so Macs are safe.
A fix rolls out
Hours after, CrowdStrike quickly pushed out an update that resolved the issue. For a lot of customers, that was the end of it. Not all systems were automatically fixed, though.
Some systems require an IT representative to actually handle the issue themselves at their respective servers. Some also require additional steps, such as rebooting systems multiple times.
Thankfully, the main brunt of the issue has been resolved. However, a comprehensive fix might take quite a while. If a service is still down right now, it’s likely that they’re still working on a fix at their end.
What does this mean for the world?
Back in 1999, the early internet era imagined a world where a single bug can take down the world’s systems in one fell swoop. Twenty-five years later, the world’s fears finally manifested into a global incident that crippled the globe for a weekend.
Thankfully, the world also moved fast to fix the problem. Regardless, it proved how much everyone relies on technology these days. The onus isn’t on regular people to find a workaround, though. The incident is just a grim reminder that things like this can (and does) happen.