PH Peter Haralambas On Start Here

“Imagine a faulty thermostat. It's not necessarily like your car's overheating, but your car's computer system thinks it's overheating and it's shutting itself down, and it's creating issues for you.”

Start Here · Policy · November 2026

“Imagine a faulty thermostat. It's not necessarily like your car's overheating, but your car's computer system thinks it's overheating and it's shutting itself down, and it's creating issues for you.” — Peter Haralambas, Start Here

Context

Explaining the Microsoft 365 outage, Peter says servers were failing automated health checks and being pulled off the network. This is his analogy for that failure.

Transcript

Start Here Around 18:10 into the episode
Speaker 3

…extent to which email is integral to basically all of our news gathering operations. But I will say, not getting emails for six hours really gave me some time to look into this, to try to figure out what went wrong here and how bad it could have theoretically been in terms of just this disruption.

Devin Dwyer

…stuff, said 74 countries and territories had Microsoft users reporting the loss of service in just over an hour. It's a pretty broad scope, right? And in the middle of this are not just you and me, but governments, hospitals, healthcare services. A lot of people rely on Microsoft email services.

Speaker 3

That's right. The federal government relies on Outlook for daily operations. Healthcare systems were deeply disrupted by this. News organizations like us, too, were impacted. And I think one thing that added to the frustration for people was the lack of communication from Microsoft for hours. We're talking about these weird piecemeal updates we were getting through their X account mainly that were kind of complicated technically. They didn't really make much sense. A lot of us were trying to parse them here in the newsroom to figure out: does this mean they were hacked? Were they not hacked? Does it mean it's getting better? Does this mean it's getting worse? And I've probably spent maybe three hours at this point staring at this chain of messages, trying to understand what the technical terms mean. I'm still not 100% sure what Microsoft was trying to convey in terms of how this actually happened.

Devin Dwyer

Yeah, there's a lot of jargon coming out of the sole mouthpiece at Microsoft on X, as you said. I mean, I was looking at one here. They said yesterday's outage was not caused by any recent change, but our investigation indicates the failed health checks may originate from a specific component…

Speaker 3

Yeah, a somewhat catastrophic mistake or some kind of error. Yes, really technical, obtuse description from them. They basically came out the gate and acknowledged. We know people are having issues. At first, they basically said that their servers were overloaded, that something was driving…

Devin Dwyer

Yeah, and it seems those issues could even be a matter of life and death. I mean, New York City Emergency Management put out an alert yesterday saying the Microsoft problems were causing delays or temporary service disruptions from some city agencies, telling people to call 911 for urgent requests.…

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.

More from Start Here