A deep dive into the March 25th voice outage and the E2EE rollout that followed — two stories that together define Discord's most technically eventful year yet.
If you were trying to hop on a Discord voice call on the afternoon of March 25, 2026, you probably stared at that maddening "Awaiting Endpoint" spinner for a long time. Maybe you refreshed. Maybe you rage-quit. Maybe you blamed your ISP.
It wasn't your ISP.
What actually happened behind the scenes is one of the most fascinating distributed systems failure stories of the year — a cascade that started with a routine Kubernetes config tweak and ended with Discord engineers playing an urgent, multi-hour game of infrastructure whack-a-mole. And just weeks after that chaos, the same engineering org quietly shipped one of the most significant privacy features in the company's history: mandatory end-to-end encryption for every voice and video call on the platform.
Let's dig into both.
