Editing article

Title

Summary

Content

<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ohLjzpaESYZ_V6fr.jpg" /></figure>Can you imagine the sort of worldwide panic that would ensue if everyone’s smart phone suddenly stopped working? Something analogous happened thirty years ago when, on January 15, 1990, the entire US long-distance telephone network crashed for nine hours.<blockquote>This was a strange, dire, huge event. During the nine long hours of frantic effort that it took to restore service, some seventy million telephone calls went uncompleted.</blockquote>I was working at Bell Labs at the time, which was a subsidiary of AT&amp;T. Limited and isoated failures, akin to modern outages in your ISP’s internet service, were relatively common in those days, however, this sort of ubiquitous and sustained service breakdown taking out the entire network was unprecedented.<blockquote>Bell Labs engineers, working feverishly in New Jersey, Illinois, and Ohio, first tried their entire repertoire of standard network remedies on the malfunctioning System 7. None of the remedies worked, of course, because nothing like this had ever happened to any phone system before.</blockquote>Perhaps the most interesting aspect of the story: the crash of Janurary 15, which happened to be Martin Luther King Day, was not caused by Russian agents, cybercriminals, or hackers. The entire calamity was caused by one line of errant code, written by one very unlucky programmer.<blockquote>As it happened, the problem itself — the problem per se — took this form. A piece of telco software had been written in C language, a standard language of the telco field. Within the C software was a long “do… while” construct. The “do… while” construct contained a “switch” statement. The “switch” statement contained an “if” clause. The “if” clause contained a “break.” The “break” was supposed to “break” the “if clause.” Instead, the “break” broke the “switch” statement.</blockquote>Read the whole amazing story in the article linked below.<blockquote>On January 15, 1990, AT&amp;T’s long-distance telephone switching system crashed. <a href="http://www.mit.edu/hacker/part1.html">http://www.mit.edu/hacker/part1.html</a></blockquote>Originally published at <a href="https://mco.dev/the-big-crash/">https://mco.dev</a> on November 19, 2020.<img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d68599693e22" width="1" height="1" alt="">

Author

Link

Published date

Image url

Feed url

Guid

Hidden blurb

--- !ruby/object:Feedjira::Parser::RSSEntry
title: The Big Crash
url: https://marcacohen.medium.com/the-big-crash-d68599693e22?source=rss-1f225b5f22b2------2
author: Marc Cohen
categories:
- history
- history-of-technology
- crash
published: 2020-11-19 00:00:00.000000000 Z
entry_id: !ruby/object:Feedjira::Parser::GloballyUniqueIdentifier
 is_perma_link: 'false'
 guid: https://medium.com/p/d68599693e22
carlessian_info:
 news_filer_version: 2
 newspaper: Marc Cohen - Medium
 macro_region: Blogs
rss_fields:
- title
- url
- author
- categories
- published
- entry_id
- content
content: '<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ohLjzpaESYZ_V6fr.jpg"
 /></figure>Can you imagine the sort of worldwide panic that would ensue if everyone’s
 smart phone suddenly stopped working? Something analogous happened thirty years
 ago when, on January 15, 1990, the entire US long-distance telephone network crashed
 for nine hours.<blockquote>This was a strange, dire, huge event. During
 the nine long hours of frantic effort that it took to restore service, some seventy
 million telephone calls went uncompleted.</blockquote>I was working at Bell
 Labs at the time, which was a subsidiary of AT&amp;T. Limited and isoated failures,
 akin to modern outages in your ISP’s internet service, were relatively common in
 those days, however, this sort of ubiquitous and sustained service breakdown taking
 out the entire network was unprecedented.<blockquote>Bell Labs engineers,
 working feverishly in New Jersey, Illinois, and Ohio, first tried their entire repertoire
 of standard network remedies on the malfunctioning System 7. None of the remedies
 worked, of course, because nothing like this had ever happened to any phone system before.</blockquote>Perhaps
 the most interesting aspect of the story: the crash of Janurary 15, which happened
 to be Martin Luther King Day, was not caused by Russian agents, cybercriminals,
 or hackers. The entire calamity was caused by one line of errant code, written
 by one very unlucky programmer.<blockquote>As it happened, the
 problem itself — the problem per se — took this form. A piece of telco software
 had been written in C language, a standard language of the telco field. Within the
 C software was a long “do… while” construct. The “do… while” construct contained
 a “switch” statement. The “switch” statement contained an “if” clause. The “if”
 clause contained a “break.” The “break” was supposed to “break” the “if clause.”
 Instead, the “break” broke the “switch” statement.</blockquote>Read the
 whole amazing story in the article linked below.<blockquote>On January 15,
 1990, AT&amp;T’s long-distance telephone switching system crashed. <a href="http://www.mit.edu/hacker/part1.html">http://www.mit.edu/hacker/part1.html</a></blockquote>Originally
 published at <a href="https://mco.dev/the-big-crash/">https://mco.dev</a>
 on November 19, 2020.<img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d68599693e22"
 width="1" height="1" alt="">'

Language

Active

Ricc internal notes

Ricc source

Show this article Back to articles