Discord reported "Voice endpoint selection issues" on its status page at 2026-09-02 23:26 UTC.

Discord did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-09-02 23:26 UTC and ended at 2026-09-02 23:42 UTC. It lasted 16 min.

How do I get alerts for Discord?

Subscribe to the Discord live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Discord. outages.live reads it every few minutes and keeps every update.

DiscordIncident · 2026-09-02 23:26 UTC

Voice endpoint selection issues

ResolvedOfficial update

This incident has been resolved.

The latest update from Discord.

State

Resolved

Started

59 d ago

2026-09-02 23:26 UTC

Lasted

16 min

until 2026-09-02 23:42 UTC

Worst impact

Partial outage

Timeline

3 updates

23:2623:3023:3423:3823:42

Partial outageUpdate postedTimes in UTC

Investigating

9 min 54%

Identified

7 min 46%

Updates

Times in UTC

As posted by Discord

Resolved2026-09-02 23:42 UTC

This incident has been resolved.

Identified2026-09-02 23:35 UTC

We've identified an issue with our endpoint selection service and are applying a mitigation now. We are seeing recovery to endpoint selection now.

Investigating2026-09-02 23:26 UTC

We are investigating problems with voice endpoint selection. Your calls may fail to start or may fail to get an endpoint.

Discord in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 2 min

This incident

74% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

6 h 17 min

median 1 h 2 min

90 days agoToday

Other Discord incidents

All incidents

Discord·Issues establishing voice call

This incident has been resolved.

Resolvedresolved 10 h ago

Discord·Issues establishing voice calls

This incident has been resolved.

Resolvedresolved 2 d ago

Discord·Elevated API error rate

This incident has been resolved.

Resolvedresolved 30 d ago

Discord·Age group status mismatch across devices

This incident has been resolved. https://x.com/discord/status/2102964092189475028?s=20

Resolvedresolved 38 d ago

Discord·Issue / Delay in establishing call connection

This incident has been resolved.

Resolvedresolved 44 d ago

Follow Discord

Your coding agent knows when Discord is down, and tells you when a failure is theirs, not yours. You can also get Discord incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "discord" and tell me if Discord has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.cc/feed.xml?providers=discord

Slack

/feed subscribe https://outages.cc/feed.xml?providers=discord

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane