Discord reported "Media Proxy Latency High" on its status page at 2026-09-11 16:24 UTC.

Discord lists these components: Media Proxy.

When did the incident start and end?

It started at 2026-09-11 16:24 UTC and ended at 2026-09-11 17:46 UTC. It lasted 1 h 22 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-11 16:24 UTC

Media Proxy Latency High

ResolvedOfficial update

This incident has been resolved.

The latest update from Discord.

State

Resolved

Started

51 d ago

2026-09-11 16:24 UTC

Lasted

1 h 22 min

until 2026-09-11 17:46 UTC

Worst impact

Degraded

Timeline

4 updates

16:2416:4517:0517:2517:46

DegradedUpdate postedTimes in UTC

Investigating

3 min 4%

Identified

1 h 12 min 88%

Monitoring

7 min 9%

Updates

Times in UTC

As posted by Discord

Resolved2026-09-11 17:46 UTC

This incident has been resolved.

Monitoring2026-09-11 17:39 UTC

A fix has been implemented and we are monitoring the results.

Identified2026-09-11 16:27 UTC

The issue has been identified and a fix is being implemented.

Investigating2026-09-11 16:24 UTC

We are currently investigating an issue involving high error-rates for image downloads.

Affected components

Media Proxy

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

1.3× 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 12 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 31 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 45 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