A new podcast from Teller's Tech

It worked yesterday.

True stories about the day a system failed, and what was really going on underneath.

With Brian TellerOne true story an episode

System messageEpisode 1

This is not a drill.

Phones across Hawaii. One message. Thirty-eight minutes to take it back.

The show

If you've ever told someone “it worked yesterday,” these stories are for you.

  1. The moment it broke

    Where people were, what they saw, and the minute everything changed.

  2. How it really works

    The machinery underneath, in plain language.

  3. The decision in the middle

    The person, the pressure, and the choice they made.

  4. What I take from it

    What one failure says about the systems we all depend on.

  • One true storyEvery episode stands on its own.
  • No engineering degreeYou only need to have used the thing.
  • Every source linkedCheck the story yourself.
Episode cover: a dialog box that reads This is not a drill, with Brian Teller.

Episode 1 Hawaii, 2018

This is not a drill.

January 13, 2018. Phones across Hawaii get the same message: a ballistic missile is inbound, seek shelter, this is not a drill.

There is no missile. It takes thirty-eight minutes to say so. The official explanation was that an employee pushed the wrong button. That isn't what happened.

In production. Not released yet.

  • Apple PodcastsAt launch
  • SpotifyAt launch
  • RSSAt launch

From the record

Thirty-eight minutes.

Sending the alert took seconds. This is everything that happened before anyone could take it back.

  1. A drill begins

    During shift change, a supervisor starts a no-notice missile drill by calling the warning officers from a secure phone.

  2. The alert goes out

    A warning officer picks the live template and confirms. Phones across Hawaii begin to receive it.

  3. It reaches the sender

    The alert arrives on the phone of the officer who sent it.

  4. The governor is told

    The state adjutant general tells Governor Ige the alert is false.

  5. No launch

    The adjutant general tells U.S. Pacific Command there was no launch, confirming what it already knew.

  6. Cancelled, but not corrected

    The agency stops further transmission. Phones already showing the alert get no all-clear.

  7. The phone lines jam

    Calls from the public keep the agency's lines congested until 8:26.

  8. The estimated moment of impact

    Had a missile been real, the Associated Press timeline puts impact at about this minute.

  9. The first public word

    The agency posts on Twitter: "NO missile threat to Hawaii." Facebook follows at 8:23.

  10. The governor retweets it

    Fifteen minutes after he was told.

  11. A meeting

    Staff meet to work out what kind of message a correction should be.

  12. Two calls to FEMA

    The first goes unanswered. The second reaches someone on a mobile phone, and they agree on the message type in 45 seconds.

  13. Writing the correction

    A deputy chief logs in to the alert software and builds it. That takes until 8:44.

  14. The correction goes out

    Thirty-eight minutes after the alert. The version sent to TV and radio has no audio.

The prompt, reconstructed

Confirm

Are you sure that you want to send this Alert?

The software asked this same question for a test and for the real thing, and it never showed the message about to go out. The wording is from the FCC's report. The window is our illustration.

To send it

One person. One menu. One click.

To take it back

A meeting. Two phone calls. Thirty-eight minutes.

Brian Teller

Your host

Brian Teller

Brian has spent his career as the person who gets called when a system breaks.

Have a story about the day something broke?

Send it to Brian