Wire Service FAILURE to report: 1) numerous Best Buy stores closed or only operating one or two registers despite very long lines; 2) VISA unable to access their own or customer accounts; 3) all 7-11 stores computers with system date of 1901; 4) AT&T Digital Cable re-providing viewing schedule with November dates; 5)Story printed from ZDNet Australia [not Wire Service], http://www.zdnet.com.au/news/dailynews/story/0,2000011358,20107955,00.htm. ATM and EFTPOS services outage Australiawide; 6) electrical grid failures; 7) railroad routing failures; 8) explosions; 9) smoke in cockpits; 10) water main breaks; 11) pipeline breaks; 12) ships sinking; 13) ... Any one else noticed ramping on of these non-events?

-- Crypto Byte (cryptobyte@hotmail.com), January 03, 2001

Answers

Yes. The wires I've been monitoring for a year are suddenly showing almost none of these. Does it mean they're still happening but now not being picked-up by the wires? (See my comment on the India power outage thread.)

-- Rachel Gibson (rgibson@hotmail.com), January 03, 2001.

I don't think there is any conspiracy of silence on the part of the media or government officials at this point in time. At least, there are no "would be" "conspirators" around that I know of. In order to be part of a conspiracy, one would have to be a basic understanding of the possibility of there being a Y2K or date-related problem connected with the problems that are continuing to occur. Those reporting the Norwegian railway problems reported in the first days of 2001 did make the connection. That other reporters or public officials elsewhere do not seem to be even raising the possibility of such a cause-effect relationship involving other anomalies can be chalked up to a simple lack of technical knowledge coupled with an absence of interest. To my knowledge, there is no one in the Federal government tracking the possible connection between Y2K or other date sensitive embedded system or complex integrated system- related problems and the anomalies that have occurred since February and March of the Year 2000. This includes the anomalies that have just occurred in the past few days. Even when the President's Council's Information Coordination Center was functioning and fully staffed (including at the time of the rollover and during the first part of January of 2000), there was scant expertise available or enlisted to identify, track, and assess anomalies that could have been related to embedded system and complex integrated system malfunctions and failures. ICC relied on information reported they received from others. There were (and still are) innumerable legal, economic, accountability-related, insurance-related, job security- related, and other disincentives that seem to make unlikely the full and open disclosure of problems by those closest to the problems. There are also those who are experiencing the problems who may also lack the technical expertise to recognize and assess their causes. I am attaching some previously posted threads that contains some still pertinent perspectives on what has happened and is still happening. Summary of a Slide Presentation ~ April 12, 2000 GW Panel Program on Y2K & Embedded Systems greenspun.com : LUSENET : Grassroots Information Coordination Center (GICC) : One Thread ---------------------------------------------------------------------- ----------

The following is a summary of a slide presentation that I gave at a panel program on Y2K on April 12, 2000. The topic of the program was "Y2K: What Happened and What Has Been Happening Since January 1?" A video of all of the panel presentations can be seen at http://www.stuarthrodman.com/video.htm Additional information concerning the panel and other presentations and programs can be found at http://www.gwu.edu/~y2k/keypeople/gordon. I hope it may prove helpful to those trying to sort out some of the "unsolved mysteries" of the Y2K story. Summary of Slide Presentation by Paula Gordon Given at an April 12, 2000 Panel Program at GW University Entitled "Y2K: What Happened and What Has Been Happening Since January 1?"

Topic Outline:

I. Some Problems in Obtaining Information Concerning Y2K-Related Problems

II. Some Mainstream Sources (or Potential Sources) of Information

III. A Basis for Making a Case That Y2K Problems Have Occurred and Are Continuing to Occur

IV. Reasons for the Use of Anonymous or Unnamed Sources

V. Why We Are Likely to Know More Soon

VI. The Need to Understand That Embedded Systems Failures and Malfunctions Can Occur or Become Evident at Different Times

VII. Some Sources of Information of Potential Interest

I. Some Problems in Obtaining Information Concerning Y2K-Related Problems

1) There is information that has not yet been made available.

2) Some of the information that is available is lacking in details and/or is impossible or difficult to trace or verify.

3) Some information was made available only briefly owing to proprietary concerns or for other reasons such as lack of funding.

4) Some information is accessible but may be very difficult to find.

