Discord reported "Messaging failures" on its status page at 2026-08-04 18:49 UTC.

Discord lists these components: API.

When did the incident start and end?

It started at 2026-08-04 18:49 UTC and ended at 2026-08-04 20:17 UTC. It lasted 1 h 27 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-08-04 18:49 UTC

Messaging failures

ResolvedOfficial update

This incident has been resolved.

The latest update from Discord.

State

Resolved

Started

89 d ago

2026-08-04 18:49 UTC

Lasted

1 h 27 min

until 2026-08-04 20:17 UTC

Worst impact

Major outage

Timeline

6 updates

18:4919:1119:3319:5520:17

Major outageUpdate postedTimes in UTC

Identified

1 h 4 min 73%

Monitoring

24 min 27%

Updates

Times in UTC

As posted by Discord

Resolved2026-08-04 20:17 UTC

This incident has been resolved.

Monitoring2026-08-04 19:59 UTC

We're seeing significant positive impact from our earlier fix; nearly all users should be recovered at this point. We are monitoring closely.

Monitoring2026-08-04 19:53 UTC

We have a fix in place are seeing recovery, although some users may still be seeing impact.

Identified2026-08-04 19:36 UTC

We are actively working toward system recovery and will post another update in 10 minutes.

Identified2026-08-04 18:50 UTC

We are continuing to work on a fix for this issue.

Identified2026-08-04 18:49 UTC

We are currently investigating an issue that is impacting users' ability to send direct messages. Other functionality including interactions, shop, and SDK integrations are also affected.

Affected components

API

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.4× 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