On January 1, something unusual happened to many people who owned certain Hondas and Acuras. A strange glitch in the clocks found in those automobiles had them going back in time some 20 years.
Many of the drivers were confused as to why the clocks started reading the wrong time. They had jumped back 20 years and are now reading January 1, 2002.
As most people do these days, the confused car owners went online to see if they could come up with a quick fix. They also wanted to see if others were experiencing the same problem.
Sumner Hushing and Steven Tender are Twitter users who shared images of what was taking place in those clocks. Tender even claims that he thought he was going crazy!
I thought I was going crazy because my 2007 @Honda CR-V is now always 4 o'clock. pic.twitter.com/dzKmvrLw0B
— Steven Tender (@MooseTender) January 8, 2022
Nobody is really sure what is going on but it seems as if many of the Hondas and Acuras that were sold in 2006-2014 came with an added feature. That feature is a technical glitch that seems to be associated with a programming issue!
According to a report on Jalopnik, Honda is aware of the issue and they claim to be working on it. As of this time, however, their brightest engineers are unable to come up with a fix for the issue so they are recommending that their customers wait it out until it fixes itself.
Honda also released a statement, saying: “We have escalated the NAVI Clock Issue to our Engineering Team and they have informed us that you will experience issue from Jan 2022 thru August 2022 and then it will auto-correct. Please be assured that we will continue to monitor this and will advise you if a fix is available before that time.”
Honda owners are not satisfied to simply sit on the sidelines and wait for a few months to see if it fixes itself. They are calling it the Y2K22 bug, and there have been a few theories as to how it may have happened.
One Honda enthusiast said in a forum that the issue may have to do with how the data is written by many computers, as “2201010001 (YYMMDDHHMM).” Older computers are not always able to handle a larger number so when the year starts with 22, the time and date are unable to be registered properly.
Recently @lazygamereviews joked about the “Y2K22 bug”
Well, for some of us it’s real: https://t.co/AaQnE1CREk
Happy 2002 y’all! 🤣 pic.twitter.com/syz1b0burR
— Hello, yes, this is Gregly (@glindsey) January 5, 2022
He went on to say that he isn’t able to prove it but the timing seems to be more than a coincidence. Think of it as a Y2K bug, but on a much smaller scale.
Fortunately, the navigation system and other functionality in the car are not affected. If owners of Hondas that are affected by this bug are concerned, they can schedule an appointment with their local authorized Honda dealer for repair, if one happens to become available.