# You've Got (Too Much) Mail: Behind the Scenes of the 3/25/26 Voice Outage

DevFeed: [You've Got (Too Much) Mail: Behind the Scenes of the 3/25/26 Voice Outage](<https://devfeed.tech/articles/you-ve-got-too-much-mail-behind-the-scenes-of-the-3-25-26-voice-outage-197.md>)

Original publisher: [Read original article](<https://discord.com/blog/behind-the-scenes-of-the-3-25-26-voice-outage>)

Author: Discord Engineering

Published: 2026-04-29T00:00:00Z

Content type: article

Language: en

Sources: [Discord Blog](<https://devfeed.tech/sources/discord-blog.md>)

Topics: [incident](<https://devfeed.tech/topics/incident.md>), [migration](<https://devfeed.tech/topics/migration.md>), [networking](<https://devfeed.tech/topics/networking.md>), [Processes](<https://devfeed.tech/topics/processes.md>)

Tags: [audio](<https://devfeed.tech/tags/audio.md>), [backend](<https://devfeed.tech/tags/backend.md>), [discord](<https://devfeed.tech/tags/discord.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [incident](<https://devfeed.tech/tags/incident.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [migration](<https://devfeed.tech/tags/migration.md>), [on-call](<https://devfeed.tech/tags/on-call.md>), [outage](<https://devfeed.tech/tags/outage.md>), [processes](<https://devfeed.tech/tags/processes.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [routing](<https://devfeed.tech/tags/routing.md>), [video](<https://devfeed.tech/tags/video.md>), [voice](<https://devfeed.tech/tags/voice.md>)

## AI overview

Discord's engineering team explains a cascading voice and video outage caused when a routine configuration update shut down a large portion of session-management servers. The post covers the resulting load on call-routing systems, recovery, and infrastructure improvements.

## Source excerpt

On March 25th, voice and video on Discord suffered major degradation beginning at 12:13 PDT, lasting a little over three hours. Learn how the issue originated, how it affected systems across Discord, how we recovered, and how we're preventing the same problem from reoccurring.