outages.live
Live

Discord

Discord is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

19

Days with an incident

14

Median duration

1 h 2 min

Longest incident

6 h 17 min

Components

30
API Operational
90 days ago3 days with an incidentToday
Media Proxy Operational
90 days ago2 days with an incidentToday
Gateway Operational
90 days agoNo incidentsToday
Push Notifications Operational
90 days agoNo incidentsToday
Search Operational
90 days agoNo incidentsToday
Server Web Pages Operational
90 days agoNo incidentsToday
Payments Operational
90 days agoNo incidentsToday
Marketing Site Operational
90 days agoNo incidentsToday

Third-party

CloudFlare Operational
90 days agoNo incidentsToday
Tax Calculation Service Operational
90 days agoNo incidentsToday
Creator Payouts Operational
90 days agoNo incidentsToday

Client

Desktop Operational
90 days agoNo incidentsToday
iOS Operational
90 days agoNo incidentsToday
Android Operational
90 days ago1 day with an incidentToday
Web Operational
90 days agoNo incidentsToday

Voice

Atlanta Operational
90 days agoNo incidentsToday
Brazil Operational
90 days agoNo incidentsToday
Rotterdam Operational
90 days agoNo incidentsToday
Hong Kong Operational
90 days agoNo incidentsToday
India Operational
90 days agoNo incidentsToday
Japan Operational
90 days agoNo incidentsToday
Russia Operational
90 days agoNo incidentsToday
Singapore Operational
90 days agoNo incidentsToday
South Africa Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 31, 2026

Duration6 h 17 min15:26 to 21:43Issues establishing voice callPartial outage

This incident has been resolved.

Oct 30, 2026

Duration55 min15:23 to 16:18Issues establishing voice callsPartial outage

This incident has been resolved.

Oct 1, 2026

Duration1 h 5 min19:48 to 20:52Elevated API error rateDegraded

This incident has been resolved.

Sep 24, 2026

Duration1 h 24 min02:08 to 03:32Age group status mismatch across devicesPartial outage

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

Sep 17, 2026

Duration2 h 21 min18:18 to 20:39Issue / Delay in establishing call connectionPartial outage

This incident has been resolved.

Sep 16, 2026

Duration1 h 2 min21:32 to 22:35Issue establishing voice callPartial outage

This incident has been resolved.

Duration25 min19:03 to 19:28API ErrorsNotice

This incident has been resolved.

Duration28 min16:15 to 16:43Google Pay OutagePartial outage

This incident has been resolved.

Sep 15, 2026

Duration50 min14:26 to 15:16Session UnavailabilityNotice

This incident has been resolved.

Sep 11, 2026

Duration1 h 22 min16:24 to 17:46Media Proxy Latency HighDegraded

This incident has been resolved.

Duration2 h 21 min04:21 to 06:42Issue with establishing voice callsPartial outage

This incident has been resolved.

Sep 3, 2026

Duration56 min21:31 to 22:27Some Servers UnavailableNotice

This incident has been resolved.

Duration1 h 2 min14:35 to 15:37Some servers unavailablePartial outage

This incident has been resolved.

Sep 2, 2026

Duration16 min23:26 to 23:42Voice endpoint selection issuesPartial outage

This incident has been resolved.

Duration2 h 14 min16:12 to 18:26Server UnavailabilityPartial outage

This incident has been resolved.

Aug 31, 2026

Duration1 h 55 min22:54 to 00:49Some servers and other services (voice calls, activities) not available for some usersPartial outage

This incident has been resolved.

Aug 14, 2026

Duration14 min06:09 to 06:24Issue with establishing a callPartial outage

This incident has been resolved.

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.live/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.live/feed.xml?providers=discord
Slack
/feed subscribe https://outages.live/feed.xml?providers=discord

Go from tracking outages to fixing production issues with Polylane.

Try Polylane