Is Discord (for communities) Down?

No — Discord (for communities) is up

Discord (for communities)'s status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 66 ms

Right now

The verdict is the worse of these two. How we decide

Discord (for communities)'s status page

discordstatus.com · read 3 minutes ago · checked every 3 minutes

Operational

Discord (for communities)'s components, as its status page reports them
Component	Status
API	Operational
Media Proxy	Operational
Gateway	Operational
Push Notifications	Operational
Search	Operational
Server Web Pages	Operational
Payments	Operational
Marketing Site	Operational
CloudFlare	Operational
Tax Calculation Service	Operational
Creator Payouts	Operational
Desktop	Operational

12 more, all operational · show all 24

All of Discord (for communities)'s components
Component	Status
API	Operational
Media Proxy	Operational
Gateway	Operational
Push Notifications	Operational
Search	Operational
Server Web Pages	Operational
Payments	Operational
Marketing Site	Operational
Third-party
CloudFlare	Operational
Tax Calculation Service	Operational
Creator Payouts	Operational
Client
Desktop	Operational
iOS	Operational
Android	Operational
Web	Operational
Voice
Atlanta	Operational
Rotterdam	Operational
Russia	Operational
South Korea	Operational
Sydney	Operational
US Central	Operational
US East	Operational
US South	Operational
US West	Operational

6 locations All operational

Open their status page

FlareWarden checks

discord.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 66 ms
Checked: 3 hours ago

By region

Ashburn reachable, 69 ms
Chicago reachable, 53 ms
Johannesburg reachable, 33 ms
London reachable, 106 ms
Los Angeles reachable, 92 ms
Singapore reachable, 59 ms
São Paulo reachable, 65 ms
Tokyo reachable, 58 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	10 ms	2 ms	10 ms	65 ms
Chicago	5 ms	1 ms	6 ms	50 ms
Johannesburg	6 ms	0 ms	4 ms	30 ms
London	36 ms	2 ms	16 ms	100 ms
Los Angeles	46 ms	1 ms	7 ms	87 ms
Singapore	5 ms	2 ms	9 ms	56 ms
São Paulo	12 ms	2 ms	7 ms	58 ms
Tokyo	19 ms	1 ms	6 ms	56 ms

We check that discord.com loads, not every feature behind it. Test it yourself

History

Incidents Discord (for communities) reported

Since Oct 22, 15 days · from discordstatus.com

Incidents: 2
Major or critical: 2
Median to resolve: 3h 36m

Issues establishing voice call
major · Oct 31
lasted 6h 17m
Issues establishing voice calls
major · Oct 30
lasted 55m

Discord (for communities) website availability

Measured by FlareWarden · discord.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 55ms

Last 30 days

91-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of discord.com from multiple regions every 6 hours. Discord (for communities)'s status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 90 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Discord (for communities) does

Discord is a voice, video and text platform used by gaming communities, study groups, open-source projects and companies for real-time conversation. Servers are organised into channels, and many communities use it as their primary support and announcement channel rather than a forum or a mailing list.

What an outage looks like

During a Discord outage messages fail to send or arrive minutes late, voice channels disconnect or refuse new connections, and the app sits on a connecting spinner. Member lists can appear empty, uploads stall, and bots stop responding to commands. Desktop, web and mobile clients usually fail together because they share one backend.

What to do about it

Check discordstatus.com, which reports API, gateway, voice and media separately, so a voice-only incident shows there before anywhere else. Voice problems are often regional, and changing a channel's voice region can restore a call while the incident continues. Messages that show a failed marker were never queued, so send them again.

Is it down for everyone, or just you?

If this page says Discord (for communities) is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Slack

Cloudflare

SoundCloud

Discord (for communities) outage FAQ

Is Discord down for everyone or just me?

discordstatus.com splits the platform into API, gateway, voice and media, so a partial incident reaches only some people. If it reports everything operational, try a different network before assuming the worst. Discord's voice traffic is sensitive to restrictive firewalls, and some corporate and campus networks block it outright while leaving text working.

Why can I read messages but not send them?

That pattern usually means the gateway connection dropped while cached content stayed on screen. The client keeps showing the last state it received, so a channel looks normal until you try to post. Restarting the client is the fastest fix once the underlying incident clears, but it will not help while the gateway is still down.

Do voice channels go down separately from chat?

Yes. Voice runs on separate infrastructure and is reported as its own component. Voice incidents are also frequently regional, so one group can be unable to connect while others in the same server talk normally. Changing the channel's voice region sometimes works around it without waiting for a fix.

Are messages lost during a Discord outage?

Messages already delivered are stored and reappear when the client reconnects. Messages that failed to send are not queued for retry: the client marks them failed and you have to send them again. Anything typed but never submitted is lost if the client restarts, so copy long posts before retrying.

How we measure this

We request Discord (for communities)'s public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Discord (for communities) publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Discord (for communities) itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Discord (for communities) goes down

We check Discord (for communities) every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required