Year 2000 problem explained

The term year 2000 problem[1] , or simply Y2K, refers to potential computer errors related to the formatting and storage of calendar data for dates in and after the year 2000. Many programs represented four-digit years with only the final two digits, making the year 2000 indistinguishable from 1900. Computer systems' inability to distinguish dates correctly had the potential to bring down worldwide infrastructures for computer reliant industries.

In the years leading up to the turn of the millennium, the public gradually became aware of the "Y2K scare", and individual companies predicted the global damage caused by the bug would require anything between $400 million and $600 billion to rectify.[2] A lack of clarity regarding the potential dangers of the bug led some to stock up on food, water, and firearms, purchase backup generators, and withdraw large sums of money in anticipation of a computer-induced apocalypse.[3]

Contrary to published expectations, few major errors occurred in 2000. Supporters of the Y2K remediation effort argued that this was primarily due to the pre-emptive action of many computer programmers and information technology experts. Companies and organizations in some countries, but not all, had checked, fixed, and upgraded their computer systems to address the problem.[4] [5] Then-U.S. president Bill Clinton, who organized efforts to minimize the damage in the United States, labeled Y2K as "the first challenge of the 21st century successfully met",[6] and retrospectives on the event typically commend the programmers who worked to avert the anticipated disaster.

Critics argued that even in countries where very little had been done to fix software, problems were minimal. The same was true in sectors such as schools and small businesses where compliance with Y2K policies was patchy at best.

Background

Y2K is a numeronym and was the common abbreviation for the year 2000 software problem. The abbreviation combines the letter Y for "year", the number 2 and a capitalized version of k for the SI unit prefix kilo meaning 1000; hence, 2K signifies 2000. It was also named the "millennium bug" because it was associated with the popular (rather than literal) rollover of the millennium, even though most of the problems could have occurred at the end of any century.

Computerworlds 1993 three-page "Doomsday 2000" article by Peter de Jager was called "the information-age equivalent of the midnight ride of Paul Revere" by The New York Times.[7] [8] [9]

The problem was the subject of the early book Computers in Crisis by Jerome and Marilyn Murray (Petrocelli, 1984; reissued by McGraw-Hill under the title The Year 2000 Computing Crisis in 1996). Its first recorded mention on a Usenet newsgroup is from 18 January 1985 by Spencer Bolles.[10]

The acronym Y2K has been attributed to Massachusetts programmer David Eddy[11] in an e-mail sent on 12 June 1995. He later said, "People were calling it CDC (Century Date Change), FADL (Faulty Date Logic). There were other contenders. Y2K just came off my fingertips."[12]

The problem started because on both mainframe computers and later personal computers, memory was expensive, from as low as $10 per kilobyte, to more than US$100 per kilobyte in 1975.[13] [14] It was therefore very important for programmers to minimize usage. Since computers only gained wide usage in the 20th century, programs could simply prefix "19" to the year of a date, allowing them to only store the last two digits of the year instead of four. As space on disc and tape storage was also expensive, these strategies saved money by reducing the size of stored data files and databases in exchange for becoming unusable past the year 2000.[15]

This meant that programs facing two-digit years could not distinguish between dates in 1900 and 2000. Dire warnings at times were in the mode of:

The Y2K problem is the electronic equivalent of the El Niño and there will be nasty surprises around the globe.

— John Hamre, United States Deputy Secretary of Defense[16]

Options on the De Jager Year 2000 Index, "the first index enabling investors to manage risk associated with the ... computer problem linked to the year 2000" began trading mid-March 1997.[17]

Special committees were set up by governments to monitor remedial work and contingency planning, particularly by crucial infrastructures such as telecommunications, utilities and the like, to ensure that the most critical services had fixed their own problems and were prepared for problems with others. While some commentators and experts argued that the coverage of the problem largely amounted to scaremongering,[18] it was only the safe passing of the main event itself, 1 January 2000, that fully quelled public fears.

Some experts who argued that scaremongering was occurring, such as Ross Anderson, professor of security engineering at the University of Cambridge Computer Laboratory, have since claimed that despite sending out hundreds of press releases about research results suggesting that the problem was not likely to be as big as some had suggested, they were largely ignored by the media. In a similar vein, the Microsoft Press book Running Office 2000 Professional, published in May 1999, accurately predicted that most personal computer hardware and software would be unaffected by the year 2000 problem.[19] Authors Michael Halvorson and Michael Young characterized most of the worries as popular hysteria, an opinion echoed by Microsoft Corp.[20]

Programming problem

The practice of using two-digit dates for convenience predates computers, but was never a problem until stored dates were used in calculations.

Bit conservation need

Business data processing was done using unit record equipment and punched cards, most commonly the 80-column variety employed by IBM, which dominated the industry. Many tricks were used to squeeze needed data into fixed-field 80-character records. Saving two digits for every date field was significant in this effort.

In the 1960s, computer memory and mass storage were scarce and expensive. Early core memory cost one dollar per bit. Popular commercial computers, such as the IBM 1401, shipped with as little as 2 kilobytes of memory. Programs often mimicked card processing techniques. Commercial programming languages of the time, such as COBOL and RPG, processed numbers in their character representations. Over time, the punched cards were converted to magnetic tape and then disc files, but the structure of the data usually changed very little.

Data was still input using punched cards until the mid-1970s. Machine architectures, programming languages and application designs were evolving rapidly. Neither managers nor programmers of that time expected their programs to remain in use for many decades, and the possibility that these programs would both remain in use and cause problems when interacting with databases – a new type of program with different characteristics – went largely uncommented upon.

Early attention

The first person known to publicly address this issue was Bob Bemer, who had noticed it in 1958 as a result of work on genealogical software. He spent the next twenty years fruitlessly trying to raise awareness of the problem with programmers, IBM, the government of the United States and the International Organization for Standardization. This included the recommendation that the COBOL picture clause should be used to specify four digit years for dates.[21]

In the 1980s, the brokerage industry began to address this issue, mostly because of bonds with maturity dates beyond the year 2000. By 1987 the New York Stock Exchange had reportedly spent over $20 million on Y2K, including hiring 100 programmers.[22]

Despite magazine articles on the subject from 1970 onward, the majority of programmers and managers only started recognizing Y2K as a looming problem in the mid-1990s, but even then, inertia and complacency caused it to be mostly unresolved until the last few years of the decade. In 1989, Erik Naggum was instrumental in ensuring that internet mail used four digit representations of years by including a strong recommendation to this effect in the internet host requirements document .[23] On April Fools' Day 1998, some companies set their mainframe computer dates to 2001, so that "the wrong date will be perceived as good fun instead of bad computing" while having a full day of testing.[24]

While using 3-digit years and 3-digit dates within that year was used by some, others chose to use the number of days since a fixed date, such as 1 January 1900.[25] Inaction was not an option, and risked major failure. Embedded systems with similar date logic were expected to malfunction and cause utilities and other crucial infrastructure to fail.

Saving space on stored dates persisted into the Unix era, with most systems representing dates to a single 32-bit word, typically representing dates as elapsed seconds from some fixed date, which causes the similar Y2K38 problem.

Resulting bugs from date programming

Storage of a combined date and time within a fixed binary field is often considered a solution, but the possibility for software to misinterpret dates remains because such date and time representations must be relative to some known origin. Rollover of such systems is still a problem but can happen at varying dates and can fail in various ways. For example:

Similar date bugs

See main article: Time formatting and storage bugs.

4 January 1975

The date of 4 January 1975 overflowed the 12-bit field that had been used in the Decsystem 10 operating systems. There were numerous problems and crashes related to this bug while an alternative format was developed.[31]

9 September 1999

Even before 1 January 2000 arrived, there were also some worries about 9 September 1999 (albeit less than those generated by Y2K). Because this date could also be written in the numeric format 9/9/99, it could have conflicted with the date value 9999, frequently used to specify an unknown date. It was thus possible that database programs might act on the records containing unknown dates on that day. Data entry operators commonly entered 9999 into required fields for an unknown future date, (e.g., a termination date for cable television or telephone service), in order to process computer forms using CICS software.[32] Somewhat similar to this is the end-of-file code 9999, used in older programming languages. While fears arose that some programs might unexpectedly terminate on that date, the bug was more likely to confuse computer operators than machines.

Leap years