5) Some information is in a form that makes it difficult to use. 6) Some information may require special direct requests.

II. Some Mainstream.Sources (or Potential Sources) of Information

~ The Information Coordination Center (ICC)

~ The International Y2K Coordination Center (IY2KCC)

~ Nuclear Regulatory Commission (NRC)

~ Environmental Protection Agency (EPA)

~ Chemical Safety Board

~ State of California

III. A Basis for Making a Case That Y2K Problems Have Occurred and Are Continuing to Occur

What basis might there be for concluding that problems that are occurring are Y2K-related?

If problems in question meet the following criteria, there is a basis for at least tentatively concluding that the problems could be Y2K- or embedded systems-related:

1) High Number of Problems:

An usually high number of problems in a specific sector having no readily identifiable causes and/or having causes that could be Y2K- or embedded systems related

2) Number of Problems in a Specific Sector is Higher Than Prior Years:

The number of problems occurring in 2000 exceeds the number of problems that occurred during comparable periods of time in prior years

3) Patterns or Similarities in Current Problems:

The problems occurring during 2000 have patterns in common and have similarities not found in problems that occurred in prior years. In addition, the problems that have been occurring are typically associated with Y2K- or embedded systems-related problems.

4) The Problems That Are Occurring Were of a Kind that Were Predicted or Expected:

The problems occurring in 2000 were anticipated or predicted or regarded as being possible or likely consequences of Y2K- or embedded systems-related failures or malfunctions.

If all of these criteria are met, then there is a likelihood that the problems are Y2K- or embedded systems-related. Such problems can at least be regarded as falling under the heading of "Predicted Coincidences".

In Other Words:

When it can be established that there has been a higher than usual number of problems in a specific sector, including problems that either have no readily identifiable cause or problems that could conceivably have a Y2K- or embedded systems-related cause;

when, in addition, a comparison of current problems with problems that occurred during the same time frame in previous years reveals patterns or similarities that are not apparent in problems that have occurred in prior years;

when such patterns or similarities either indicate or do not exclude the possibility of Y2K- or embedded systems-related causes; and

when the kinds of problems that are occurring now are the same kinds of problems that were expected to result from Y2K- or embedded systems related failures or malfunctions;

then there is a likelihood that the problems are Y2K- or embedded systems-related.

Such problems can at least be characterized as "Predicted Coincidences".

IV. Reasons for the Use of Anonymous or Unnamed Sources

There are many people who are in a position to provide needed information or expertise concerning Y2K and embedded systems who feel little, if any inclination to do so. In their minds, the disincentives to being forthcoming concerning problems or issues relating to Y2K- and embedded systems- related problems may far outweigh any possible incentives. The following is a list of some major reasons that individuals may refrain from speaking out or may request anonymity when they do:

~ Fear of losing a job, jeopardizing a contract, or otherwise adversely affecting ones career or business

~ Liability concerns or fear of litigation

~ Fear of other possible consequences or reprisals

~ Existence of Non-Disclosure Agreements preventing the sharing of proprietary information

~ Organizational or peer pressure

~ Political pressure

~ A desire to avoid controversy

~ The existence of a climate that can prove hostile to people who are candid about sensitive or controversial Y2K- and embedded systems- related concerns

For some of these and other reasons, it has been necessary for me to promise anonymity to a number of sources who have provided me information.

V. Why We Are Likely to Know More Soon

~ Quarterly Reports

~ End of Fiscal Year Reports

~ Market Analyses

~ SEC Filings

~ Insurance Claims

~ Quarterly and Annual Reports of Insurance Companies and Reinsurers

~ Law Suits, including any of the following:

- Directors and Officers, vendors, manufacturers, contractors, insurance companies, or other businesses

- Whistleblowing Cases

- Dismissed Employees Suing Employers

VI. The Need to Understand That Embedded Systems Failures and Malfunctions Can Occur at Different Times

Some examples include :

~ Buffer Overflow-Related Problems

~ Function Overflow-Related Problems

~ Problems Triggered by Annual Maintenance Scheduling

~ Epoch Date-Related Problems

For some background on the first three, see the appendices focusing on embedded systems concerns in "John Koskinen's Responses to Questions from Paula Gordon: March 22, 2000" at http://www.gwu.edu/~keypeople/gordon/Q&A.html

