Photo credit: Proofpoint (X)
This morning did not go as planned for a lot of people staring at frozen inboxes. Two major platforms stumbled almost back to back, and the disruption spread fast enough that outage trackers lit up before most companies had finished their first coffee.
Where the trouble started
The trouble began with Proofpoint, an enterprise security firm that quietly protects email for thousands of organizations. Proofpoint handles work most people never see, including email security, spam filtering, cloud security, archiving and data loss prevention. When a service like that stumbles, the damage rarely stays contained. It spreads to every business that depends on it.
By mid morning, reports were pouring in. On Down Detector, the tracker that monitors real time failures, Proofpoint complaints spiked to roughly 400 around 9 a.m. About 56% of users reported they could not send messages, while another 32% struggled to receive them, a pattern that pointed to a problem at the core of the email pipeline rather than in any single app.
Why the outage spread so fast
The twist here is that this was not a dramatic hack or a server meltdown. Proofpoint’s own status updates pointed to a DNS resolution issue, essentially a mail carrier that could no longer read the addresses on the envelopes.
DNS is the quiet backbone that tells internet traffic where to go. When it fails, messages do not disappear. They simply lose their way, stalling or bouncing with no clear explanation for the person waiting on the other end. That is part of why outages like this feel so confusing from the outside. Everything looks fine until suddenly nothing works.
Because Proofpoint sits between the sender and the inbox for so many companies, one routing failure was enough to freeze communication across universities, businesses and email systems all at once. The company had not issued a public statement while the disruption was still unfolding.
Outlook joins the trouble
The morning brought a second wave. Right as the first issue peaked, Microsoft Outlook users began flooding the same tracker with their own complaints. Outlook reports climbed to around 450 by 10 a.m., a slightly larger spike that landed about an hour after the first.
For people affected by both, the timing blurred together into one long headache. Someone unable to send a work email had no easy way to tell whether the issue lived with their security layer, their mail client or something further upstream. Microsoft, like Proofpoint, stayed quiet publicly as complaints climbed. It remained unclear whether the two outages shared a root cause or simply collided by unlucky timing.
What you can actually do
Outages at this level leave individuals with very few real options. You cannot fix a provider’s DNS from your desk, and refreshing your inbox repeatedly accomplishes nothing beyond raising your blood pressure. A few small steps still help. Check a live status tracker before assuming your own device is broken. Keep a backup channel ready, like a phone or chat app, for anything urgent. Avoid resending the same message multiple times, since duplicates only clog the queue once service returns. Save drafts locally so nothing is lost if your client crashes. Beyond that, waiting is really the only option, since a fix at this level sits entirely with the provider.
Mornings like this are a reminder that the tools people treat as permanent are held together by systems most never think about. A single routing glitch inside Proofpoint was enough to stall real work for thousands of people, and the fix was never in their hands to begin with.
About the Author