See main article: Zeller's congruence. Normally, a year is a leap year if it is evenly divisible by four. A year divisible by 100 is not a leap year in the Gregorian calendar unless it is also divisible by 400. For example, 1600 was a leap year, but 1700, 1800 and 1900 were not. Some programs may have relied on the oversimplified rule that "a year divisible by four is a leap year". This method works fine for the year 2000 (because it is a leap year), and will not become a problem until 2100, when older legacy programs will likely have long since been replaced. Other programs contained incorrect leap year logic, assuming for instance that no year divisible by 100 could be a leap year. An assessment of this leap year problem including a number of real-life code fragments appeared in 1998.[33] For information on why century years are treated differently, see Gregorian calendar.

Year 2010 problem

Some systems had problems once the year rolled over to 2010. This was dubbed by some in the media as the "Y2K+10" or "Y2.01K" problem.[34]

The main source of problems was confusion between hexadecimal number encoding and binary-coded decimal encodings of numbers. Both hexadecimal and BCD encode the numbers 0–9 as 0x0–0x9. BCD encodes the number 10 as 0x10, while hexadecimal encodes the number 10 as 0x0A; 0x10 interpreted as a hexadecimal encoding represents the number 16.

For example, because the SMS protocol uses BCD for dates, some mobile phone software incorrectly reported dates of SMSes as 2016 instead of 2010. Windows Mobile is the first software reported to have been affected by this glitch; in some cases WM6 changes the date of any incoming SMS message sent after 1 January 2010 from the year 2010 to 2016.[35] [36]

Other systems affected include EFTPOS terminals,[37] and the PlayStation 3 (except the Slim model).[38]

The most important occurrences of such a glitch were in Germany, where up to 20 million bank cards became unusable, and with Citibank Belgium, whose Digipass customer identification chips failed.[39]

Year 2022 problem

When the year 2022 began, many systems using 32-bit integers encountered problems, which are now collectively known as the Y2K22 bug. The maximum value of a signed 32-bit integer, as used in many computer systems, is 2147483647. Systems using an integer to represent a 10 character date-based field, where the leftmost two characters are the 2-digit year, ran into an issue on 1 January 2022 when the leftmost characters needed to be '22', i.e. values from 2200000001 needed to be represented.

Microsoft Exchange Server was one of the more significant systems affected by the Y2K22 bug. The problem caused emails to be stuck on transport queues on Exchange Server 2016 and Exchange Server 2019, reporting the following error:[40]

Year 2038 problem

See main article: Year 2038 problem.

Many systems use Unix time and store it in a signed 32-bit integer. This data type is only capable of representing integers between −(2) and (2)−1, treated as number of seconds since the epoch at 1 January 1970 at 00:00:00 UTC. These systems can only represent times between 13 December 1901 at 20:45:52 UTC and 19 January 2038 at 03:14:07 UTC. If these systems are not updated and fixed, then dates all across the world that rely on Unix time will wrongfully display the year as 1901 beginning at 03:14:08 UTC on 19 January 2038.

Programming solutions

Several very different approaches were used to solve the year 2000 problem in legacy systems.

