
Grok Bot is Like Pac-Man and The Electricity is The Dots
November 13, 2026
You Can’t Sweep Back the Tide of AI
November 14, 2026Free Audiovisual Version Here

By C. Rich
Somewhere, a Microsoft customer probably tried to email a colleague to ask whether Outlook was down, then opened Teams to discuss why the email wouldn’t send. Perhaps they asked Copilot for help and discovered that the assistant was having trouble, too. At that point, the most advanced productivity ecosystem in human history had successfully recreated the experience of standing outside a locked office.
Microsoft’s sprawling service outage began Thursday, November 12, disrupting Outlook and other Microsoft 365 services and dragging into early Friday. Businesses and government agencies around the world experienced communications problems. Features across Teams, SharePoint and Copilot were among those affected. Suddenly, quite a few people were reminded that their workplace lives somewhere they cannot physically walk into and yell at anybody.
We call that place “the cloud,” which remains one of the greatest branding achievements in commercial history. Clouds are soft, graceful things floating across a blue sky. Nobody pictures a building full of hot equipment, power cables, cooling machinery and exhausted engineers wondering why the fix stopped working the moment customers returned.
But the cloud has a basement. This week, the basement made the news.
Microsoft’s account of the disruption described servers becoming unexpectedly unavailable, shifting their workload onto the remaining infrastructure. The company subsequently identified an overwhelmed process responsible for establishing secure connections. Some servers brought back into service became unresponsive again when traffic returned.
Imagine reopening a supermarket checkout lane, watching every customer rush toward it, and seeing the cashier climb out through the ceiling. Now imagine your company’s email depends on getting that cashier back down.
The engineers deserve sympathy. Troubleshooting a system that behaves until people use it sounds like a special punishment designed by someone who once worked in technical support.
The rest of us deserve a moment to consider what we have built.
For years, businesses have been encouraged to bring everything together. Put the documents here. Put the conversations here. Connect the calendars, meetings, security tools and workflows. Then add an intelligent assistant that can reach across the whole arrangement and help everybody work faster.
There is real value in that. An assistant becomes more useful when it can find the document, understand the meeting and help answer the email. Integration is part of what makes these tools exciting.
It also means several impressive doors can open into the same flooded basement.
A company might believe it has multiple ways to keep working because it has email, workplace messaging, shared documents and an SI assistant. Yet this outage illustrates how functions across those services can depend on common infrastructure. Microsoft’s incident description specifically identified effects on features that interact with Exchange Online and email services.
Having four applications does not necessarily mean having four independent escape routes. Sometimes it means having four attractive icons that deliver the same bad news.
That matters even more as we give intelligent systems larger roles in daily operations. We want assistants that schedule, research, coordinate and carry out work. Eventually, losing access to one could feel less like losing a convenient chatbot and more like arriving at work to discover that half the staff cannot get through the front door.
The smarter the service becomes, the more work we will naturally entrust to it. That makes the infrastructure underneath it increasingly consequential.
I love these tools. I want them to improve. I want the assistants to become capable enough to take the tedious machinery of daily life off our hands. But the industry’s enthusiasm for showing us what they can do should be matched by its determination to keep them available when everybody actually wants to do it.
A magnificent demonstration is one thing. Tuesday morning is another.
Every promise about the future eventually encounters electricity, cooling, networking, maintenance and the deeply inconvenient behavior of physical equipment. The intelligence may astonish us. The plumbing still gets a vote.
Somewhere beneath the polished interface and the cheerful promise of seamless productivity, somebody has to keep the servers answering.
The cloud has a basement. We are putting an awful lot of civilization upstairs.