VII. Some Sources of Information of Potential Interest

~ Final Senate Report

~ March 29, 2000 Final Report of the Presidents Council

~ January 17 Comments and Impact Ratings by Paula Gordon http://www.gwu.edu/~keypeople/gordon

~ John Koskinen's Responses to Questions from Paula Gordon: March 22, 2000 http://www.gwu.edu/~keypeople/gordon/Q&A.html

~ Proceedings of the January 24 - 25, 2000 Y2K Assessment Conference Sponsored by the Center for Global Security Research, Lawrence Livermore National Laboratory

~ Grassroots Information Coordination Center

~ Glitch Central

For URLs not indicated, see

~ the reference list in http://www.gwu.edu/~keypeople/gordon/Q&A.html and

~ the references in the January 17 Comments and Rating piece at http://www.gwu.edu/~y2k/keypeople/gordon

Additional References

Nuclear Power Sector: for the archives http://www.greenspun.com/bboard/q-and-a-fetch-msg.tcl?msg_id=003Vyr Energy Sector - for the archives http://www.greenspun.com/bboard/q-and-a-fetch-msg.tcl?msg_id=003VxC Energy Sector postings - for the archives http://www.greenspun.com/bboard/q-and-a-fetch-msg.tcl?msg_id=003Vyf Brazil Oil Spill: for the archives http://www.greenspun.com/bboard/q-and-a-fetch-msg.tcl?msg_id=003VzX Railway incidents - for the archives http://www.greenspun.com/bboard/q-and-a-fetch-msg.tcl?msg_id=003Vzi Australian aviation fuel problem - for the archives http://www.greenspun.com/bboard/q-and-a-fetch-msg.tcl?msg_id=003Vzp Y2K Malfunctions in Nuke Plants - for the archives http://www.greenspun.com/bboard/q-and-a-fetch-msg.tcl?msg_id=003W00 Explosions and Fires Summary - for the archives http://www.greenspun.com/bboard/q-and-a-fetch-msg.tcl?msg_id=003W0O Venezuelan and other energy sector problems - for the archives http://www.greenspun.com/bboard/q-and-a-fetch-msg.tcl?msg_id=003W04 Energy Sector concerns - for the archives http://www.greenspun.com/bboard/q-and-a-fetch-msg.tcl?msg_id=003W0K Insurance and legal concerns - for the archives http://www.greenspun.com/bboard/q-and-a-fetch-msg.tcl?msg_id=003W09 Plant and pipeline explosions - for the archives http://www.greenspun.com/bboard/q-and-a-fetch-msg.tcl?msg_id=003W0A Airplane related concerns - for the archives http://www.greenspun.com/bboard/q-and-a-fetch-msg.tcl?msg_id=003W0G International glitches - for the archives http://www.greenspun.com/bboard/q-and-a-fetch-msg.tcl?msg_id=003W0Z Senate Y2K Committee Report 2/29/2000 for the archives http://www.greenspun.com/bboard/q-and-a-fetch-msg.tcl?msg_id=003W2r Oil accidents and problems - for the archives http://www.greenspun.com/bboard/q-and-a-fetch-msg.tcl?msg_id=003W2v Refinery problems contributing to spike in fuel prices - for the archives http://www.greenspun.com/bboard/q-and-a-fetch-msg.tcl?msg_id=003W3H Oil sector and railroad derailments - for the archives http://www.greenspun.com/bboard/q-and-a-fetch-msg.tcl?msg_id=003W35 Pipeline breaks - for the archives http://www.greenspun.com/bboard/q-and-a-fetch-msg.tcl?msg_id=003W8b Oil Refinery Concerns - for the archives http://www.greenspun.com/bboard/q-and-a-fetch-msg.tcl?msg_id=003Vze Airline Sector Postings for the archives http://www.greenspun.com/bboard/q-and-a-fetch-msg.tcl?msg_id=003VzL Energy sector items - for the archives http://www.greenspun.com/bboard/q-and-a-fetch-msg.tcl?msg_id=003W9U Miscellaneous sources of information re Y2K - for the archives http://www.greenspun.com/bboard/q-and-a-fetch-msg.tcl?msg_id=003W9N

-- Paula Gordon (pgordon@erols.com), January 03, 2001.