Date expansion
  • Two-digit years were expanded to include the century (becoming four-digit years) in programs, files, and databases. This was considered the "purest" solution, resulting in unambiguous dates that are permanent and easy to maintain. This method was costly, requiring massive testing and conversion efforts, and usually affecting entire systems.
    Date windowing
  • Two-digit years were retained, and programs determined the century value only when needed for particular functions, such as date comparisons and calculations. (The century "window" refers to the 100-year period to which a date belongs.) This technique, which required installing small patches of code into programs, was simpler to test and implement than date expansion, thus much less costly. While not a permanent solution, windowing fixes were usually designed to work for many decades. This was thought acceptable, as older legacy systems tend to eventually get replaced by newer technology.[41]
    Date compression
  • Dates can be compressed into binary 14-bit numbers. This allows retention of data structure alignment, using an integer value for years. Such a scheme is capable of representing 16384 different years; the exact scheme varies by the selection of epoch.
    Date re-partitioning
  • In legacy databases whose size could not be economically changed, six-digit year/month/day codes were converted to three-digit years (with 1999 represented as 099 and 2001 represented as 101, etc.) and three-digit days (ordinal date in year). Only input and output instructions for the date fields had to be modified, but most other date operations and whole record operations required no change. This delays the eventual roll-over problem to the end of the year 2899.
    Software kits
  • Software kits, such as those listed in CNN.com's Top 10 Y2K fixes for your PC:[42] ("most ... free") which was topped by the $50 Millennium Bug Kit.[43]
    Real Time Clock Upgrades
  • One unique solution found prominence. While other fixes worked at the BIOS level as TSRs (Terminate and Stay Resident), intercepting BIOS calls, Y2000RTC was the only product that worked as a device driver and replaced the functionality of the faulty RTC with a compliant equivalent. This driver was rolled out in the years before the 1999/2000 deadline onto millions of PCs.
    Bridge programs
  • Date servers where Call statements are used to access, add or update date fields.[44] [45] [46]

    Documented errors

    Before 2000

    On 1 January 2000

    Problems that occurred on 1 January 2000 were generally regarded as minor.[60] Consequences did not always result exactly at midnight. Some programs were not active at that moment and problems would only show up when they were invoked. Not all problems recorded were directly linked to Y2K programming in a causality; minor technological glitches occur on a regular basis.

    Reported problems include:

    After January 2000

    On 29 February and 1 March 2000

    See also: Leap year problem. Problems were reported on 29 February 2000, Y2K's first Leap Year Day, and 1 March 2000. These were mostly minor.[93] [94] [95]

    On 31 December 2000 or 1 January 2001

    Some software did not correctly recognize 2000 as a leap year, and so worked on the basis of the year having 365 days. On the last day of 2000 (day 366) and first day of 2001 these systems exhibited various errors. Some computers also treated the new year 2001 as 1901, causing errors. These were generally minor.

    Since 2000

    See main article: Time formatting and storage bugs.

    Since 2000, various issues have occurred due to errors involving overflows. An issue with time tagging caused the destruction of the NASA Deep Impact spacecraft.[104]

    Some software used a process called date windowing to fix the issue by interpreting years 00–19 as 2000–2019 and 20–99 as 1920–1999. As a result, a new wave of problems started appearing in 2020, including parking meters in New York City refusing to accept credit cards, issues with Novitus point of sale units, and some utility companies printing bills listing the year 1920. The video game WWE 2K20 also began crashing when the year rolled over, although a patch was distributed later that day.[105]

    Government responses

    Bulgaria

    Although the Bulgarian national identification number allocates only two digits for the birth year, the year 1900 problem and subsequently the Y2K problem were addressed by the use of unused values above 12 in the month range. For all persons born before 1900, the month is stored as the calendar month plus 20, and for all persons born in or after 2000, the month is stored as the calendar month plus 40.[106]

    Canada

    Canadian Prime Minister Jean Chrétien's most important cabinet ministers were ordered to remain in the capital Ottawa, and gathered at 24 Sussex Drive, the prime minister's residence, to watch the clock. 13,000 Canadian troops were also put on standby.

    Netherlands

    The Dutch Government promoted Y2K Information Sharing and Analysis Centers (ISACs) to share readiness between industries, without threat of antitrust violations or liability based on information shared.

    Norway and Finland

    Norway and Finland changed their national identification numbers to indicate a person's century of birth. In both countries, the birth year was historically indicated by two digits only. This numbering system had already given rise to a similar problem, the "Year 1900 problem", which arose due to problems distinguishing between people born in the 19th and 20th centuries. Y2K fears drew attention to an older issue, while prompting a solution to a new problem. In Finland, the problem was solved by replacing the hyphen ("-") in the number with the letter "A" for people born in the 21st century (for people born before 1900, the sign was already "+").[107] In Norway, the range of the individual numbers following the birth date was altered from 0–499 to 500–999.

    Romania

    Romania also changed its national identification number in response to the Y2K problem, due to the birth year being represented by only two digits. Before 2000, the first digit, which shows the person's sex, was 1 for males and 2 for females. Individuals born since 1 January 2000 have a number starting with 5 if male or 6 if female.

    Uganda

    The Ugandan government responded to the Y2K threat by setting up a Y2K Task Force.[108] In August 1999 an independent international assessment by the World Bank International Y2k Cooperation Centre found that Uganda's website was in the top category as "highly informative". This put Uganda in the "top 20" out of 107 national governments, and on a par with the United States, United Kingdom, Canada, Australia and Japan, and ahead of Germany, Italy, Austria, Switzerland which were rated as only "somewhat informative". The report said that "Countries which disclose more Y2K information will be more likely to maintain public confidence in their own countries and in the international markets."[109]

    United States

    In 1998, the United States government responded to the Y2K threat by passing the Year 2000 Information and Readiness Disclosure Act, by working with private sector counterparts in order to ensure readiness, and by creating internal continuity of operations plans in the event of problems and set limits to certain potential liabilities of companies with respect to disclosures about their year 2000 programs.[110] [111] The effort was coordinated by the President's Council on Year 2000 Conversion, headed by John Koskinen, in coordination with the Federal Emergency Management Agency (FEMA), and an interim Critical Infrastructure Protection Group within the Department of Justice.[112] [113]

    The US government followed a three-part approach to the problem: (1) outreach and advocacy, (2) monitoring and assessment, and (3) contingency planning and regulation.[114]

    A feature of US government outreach was Y2K websites, including y2k.gov, many of which have become inaccessible in the years since 2000. Some of these websites have been archived by the National Archives and Records Administration or the Wayback Machine.[115] [116]

    Each federal agency had its own Y2K task force which worked with its private sector counterparts; for example, the FCC had the FCC Year 2000 Task Force.[117]

    Most industries had contingency plans that relied upon the internet for backup communications. As no federal agency had clear authority with regard to the internet at this time (it had passed from the Department of Defense to the National Science Foundation and then to the Department of Commerce), no agency was assessing the readiness of the internet itself. Therefore, on 30 July 1999, the White House held the White House Internet Y2K Roundtable.[118]

    The U.S. government also established the Center for Year 2000 Strategic Stability as a joint operation with the Russian Federation. It was a liaison operation designed to mitigate the possibility of false positive readings in each nation's nuclear attack early warning systems.[119]

    International cooperation

    The International Y2K Cooperation Center (IY2KCC) was established at the behest of national Y2K coordinators from over 120 countries when they met at the First Global Meeting of National Y2K Coordinators at the United Nations in December 1998.[120] IY2KCC established an office in Washington, D.C. in March 1999. Funding was provided by the World Bank, and Bruce W. McConnell was appointed as director.

    IY2KCC's mission was to "promote increased strategic cooperation and action among governments, peoples, and the private sector to minimize adverse Y2K effects on the global society and economy." Activities of IY2KCC were conducted in six areas:

    IY2KCC closed down in March 2000.

    Private sector response

    The Y2K issue was a major topic of discussion in the late 1990s and as such showed up in most popular media. A number of "Y2K disaster" books were published such as Deadline Y2K by Mark Joseph. Movies such as Y2K: Year to Kill capitalized on the currency of Y2K, as did numerous TV shows, comic strips, and computer games.

    Fringe group responses

    A variety of fringe groups and individuals such as those within some fundamentalist religious organizations, survivalists, cults, anti-social movements, self-sufficiency enthusiasts and those attracted to conspiracy theories, called attention to Y2K fears and claimed that they provided evidence for their respective theories. End-of-the-world scenarios and apocalyptic themes were common in their communication.

    Interest in the survivalist movement peaked in 1999 in its second wave for that decade, triggered by Y2K fears. In the time before extensive efforts were made to rewrite computer programming codes to mitigate the possible impacts, some writers such as Gary North, Ed Yourdon, James Howard Kunstler,[124] and Ed Yardeni anticipated widespread power outages, food and gasoline shortages, and other emergencies. North and others raised the alarm because they thought Y2K code fixes were not being made quickly enough. While a range of authors responded to this wave of concern, two of the most survival-focused texts to emerge were Boston on Y2K (1998) by Kenneth W. Royce and Mike Oehler's The Hippy Survival Guide to Y2K.

    Y2K also appeared in the communication of some fundamentalist and charismatic Christian leaders throughout the Western world, particularly in North America and Australia. Their promotion of the perceived risks of Y2K was combined with end times thinking and apocalyptic prophecies, allegedly in an attempt to influence followers.[125] The New York Times reported in late 1999, "The Rev. Jerry Falwell suggested that Y2K would be the confirmation of Christian prophecy – God's instrument to shake this nation, to humble this nation. The Y2K crisis might incite a worldwide revival that would lead to the rapture of the church. Along with many survivalists, Mr. Falwell advised stocking up on food and guns".[126] Adherents in these movements were encouraged to engage in food hoarding, take lessons in self-sufficiency, and the more extreme elements planned for a total collapse of modern society. The Chicago Tribune reported that some large fundamentalist churches, motivated by Y2K, were the sites for flea market-like sales of paraphernalia designed to help people survive a social order crisis ranging from gold coins to wood-burning stoves.[127] Betsy Hart wrote in the Deseret News that many of the more extreme evangelicals used Y2K to promote a political agenda in which the downfall of the government was a desired outcome in order to usher in Christ's reign. She also said, "the cold truth is that preaching chaos is profitable and calm doesn't sell many tapes or books".[128] Y2K fears were described dramatically by New Zealand-based Christian prophetic author and preacher Barry Smith in his publication "I Spy with my Little Eye," where he dedicated an entire chapter to Y2K.[129] Some expected, at times through so-called prophecies, that Y2K would be the beginning of a worldwide Christian revival.[130]

    In the aftermath, it became clear that leaders of these fringe groups and churches, had manufactured fears of apocalyptic outcomes to manipulate their followers into dramatic scenes of mass repentance or renewed commitment to their groups, as well as urging additional giving of funds. The Baltimore Sun claimed this in their article "Apocalypse Now – Y2K spurs fears," noting the increased call for repentance in the populace in order to avoid God's wrath.[131] Christian leader Col Stringer in his commentary published, "Fear-creating writers sold over 45 million books citing every conceivable catastrophe from civil war, planes dropping from the sky to the end of the civilized world as we know it. Reputable preachers were advocating food storage and a "head for the caves" mentality. No banks failed, no planes crashed, no wars or civil war started. And yet not one of these prophets of doom has ever apologized for their scare-mongering tactics." Critics argue that some prominent North American Christian ministries and leaders generated huge personal and corporate profits through sales of Y2K preparation kits, generators, survival guides, published prophecies and a wide range of other associated merchandise, such as Christian journalist Rob Boston in his article "False Prophets, Real Profits." However, Pat Robertson, founder of the global Christian Broadcasting Network, gave equal time to pessimists and optimists alike and granted that people should at least expect "serious disruptions".[132]

    Cost

    The total cost of the work done in preparation for Y2K likely surpassed US$300 billion ($ billion as of January 2018, once inflation is taken into account).[133] IDC calculated that the US spent an estimated $134 billion ($ billion) preparing for Y2K, and another $13 billion ($ billion) fixing problems in 2000 and 2001. Worldwide, $308 billion ($ billion) was estimated to have been spent on Y2K remediation.[134]

    Remedial work organization

    Remedial work was driven by customer demand for solutions.[135] Software suppliers, mindful of their potential legal liability,[121] responded with remedial effort. Software subcontractors were required to certify that their software components were free of date-related problems, which drove further work down the supply chain.

    By 1999, many corporations required their suppliers to certify that their software was all Y2K-compliant. Some signed after accepting merely remedial updates. Many businesses or even whole countries suffered only minor problems despite spending little effort themselves.

    Results

    There are two ways to view the events of 2000 from the perspective of its aftermath:

    Supporting view

    This view holds that the vast majority of problems were fixed correctly, and the money spent was at least partially justified. The situation was essentially one of preemptive alarm. Those who hold this view claim that the lack of problems at the date change reflects the completeness of the project, and that many computer applications would not have continued to function into the 21st century without correction or remediation.

    Expected problems that were not seen by small businesses and small organizations were prevented by Y2K fixes embedded in routine updates to operating system and utility software[136] that were applied several years before 31 December 1999.

    The extent to which larger industry and government fixes averted issues that would have more significant impacts had they not been fixed, were typically not disclosed or widely reported.[137]

    It has been suggested that on 11 September 2001, infrastructure in New York City (including subways, phone service, and financial transactions) was able to continue operation because of the redundant networks established in the event of Y2K bug impact[138] and the contingency plans devised by companies.[139] The terrorist attacks and the following prolonged blackout to lower Manhattan had minimal effect on global banking systems.[140] Backup systems were activated at various locations around the region, many of which had been established to deal with a possible complete failure of networks in Manhattan's Financial District on 31 December 1999.[141]

    Opposing view

    The contrary view asserts that there were no, or very few, critical problems to begin with. This view also asserts that there would have been only a few minor mistakes and that a "fix on failure" approach would have been the most efficient and cost-effective way to solve these problems as they occurred.

    International Data Corporation estimated that the US might have wasted $40 billion.[142]

    Skeptics of the need for a massive effort pointed to the absence of Y2K-related problems occurring before 1 January 2000, even though the 2000 financial year commenced in 1999 in many jurisdictions, and a wide range of forward-looking calculations involved dates in 2000 and later years. Estimates undertaken in the leadup to 2000 suggested that around 25% of all problems should have occurred before 2000.[143] Critics of large-scale remediation argued during 1999 that the absence of significant reported problems in non-compliant small firms was evidence that there had been, and would be, no serious problems needing to be fixed in any firm, and that the scale of the problem had therefore been severely overestimated.[144]

    Countries such as South Korea, Italy, and Russia invested little to nothing in Y2K remediation,[126] [142] yet had the same negligible Y2K problems as countries that spent enormous sums of money. Western countries anticipated such severe problems in Russia that many issued travel advisories and evacuated non-essential staff.[145]

    Critics also cite the lack of Y2K-related problems in schools, many of which undertook little or no remediation effort. By 1 September 1999, only 28% of US schools had achieved compliance for mission critical systems, and a government report predicted that "Y2K failures could very well plague the computers used by schools to manage payrolls, student records, online curricula, and building safety systems".[146]

    Similarly, there were few Y2K-related problems in an estimated 1.5 million small businesses that undertook no remediation effort. On 3 January 2000 (the first weekday of the year), the Small Business Administration received an estimated 40 calls from businesses with computer issues, similar to the average. None of the problems were critical.[147]

    Legacy

    The 2024 CrowdStrike incident, a global IT system outage, was compared to the Y2K bug by several news outlets, recalling fears surrounding it due to its scale and impact.[148] [149]

    See also

    External links

    Notes and References

    1. also commonly known as the year 2000 bug, Y2K problem, Y2K scare, millennium bug, Y2K bug, Y2K glitch, or Y2K error.
    2. Book: Committee on Government Reform and Oversight . The Year 2000 Problem: Fourth Report by the Committee on Government Reform and Oversight, Together with Additional Views . 26 October 1998 . U.S. Government Printing Office . 3 . 7 June 2021 . 2021-07-20 . https://web.archive.org/web/20210720091329/https://www.congress.gov/105/crpt/hrpt827/CRPT-105hrpt827.pdf . live .
    3. News: Uenuma . Francine . 20 Years Later, the Y2K Bug Seems Like a Joke—Because Those Behind the Scenes Took It Seriously . 7 June 2021 . Time Magazine . 30 December 2019 . 2021-09-30 . https://web.archive.org/web/20210930045430/https://time.com/5752129/y2k-bug-history/ . live .
    4. Leap Day Tuesday Last Y2K Worry . 25 February 2000 . Wired . 16 October 2016 . 2021-04-30 . https://web.archive.org/web/20210430175535/https://www.wired.com/2000/02/leap-day-tuesday-last-y2k-worry/ . live .
    5. News: Carrington . Damian . 4 January 2000 . Was Y2K bug a boost? . 19 September 2009 . https://web.archive.org/web/20040422221434/http://news.bbc.co.uk/2/hi/science/nature/590932.stm . 22 April 2004 . BBC News.
    6. News: Loeb . Zachary . The lessons of Y2K, 20 years later . The Washington Post . 30 December 2019 . 7 June 2021 . 2020-12-02 . https://web.archive.org/web/20201202183008/https://www.washingtonpost.com/outlook/2019/12/30/lessons-yk-years-later/ . live .
    7. News: Eric Andrew-Gee . Y2K: The strange, true history of how Canada prepared for an apocalypse that never happened, but changed us all . 28 December 2019 . . 2020-02-27 . 2020-01-01 . https://web.archive.org/web/20200101194653/https://www.theglobeandmail.com/canada/article-y2k-20th-anniversary-how-canada-prepared/ . live .
    8. Cory Johnson . 29 December 1999 . Y2K Crier's Crisis . . 2020-02-28 . 2020-02-28 . https://web.archive.org/web/20200228060318/https://www.thestreet.com/opinion/y2k-criers-crisis-839189 . live .
    9. News: Barnaby J. Feder . The Town Crier for the Year 2000 . 11 October 1998 . . 2020-02-28 . 2020-04-14 . https://web.archive.org/web/20200414133107/https://archive.nytimes.com/www.nytimes.com/library/tech/98/10/biztech/articles/11prof.html#1 . live .
    10. Computer bugs in the year 2000 . Bolles . Spencer . 19 January 1985 . net.bugs . 820@reed.UUCP . 15 August 2019 . 2011-01-22 . http://arquivo.pt/wayback/20110122130054/https://groups.google.com/forum/#!topic/net.bugs/ZGlqGwNaq3I . live .
    11. http://americanradioworks.publicradio.org/index.html American RadioWorks
    12. News: Rose . Ted . Who invented Y2K and why did it become so universally popular? . Baltimore Sun . 22 December 1999 . 2022-09-26 . 2022-09-26 . https://web.archive.org/web/20220926134950/https://www.baltimoresun.com/news/bs-xpm-1999-12-22-9912220295-story.html . live .
    13. A web search on images for "computer memory ads 1975" returns advertisements showing pricing for 8K of memory at $990 and 64K of memory at $1495.
    14. Web site: McCallum . John C. . Computer Memory and Data Storage . Global Change Data Lab . 21 October 2023 . 2022 . 2023-10-04 . https://web.archive.org/web/20231004134336/https://ourworldindata.org/grapher/historical-cost-of-computer-memory-and-storage . live .
    15. Web site: Accrued Savings of the Year 2000 Computer Date Problem . Kappelman . Leon . Scott . Phil . 25 November 1996 . Computerworld . 13 February 2017 . 18 December 2017 . https://web.archive.org/web/20171218124916/http://www.comlinks.com/mag/accr.htm . dead .
    16. http://www.cnn.com/TECH/specials/y2k/ Looking at the Y2K bug
    17. News: Piskora . Beth . The Dow decimal system . 1 March 1997 . . 26.
    18. In the beginning was the nerd . Archive on 4 . BBC Radio 4 . . 3 October 2009 . 2018-02-13 . 2009-10-13 . https://web.archive.org/web/20091013090148/http://www.bbc.co.uk/iplayer/episode/b00mz53r/Archive_on_4_In_the_Beginning_Was_the_Nerd/ . live .
    19. Book: Halvorson, Michael . Running Microsoft Office 2000 . 1999 . Microsoft Press . Young, Michael J. . 1-57231-936-4 . Redmond, Wash. . 40174922.
    20. Book: Halvorson . Michael . Running Microsoft Office 2000 Professional . Young . Michael . Microsoft Press . 1999 . 1572319364 . Redmond, WA . xxxix . "As you learn about the year 2000 problem, and prepare for its consequences, there are a number of points we’d like you to consider. First, despite dire predictions, there is probably no good reason to prepare for the new millennium by holing yourself up in a mine shaft with sizable stocks of water, grain, barter goods, and ammunition. The year 2000 will not disable most computer systems, and if your personal computer was manufactured after 1996, it's likely that your hardware and systems software will require little updating or customizing.".
    21. News: Key computer coding creator dies . 25 June 2004 . The Washington Post . 25 September 2011 . 2017-09-19 . https://web.archive.org/web/20170919091919/http://www.washingtonpost.com/wp-dyn/articles/A4138-2004Jun24.html . live .
    22. News: Andrew-Gee . Eric . Y2K: The strange, true history of how Canada prepared for an apocalypse that never happened, but changed us all . 28 December 2019 . . 2020-02-27 . 2020-01-01 . https://web.archive.org/web/20200101194653/https://www.theglobeandmail.com/canada/article-y2k-20th-anniversary-how-canada-prepared/ . live .
    23. Requirements for Internet Hosts -- Application and Support . October 1989 . Braden . Robert . Internet Engineering Task Force . 16 October 2016 . 10.17487/RFC1123 . 2009-06-26 . https://web.archive.org/web/20090626093005/http://tools.ietf.org/html/rfc1123 . live .
    24. . 15 November 1997 . Helpful Year 2000 hint . D. Kolstedt . 12.
    25. . extends .. the 23rd century . Thinking Ahead . 28 October 1996 . 8.
    26. News: Thomas . Martyn . The millennium bug was real – and 20 years later we face the same threats . The Guardian . 31 December 2019 . 8 June 2024.
    27. . 15 September 1997 . 50 . Patrizio . Andy . Visa Debits The Vendors.
    28. Web site: Microsoft Knowledge Base article 214326 . 17 December 2015 . Microsoft Support . 16 October 2016 . 2008-04-08 . https://web.archive.org/web/20080408144118/http://support.microsoft.com/kb/214326 . live .
    29. Web site: JavaScript Reference Javascript 1.2 . Sun Microsystems . 7 June 2009 . 2007-06-08 . https://web.archive.org/web/20070608035926/http://docs.sun.com/source/816-6410-10/date.htm#1194138 . live .
    30. Web site: JavaScript Reference Javascript 1.3 . Sun . 7 June 2009 . 2009-04-20 . https://web.archive.org/web/20090420003033/http://docs.sun.com/source/816-6408-10/date.htm#1194138 . live .
    31. The RISKS Digest, Volume 4 Issue 45. The Risks Digest . 2 February 1987 . 4 . 45 . Neumann . Peter G. . 2014-12-28 . 2014-12-28 . https://web.archive.org/web/20141228211038/http://catless.ncl.ac.uk/Risks/4.45.html . live .
    32. Stockton, J.R., "Critical and Significant Dates " Merlyn.
    33. A. van Deursen, "The Leap Year Problem " The Year/2000 Journal 2(4):65–70, July/August 1998.
    34. Web site: Bank of Queensland hit by "Y2.01k" glitch . 4 January 2010 . CRN . 16 October 2016 . 2010-03-15 . https://web.archive.org/web/20100315134601/http://www.crn.com.au/News/163864,bank-of-queensland-hit-by-y201k-glitch.aspx . live .
    35. Web site: Windows Mobile glitch dates 2010 texts 2016 . https://archive.today/20130119093337/http://news.cnet.com/8301-13860_3-10425455-56.html?tag=newsLatestHeadlinesArea.0%23addcomm . dead . 19 January 2013 . 5 January 2010 .
    36. Web site: Windows Mobile phones suffer Y2K+10 bug . 4 January 2010 . 4 January 2010 . https://web.archive.org/web/20131023061135/http://www.techradar.com/news/world-of-tech/windows-mobile-phones-suffer-y2k-10-bug-661062 . 23 October 2013 . dead .
    37. Web site: Bank of Queensland vs Y2K – an update . 4 January 2010 . 4 January 2010 . 8 January 2010 . https://web.archive.org/web/20100108210918/http://www.itwire.com/content/view/30308/53/ . dead .
    38. Web site: Error: 8001050F Takes Down PlayStation Network. Gizmodo. March 2010. 2020-03-16 . 2020-08-09 . https://web.archive.org/web/20200809230316/https://gizmodo.com/error-8001050f-takes-down-playstation-network-5482365. live.
    39. Web site: 2010 Bug in Germany . 5 January 2010 . RTL . fr . 16 October 2016 . 2010-01-07 . https://web.archive.org/web/20100107031050/http://www.rtlinfo.be/info/monde/europe/297916/bug-de-l-an-2010-en-allemagne-plus-de-20-millions-de-cartes-bancaires-inutilisables . live .
    40. Web site: Remember the Y2K bug? Microsoft confirms new Y2K22 issue . Sky news . 2 January 2022 . 2022-01-04 . https://web.archive.org/web/20220104040230/https://news.sky.com/story/remember-the-y2k-bug-microsoft-confirms-new-y2k22-issue-12507401 . live .
    41. Raymond B. Howard . The Case for Windowing: Techniques That Buy 60 Years. Year/2000 Journal . Mar/Apr 1998 . Windowing is a long-term fix that should keep legacy systems working fine until the software is redesigned....
    42. Web site: CNN - Top 10 Y2K fixes for your PC - September 22, 1999 . Green . Max . CNN. dead . https://web.archive.org/web/20010508054259/http://edition.cnn.com/TECH/computing/9909/22/top.y2k.idg/ . 8 May 2001.
    43. Web site: Millennium Bug Kit . dead . https://web.archive.org/web/20000411003050/http://www.idg.net/go.cgi?id=162843 . 11 April 2000.
    44. Web site: 5 May 1998 . The Year 2000 FAQ . 1 March 2020 . 2021-03-08 . https://web.archive.org/web/20210308095219/https://www-users.cs.umn.edu/~shekhar/5180/y2kfaq.txt . live .
    45. Web site: Ellen Friedman . Jerry Rosenberg . Countdown to the Millennium: Issues to Consider in the Final Year . 2020-03-01 . 2021-08-18 . https://web.archive.org/web/20210818081834/http://davidjyoung.com/cmg98/images/8PDFILES/INT4108.PDF . live .
    46. Web site: The Date Dilemma . Bridge programs such as a date server are another option. These servers handle record format conversions from two to four-digit years. . Peter Kruskopfs . . 15 March 2020 . https://web.archive.org/web/19961227162929/http://www.ibi.com/special/year2k/dilemma.html . 27 December 1996.
    47. News: Chandrasekaran . Rajiv . Rajiv Chandrasekaran . 1999-03-07 . Big Glitch at Nuclear Plant Shows Perils of Y2K Tests . en-US . . 2023-05-12 . 0190-8286 . 2023-03-14 . https://web.archive.org/web/20230314172027/https://www.washingtonpost.com/archive/politics/1999/03/07/big-glitch-at-nuclear-plant-shows-perils-of-y2k-tests/a148232f-5760-403c-bc14-b00382b6852d/ . live .
    48. News: Y2K bug rears its ugly head . 12 January 1999 . 30 December 2019 . CNN . New York . 2021-08-17 . https://web.archive.org/web/20210817124943/https://money.cnn.com/1999/01/12/technology/y2k_moneyline/ . live .
    49. News: Y2K bug strikes airports . en . 8 March 2023 . 2023-03-08 . https://web.archive.org/web/20230308141713/https://www.irishtimes.com/news/y2k-bug-strikes-airports-1.142074 . live .
    50. News: 28 November 1999 . Philly Not Fully Y2K-Ready, as 1900 Jury Notices Prove . en-US . 8 March 2023 . 2023-03-08 . https://web.archive.org/web/20230308135218/https://www.latimes.com/archives/la-xpm-1999-nov-28-mn-38339-story.html . live .
    51. News: Becket . Andy . 23 April 2000 . The bug that didn't bite . The Guardian . 7 March 2023 . 2023-03-07 . https://web.archive.org/web/20230307215949/https://amp.theguardian.com/technology/2000/apr/24/y2k.g2 . live .
    52. News: Gibbs . Thom . 19 December 2019 . The millennium bug myth, 20 years on: Why you're probably wrong about Y2K . en-GB . The Telegraph . 7 March 2023 . 0307-1235 . 2023-03-07 . https://web.archive.org/web/20230307215947/https://www.telegraph.co.uk/technology/2019/12/19/millennium-bug-myth-20-years-probably-wrong-y2k/ . live .
    53. News: Telecom Italia bills for 1900 . en . 2023-03-15 . 2023-03-15 . https://web.archive.org/web/20230315161236/https://www.irishtimes.com/business/telecom-italia-bills-for-1900-1.265241 . live .
    54. News: Fitzpatrick . Pat . 2019-11-14 . Remember Y2K? Pat Fitzpatrick remembers when we all thought planes would fall out of the sky . en . 2023-03-15 . 2023-03-15 . https://web.archive.org/web/20230315161237/https://www.irishexaminer.com/lifestyle/arid-30964190.html . live .
    55. News: Y2K Behind Credit Card Machine Failure . 3 February 2023 . 2023-02-03 . https://web.archive.org/web/20230203035608/https://archive.nytimes.com/www.nytimes.com/library/tech/99/12/biztech/articles/30credit.html . live .
    56. http://news.bbc.co.uk/1/hi/business/582007.stm Millennium bug hits retailers
    57. News: US satellites safe after Y2K glitch . 16 January 2021 . . 2021-07-01 . https://web.archive.org/web/20210701171325/http://news.bbc.co.uk/2/hi/americas/589836.stm . live .
    58. News: Y2K glitch hobbled top secret spy sats . . 2023-03-24 . 2022-09-06 . https://web.archive.org/web/20220906071051/https://www.upi.com/Archives/2000/01/12/Y2K-glitch-hobbled-top-secret-spy-sats/7671947653200/ . live .
    59. News: 2 January 2002 . Report: Y2K fix disrupts U.S. spy satellites for days, not hours. . 2023-03-24 . 2023-03-24 . https://web.archive.org/web/20230324212428/https://www.cnet.com/tech/tech-industry/report-y2k-fix-disrupts-u-s-spy-satellites-for-days-not-hours/ . live .
    60. News: Minor bug problems arise . 1 January 2000 . BBC News . 8 July 2017 . 2009-01-11 . https://web.archive.org/web/20090111155712/http://news.bbc.co.uk/1/hi/sci/tech/586620.stm . live .
    61. Web site: Japan nuclear power plants malfunction . BBC News . 31 December 1999 . 2017-10-04 . 2021-03-22 . https://web.archive.org/web/20210322134511/http://news.bbc.co.uk/2/hi/asia-pacific/585950.stm . live .
    62. News: Y2K Problem Strikes Japanese Plant . en . 4 February 2023 . 2023-02-04 . https://web.archive.org/web/20230204220441/https://apnews.com/article/cd4e26efaa079993c1a4b3507e7fac70 . live .
    63. Web site: Computer problems hit three nuclear plants in Japan . Martyn Williams . CNN . . 3 January 2000 . https://web.archive.org/web/20041207161525/http://archives.cnn.com/2000/TECH/computing/01/03/japan.nukes.y2k.idg . 7 December 2004 .
    64. News: Will Monday be the real Y2K day? . en . 7 February 2023 . 2023-02-07 . https://web.archive.org/web/20230207153722/https://www.zdnet.com/article/will-monday-be-the-real-y2k-day/ . live .
    65. News: 3 January 2000 . Y2K bug hits heating system in Korean apartments . 7 February 2023 . 2022-11-27 . https://web.archive.org/web/20221127191633/http://www.cnn.com/2000/TECH/computing/01/03/korea.heat.y2k.idg/index.html . live .
    66. News: S.Korea declares success against Y2K bug . en . 7 February 2023 . 2020-11-11 . https://web.archive.org/web/20201111195130/https://www.upi.com/Archives/2000/01/04/SKorea-declares-success-against-Y2K-bug/3543946962000/ . live .
    67. News: 3 January 2000 . World-Wide, the Y2K Bug Had Little Bite in the End . en-US . 23 February 2023 . 2023-02-23 . https://web.archive.org/web/20230223193626/https://www.wsj.com/articles/SB946859361336019593 . live .
    68. News: Reguly . Eric . Opinion: The Y2K bug turned out to be a non-event, Eric Reguly says . en-CA . The Globe and Mail . 7 February 2023 . 2023-02-07 . https://web.archive.org/web/20230207151755/https://www.theglobeandmail.com/amp/report-on-business/rob-commentary/the-y2k-bug-turned-out-to-be-a-non-event-eric-reguly-says/article765124/ . live .
    69. News: 2000-01-02 . What Y2K bug? Global computers are A-OK . en . Deseret . 2023-05-09 . 2023-05-09 . https://web.archive.org/web/20230509190216/https://www.deseret.com/2000/1/2/19551794/what-y2k-bug-global-computers-are-a-ok . live .
    70. News: 6 January 2000 . 30,000 Cash Registers In Greece Hit By Y2K Bug . 9 March 2023 . 2023-03-09 . https://web.archive.org/web/20230309193037/https://www.orlandosentinel.com/news/os-xpm-2000-01-06-0001060101-story.html . live .
    71. Book: Samuel, Lawrence R. . Future: A Recent History . 1 June 2009 . University of Texas Press . 978-0-292-71914-9 . 179 . en . 2023-02-03 . 2023-02-03 . https://web.archive.org/web/20230203042811/https://books.google.com/books?id=AQD-DAAAQBAJ&pg=PA179 . live .
    72. News: 7 March 2023 . Y2K glitch knocks out satellite spying system . en . Flight Global . 7 March 2023 . 2023-10-21 . https://web.archive.org/web/20231021143636/https://www.flightglobal.com/y2k-glitch-knocks-out-satellite-spying-system/30123.article . live .
    73. News: Y2K bug bites German opera . USA Today . https://web.archive.org/web/20000608011648/http://www.usatoday.com/life/cyber/tech/cth131.htm . 3 February 2023. 8 June 2000 .
    74. News: Y2K bug blamed for 4m banking blunder . en . 7 February 2023 . 2023-03-07 . https://web.archive.org/web/20230307192448/https://www.zdnet.com/article/y2k-bug-blamed-for-pound4m-banking-blunder/ . live .
    75. News: Allen . Frederick E. . Apocalypse Then: When Y2K Didn't Lead To The End Of Civilization . en . 2023-03-18 . 2023-03-18 . https://web.archive.org/web/20230318175807/https://www.forbes.com/sites/frederickallen/2020/12/29/apocalypse-then-when-y2k-didnt-lead-to-the-end-of-civilization/ . live .
    76. Web site: Y2K bug briefly affected U.S. terrorist-monitoring effort, Pentagon says . 2023-09-20 . www.cnn.com . 2023-04-21 . https://web.archive.org/web/20230421235656/http://www.cnn.com/2000/TECH/computing/01/05/y2k.pentagon.01/index.html . live .
    77. News: 2000-02-04 . Y2K bug bites 105-year-old . Independent Online . 2023-04-24 . 2023-04-24 . https://web.archive.org/web/20230424201146/https://www.iol.co.za/news/eish/y2k-bug-bites-105-year-old-27195 . live .
    78. News: 8 March 2023 . Pentagon Reports Failure In Satellite Intelligence System . 8 March 2023 . 2023-03-08 . https://web.archive.org/web/20230308141225/https://www.orlandosentinel.com/news/os-xpm-2000-01-02-0001020228-story.html . live .
    79. News: Wainwright . Martin . NHS faces huge damages bill after millennium bug error . 13 September 2001 . The Guardian . 25 September 2011 . UK . The health service is facing big compensation claims after admitting yesterday that failure to spot a millennium bug computer error led to incorrect Down's syndrome test results being sent to 154 pregnant women. ... . Martin Wainwright . 2021-08-18 . https://web.archive.org/web/20210818081832/https://www.theguardian.com/uk/2001/sep/14/martinwainwright . live .
    80. News: Brazil port hassled by Y2K glitch, but no delays . 2000-01-10 . Reuters . en . 2023-03-24 . 2023-03-24 . https://web.archive.org/web/20230324164135/https://www.itweb.co.za/content/mYZRXM9Pe4k7OgA8 . live .
    81. News: 3 January 2000 . Y2K bug hits traffic lights . . 2023-05-16 . 2021-09-20 . https://web.archive.org/web/20210920054712/http://dev.go-jamaica.com/gleaner/20000103/f2.html . live .
    82. Web site: Marsha Walton . Miles O'Brien . Miles O'Brien (journalist) . 1 January 2000 . Preparation pays off; world reports only tiny Y2K glitches . CNN . https://web.archive.org/web/20041207152504/http://archives.cnn.com/2000/TECH/computing/01/01/y2k.weekend.wrap/index.html . 7 December 2004.
    83. News: Leeds . Jeff . 2000-01-04 . Year 2000 Bug Triggers Few Disruptions . en-US . 2023-04-18 . 2023-04-18 . https://web.archive.org/web/20230418164329/https://www.latimes.com/archives/la-xpm-2000-jan-04-fi-50565-story.html . live .
    84. News: 5 January 2000 . Y2K bug briefly affected U.S. terrorist-monitoring effort, Pentagon says . CNN . 2023-04-18 . 2023-04-18 . https://web.archive.org/web/20230418164329/http://www.cnn.com/2000/TECH/computing/01/05/y2k.pentagon.01/index.html . live .
    85. News: Y2K Glitch Reported At Nuclear Weapons Plant . 28 January 2023 . 2023-01-28 . https://web.archive.org/web/20230128180406/https://www.orlandosentinel.com/news/os-xpm-2000-01-03-0001030016-story.html . live .
    86. News: Y2K briefly hits nuke plant. 28 March 2023. 4 January 2000. Associated Press. 2023-03-28 . https://web.archive.org/web/20230328141748/https://usatoday30.usatoday.com/life/cyber/tech/cth058.htm. live.
    87. Web site: 2000-01-07 . Y2K Council reports Y2K annoyances Computerworld . 2023-07-23 . www.computerworld.com . 2023-07-23 . https://web.archive.org/web/20230723184926/https://www.computerworld.com/article/2594261/y2k-council-reports-y2k-annoyances.amp.html . live .
    88. Web site: Davidson . Lee . 2000-01-04 . Y2K bug squashed U.S. claims victory, ends all-day operation at command center . 2023-06-09 . Deseret News . en . 2023-06-09 . https://web.archive.org/web/20230609024607/https://www.deseret.com/2000/1/4/19483895/y2k-bug-squashed-br-u-s-claims-victory-ends-all-day-operation-at-command-center . live .
    89. News: Barr . Stephen . 2000-01-03 . Y2K Chief Waiting for Market Close to Sound All-Clear . en-US . . 2023-06-18 . 0190-8286 . 2022-11-22 . https://web.archive.org/web/20221122005932/https://www.washingtonpost.com/archive/business/technology/2000/01/03/y2k-chief-waiting-for-market-close-to-sound-all-clear/5cade634-4fc7-442f-a586-f408b7b001da/ . live .
    90. News: Michaud . Chris . 2023-01-04 . Y2K bug bites into gourmet chocolates . Independent Online . 2023-06-18 . 2023-06-18 . https://web.archive.org/web/20230618173032/https://www.iol.co.za/news/world/y2k-bug-bites-into-gourmet-chocolates-24849 . live .
    91. News: S . Edmund . ERS . 7 January 2000 . Y2K Glitch Is Causing Multiple Charges for Some Cardholders . en-US . 27 January 2023 . 2023-01-27 . https://web.archive.org/web/20230127203315/https://www.latimes.com/archives/la-xpm-2000-jan-07-fi-51567-story.html . live .
    92. News: 3 January 2000 . Two glitches hit Microsoft Internet services as New Year rolls over . CNN . https://web.archive.org/web/20060211023600/http://archives.cnn.com/2000/TECH/computing/01/03/msn.bugs.y2k/index.html . dead . 2006-02-11 . 2023-04-24.
    93. HK Leap Year Free of Y2K Glitches . 29 February 2000 . Wired . 16 October 2016 . 2021-04-30 . https://web.archive.org/web/20210430125044/https://www.wired.com/2000/02/hk-leap-year-free-of-y2k-glitches/ . live .
    94. News: 29 February 2000 . Leap Day arrives with few computer glitches worldwide . en . 3 February 2023 . 2023-02-03 . https://web.archive.org/web/20230203033904/https://www.deseret.com/2000/2/29/19493414/leap-day-arrives-with-few-computer-glitches-worldwide . live .
    95. Leap Day Had Its Glitches . 1 March 2000 . Wired . 25 February 2020 . 2021-06-08 . https://web.archive.org/web/20210608203403/http://www.wired.com/2000/03/leap-day-had-its-glitches/ . live .
    96. News: 1 March 2000 . Leap Day bug infests tax system . CBC News . 7 March 2023 . 2023-03-07 . https://web.archive.org/web/20230307210827/https://www.cbc.ca/amp/1.203744 . live .
    97. News: 1 March 2000 . Computer glitches minor on Leap Day . en . 7 March 2023 . 2023-03-07 . https://web.archive.org/web/20230307205223/https://www.deseret.com/2000/3/1/19493584/computer-glitches-minor-on-leap-day . live .
    98. Web site: The last bite of the bug . BBC News . 5 January 2001 . 2014-12-31 . 2003-02-03 . https://web.archive.org/web/20030203160827/http://news.bbc.co.uk/1/hi/sci/tech/1101917.stm . live .
    99. News: 7-Eleven Systems Hit by Y2k-like Glitch . 10 March 2023 . 2023-03-10 . https://web.archive.org/web/20230310004837/https://www.computerworld.com/article/2590234/7-eleven-systems-hit-by-y2k-like-glitch.amp.html . live .
    100. News: 1 January 2001 . Y2K Bug Hits Norway's Railroad At End Of Year . en . 10 March 2023 . 2023-03-10 . https://web.archive.org/web/20230310005119/https://greensboro.com/y2k-bug-hits-norways-railroad-at-end-of-year/article_82a866cf-3046-51ce-9aae-efd2bf3abc58.html . live .
    101. Horvath . John . 2001-01-06 . Y2K Strikes Back . de . 2023-10-10 . 2023-10-21 . https://web.archive.org/web/20231021143702/https://www.telepolis.de/features/Y2K-Strikes-Back-3443163.html . live .
    102. News: Meintjies . Marvin . 11 January 2001 . Y2K glitch gives bank a new year's shock . . 2023-03-12 . 2023-03-13 . https://web.archive.org/web/20230313011710/https://www.iol.co.za/news/south-africa/y2k-glitch-gives-bank-a-new-years-shock-57251 . live .
    103. News: Valenta . Kaaren . 2001-01-04 . Tax Collector: Car Tax Bills Are Correct . en-US . The Newtown Bee . 2023-04-28 . 2023-04-28 . https://web.archive.org/web/20230428184654/https://www.newtownbee.com/01042001/tax-collector-car-tax-bills-are-correct/ . live .
    104. Web site: NASA's Deep Space Comet Hunter Mission Comes to an End . Jet Propulsion Laboratory . 20 September 2013 . 14 October 2013. https://web.archive.org/web/20131014090812/http://www.jpl.nasa.gov/news/news.php?release=2013-287 . 9 July 2022.
    105. Web site: A lazy fix 20 years ago means the Y2K bug is taking down computers now . Stokel-Walker . Chris . New Scientist . 12 January 2020 . 2020-01-12 . https://web.archive.org/web/20200112073259/https://www.newscientist.com/article/2229238-a-lazy-fix-20-years-ago-means-the-y2k-bug-is-taking-down-computers-now/ . live .
    106. Kohler . Iliana V. . Kaltchev . Jordan . Dimova . Mariana . 14 May 2002 . Integrated Information System for Demographic Statistics 'ESGRAON-TDS' in Bulgaria . Demographic Research . 6 . Article 12 . 325–354 . 10.4054/DemRes.2002.6.12 . 2011-01-15 . 2010-12-04 . https://web.archive.org/web/20101204020430/http://www.demographic-research.org/Volumes/Vol6/12/6-12.pdf . live .
    107. Web site: The personal identity code: Frequently asked questions . 29 November 2020 . Digital and Population Data Services Agency, Finland . 2020-11-26 . https://web.archive.org/web/20201126040603/https://dvv.fi/en/personal-identity-code . live .
    108. Web site: Uganda National Y2k Task Force End-June 1999 Public Position Statement . 30 June 1999 . 11 January 2012 . 2012-08-10 . https://web.archive.org/web/20120810202528/http://parsifal.membrane.com/y2k/y2kugand.htm . live .
    109. Web site: Y2K Center urges more information on Y2K readiness . 3 August 1999 . 11 January 2012 . 2013-06-03 . https://web.archive.org/web/20130603025515/http://greenspun.com/bboard/q-and-a-fetch-msg.tcl?msg_id=001BVY . live .
    110. Web site: Year 2000 Information and Readiness Disclosure Act . FindLaw . 14 May 2019 . 2019-05-13 . https://web.archive.org/web/20190513214022/https://corporate.findlaw.com/law-library/year-2000-information-and-readiness-disclosure-act.html . live .
    111. Web site: Y2K bug: Definition, Hysteria, & Facts . 10 May 2019 . Encyclopædia Britannica . 14 May 2019 . 2019-05-20 . https://web.archive.org/web/20190520140100/https://www.britannica.com/technology/Y2K-bug . live .
    112. News: DeBruce . Orlando . White House shifts Y2K focus to states . 23 February 1999 . 16 October 2016 . CNN . Jones . Jennifer . 2006-12-20 . https://web.archive.org/web/20061220052945/http://www.cnn.com/TECH/computing/9902/23/shift.y2k.idg/ . live .
    113. Web site: The President's Council on Year 2000 Conversion . Atlee . Tom . Tom Atlee . The Co-Intelligence Institute . 14 May 2019 . 2021-03-08 . https://web.archive.org/web/20210308051834/https://www.co-intelligence.org/y2k_presidentscomm.html . live .
    114. Web site: FCC Y2K Communications Sector Report (March 1999) copy available at WUTC . 29 May 2007 . https://web.archive.org/web/20070605072208/http://www.wutc.wa.gov/webdocs.nsf/b8da29aede8fdd67882571430005a9c1/c1cf57ff131085ca88256744007e1440/$FILE/Y2kcsr.pdf . 5 June 2007 . dead.
    115. Web site: Statement by President on Y2K Information and Readiness . Clinton Presidential Materials Project . National Archives and Records Administration . 19 October 1998 . 2020-03-16 . 2020-04-14 . https://web.archive.org/web/20200414204939/https://clintonwhitehouse6.archives.gov/1998/10/1998-10-19-statement-by-president-on-y2k-information-and-readiness.html . live .
    116. Web site: Home . National Y2K Clearinghouse . . 16 March 2020 . dead . https://web.archive.org/web/20001205223500/http://www.y2k.gov/ . 5 December 2000.
    117. Web site: Federal Communications Commission Spearheads Oversight of the U.S. Communications Industries' Y2K Preparedness . Robert J. Butler . Anne E. Hoge . . September 1999 . The Open Group . https://web.archive.org/web/20081009053904/http://www.opengroup.org/comm/the_message/magazine/mmv5n5/view.htm . 9 October 2008 . 16 October 2016 . dead . Messaging Magazine.
    118. Web site: Basic Internet Structures Expected to be Y2K Ready, Telecom News, NCS (1999 Issue 2) . 2007-05-29 . 2007-05-08 . https://web.archive.org/web/20070508044227/http://www.ncs.gov/library/telcom/tn_99-02.pdf . dead .  
    119. News: U.S., Russia Shutter Joint Y2k Bug Center . 16 January 2000 . Chicago Tribune . 28 January 2017 . 2017-02-02 . https://web.archive.org/web/20170202051942/http://articles.chicagotribune.com/2000-01-16/news/0001160164_1_missile-peterson-air-force-base-y2k . live .
    120. Web site: Collection: International Y2K Cooperation Center records | University of Minnesota Archival Collections Guides. archives.lib.umn.edu. 2020-03-16 . 2019-09-08 . https://web.archive.org/web/20190908211458/https://archives.lib.umn.edu/repositories/3/resources/567. live.
    121. Kirsner . Scott . 1 November 1997 . Fly in the Legal Eagles . . 38.
    122. Web site: quetek.com . quetek.com . 25 September 2011 . 28 August 2011 . https://web.archive.org/web/20110828101722/http://www.quetek.com/dictionary/y2k-scare.html . dead .
    123. http://www.cybertelecom.org/year2000/ Internet Year 2000 Campaign
    124. Web site: My Y2K—A Personal Statement . Kunstler . Jim . 1999 . Kunstler, Jim . 12 December 2006 . https://web.archive.org/web/20070927062527/http://kunstler.com/mags_y2k.html . 27 September 2007 . dead .
    125. Web site: False Prophets, Real Profits - Americans United . 9 November 2016 . 27 September 2016 . https://web.archive.org/web/20160927030808/https://www.au.org/church-state/february-2000-church-state/featured/false-prophets-real-profits . dead .
    126. News: Dutton . Denis . 31 December 2009 . . It's Always the End of the World as We Know It . Denis Dutton . 2017-02-26 . 2017-02-27 . https://web.archive.org/web/20170227201715/http://www.nytimes.com/2010/01/01/opinion/01dutton.html . live .
    127. Coen, J., 1 March 1999, "Some Christians Fear End, It's just a day to others" Chicago Tribune
    128. Hart, B., 12 February 1999 Deseret News, "Christian Y2K Alarmists Irresponsible" Scripps Howard News Service
    129. Book: Smith, B. . 1999 . I Spy with my Little Eye . MS Life Media . chapter 24 - Y2K Bug . dead . https://web.archive.org/web/20161106064238/http://www.barrysmith.org.nz/site/books/ . 6 November 2016.
    130. Web site: Col Stringer Ministries - Newsletter Vol.1 : No.4 . 9 November 2016 . https://web.archive.org/web/20120320060233/http://www.colstringer.com/information/newsletters/vol-1-no-4.html . 20 March 2012 . dead .
    131. Rivera, J., 17 February 1999, "Apocalypse Now – Y2K spurs fears", The Baltimore Sun
    132. Web site: Washingtonpost.com: Business Y2K Computer Bug . 2023-09-27 . www.washingtonpost.com . 2012-12-19 . https://web.archive.org/web/20121219133240/http://www.washingtonpost.com/wp-srv/business/longterm/y2k/stories/consumer_faith.htm . live .
    133. News: Y2K: Overhyped and oversold? . 6 January 2000 . 2006-02-02 . 2020-02-28 . https://web.archive.org/web/20200228060317/http://news.bbc.co.uk/2/hi/talking_point/586938.stm . live .
    134. Web site: Y2K: The good, the bad and the crazy . Mitchell . Robert L. . 28 December 2009 . Computerworld . 2010-12-19 . 2010-01-01 . https://web.archive.org/web/20100101122535/http://www.computerworld.com/s/article/9142555/Y2K_The_good_the_bad_and_the_crazy?taxonomyId=14&pageNumber=2 . live .
    135. which was well underway by 1996: News: Tharp . Paul . Millennium Milllionairs: Counting past 2000; Mainframe mavens make their return . 2 December 1996 . . 27.
    136. News: . A Mini-Y2K Looms, and Other Blips . systems that automate the distribution of software fixes, called patches . David S. Joachim . 1 May 2006 . 2020-04-08 . 2021-03-08 . https://web.archive.org/web/20210308153029/https://www.nytimes.com/2006/05/01/business/smallbusiness/01tech.html . live .
    137. https://clarotesting.wordpress.com/2015/01/12/y2k-why-i-know-it-was-a-real-problem/ James Christie, (12 January 2015), Y2K – why I know it was a real problem, 'Claro Testing Blog'
    138. http://web.mit.edu/newsoffice/2002/terror-1120.html Y2K readiness helped New York after 9/11
    139. Web site: Finance & Development, March 2002 - September 11 and the U.S. Payment System . Finance and Development - F&D . 2006-10-30 . 2007-04-26 . https://web.archive.org/web/20070426234851/http://www.imf.org/external/pubs/ft/fandd/2002/03/cumming.htm . live .
    140. Goldberg . Michael . The Next Time the Lights Go Out . 13 October 2003 . . Carr . Kathleen . 2020-10-25 . 2023-10-21 . https://web.archive.org/web/20231021143647/https://books.google.com/books?id=ig0AAAAAMBAJ&q=y2k+9%2F11+blackout+banking&pg=PP1#v=snippet&q=y2k%209%2F11%20blackout%20banking&f=false . live .
    141. http://web.mit.edu/newsoffice/2002/terror.html Y2K readiness helped NYC on 9/11
    142. News: Doward . Jamie . Russia Y2K bill 'shows West overreacted' . 9 January 2000 . . 2022-08-31 . 2022-08-31 . https://web.archive.org/web/20220831053832/https://www.theguardian.com/business/2000/jan/09/y2k.observerbusiness . live .
    143. Web site: Elizabeth Weise . Lights out? Y2K appears safe . . 14 February 1999 . 2006-05-14 . 2023-10-21 . https://web.archive.org/web/20231021143637/https://www.cincinnati.com/ . live .
    144. Web site: John Quiggin . 2 September 1999 . Y2K bug may never bite . Australian Financial Review . 29 December 2009 . https://web.archive.org/web/20080524084926/http://www.uq.edu.au/economics/johnquiggin/news/Millennium9908.html . 2008-05-24 . dead.
    145. .
    146. https://web.archive.org/web/20060506133440/http://eschoolnews.com/news/showstory.cfm?ArticleID=404 White House: Schools lag in Y2K readiness: President's Council sounds alarm over K-12 districts' preparations so far
    147. Web site: Hoover . Kent . Most small businesses win their Y2K gamble . 9 January 2000 . . 2013-09-20 . 2013-09-21 . https://web.archive.org/web/20130921055908/http://www.bizjournals.com/seattle/stories/2000/01/10/newscolumn5.html?page=all . live .
    148. Web site: Oreskovic . Alexei . 19 July 2024 . The ghost of Y2K just struck back. 21 July 2024 . . en-US.
    149. Web site: Palus . Shannon . 19 July 2024 . Crowdstrike meltdown, airlines: The glitch feels like Y2K lite. . 21 July 2024 . . en-US.

    This article is licensed under the GNU Free Documentation License. It uses material from the Wikipedia article "Year 2000 problem".

    Except where otherwise indicated, Everything.Explained.Today is © Copyright 2009-2024, A B Cryer, All Rights Reserved. Cookie policy.