Y2K20? A Few Systems Aren't Handling the New Year Very Well

(Image credit: Shutterstock)

People were convinced that computers would stop working in 2000. The so-called Y2K bug was expected to result in massive problems for communication, financial and other systems around the world. That didn't happen--most of the technical problems caused by the new millennium were minor. Now it seems that similar issues are occurring two decades later in systems that weren't prepared for 2020.

The New York Times reported that New York parking meters started to refuse card payments on January 1. It turns out that's because Parkeon, the company that operates those meters in New York and other American cities, didn't update "an anti-fraud security setting." Now the city's manually updating its 14,000 parking meters, which still accept payments made with coins or via the ParkNYC mobile app.

Latest Videos FromTom's Hardware
TOPICS
Nathaniel Mott
Freelance News & Features Writer

Nathaniel Mott is a freelance news and features writer for Tom's Hardware US, covering breaking news, security, and the silliest aspects of the tech industry.

  • HideOut
    A very large hospital/health care software suite is experiencing this too. Mckesson system's used for many in hospital procedures is having date issues. We found this out the hard way on 1/2/20 where I work...
    Reply
  • Crashman
    Some of the IRS's payment systems seem affected.

    Watch a bunch of people go into default and have their property/businesses/etc auctioned off...
    Reply
  • gdmaclew
    Why do people continually downplay the issue of Y2K?
    Programmers like myself spent hundreds of hours in 1999 fixing "bugs" in programs and systems that would have impacted thousands of people.
    The Canadian government alone spent millions of person-hours reprogramming their payroll systems so that employees would be paid normally once the millennial clock ticked over.
    And NASA wouldn't even fly a shuttle or even have one in orbit during the rollover.
    Y2K not noticed? Why? Because we did such a good job.
    Reply
  • drivinfast247
    gdmaclew said:
    Why do people continually downplay the issue of Y2K?
    Programmers like myself spent hundreds of hours in 1999 fixing "bugs" in programs and systems that would have impacted thousands of people.
    The Canadian government alone spent millions of person-hours reprogramming their payroll systems so that employees would be paid normally once the millennial clock ticked over.
    And NASA wouldn't even fly a shuttle or even have one in orbit during the rollover.
    Y2K not noticed? Why? Because we did such a good job.
    🍪
    Reply
  • USAFRet
    gdmaclew said:
    Why do people continually downplay the issue of Y2K?
    Programmers like myself spent hundreds of hours in 1999 fixing "bugs" in programs and systems that would have impacted thousands of people.
    The Canadian government alone spent millions of person-hours reprogramming their payroll systems so that employees would be paid normally once the millennial clock ticked over.
    And NASA wouldn't even fly a shuttle or even have one in orbit during the rollover.
    Y2K not noticed? Why? Because we did such a good job.
    We started testing and fixing in '95 or so.
    I personally fixed or replaced several applications that were tested to fail.
    Reply