Skip to main content
Discord (for communities) logo

Is Discord (for communities) Down?

No — Discord (for communities) is up

Reachable from all 8 checked regions

Average response time: 44ms

Last checked · checks run every 6 hours

Official status page: https://discordstatus.com

Discord (for communities) uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
42ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 22 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

22-day clean streak
Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: 100.00% uptime, 8 checks
Jul 28: 100.00% uptime, 32 checks
Jul 29: 100.00% uptime, 32 checks
Jul 30: 100.00% uptime, 32 checks
Jul 31: 100.00% uptime, 32 checks
Aug 1: 100.00% uptime, 32 checks
Aug 2: 100.00% uptime, 32 checks
Aug 3: 100.00% uptime, 32 checks
Aug 4: 100.00% uptime, 40 checks
Aug 5: 100.00% uptime, 32 checks
Aug 6: 100.00% uptime, 32 checks
Aug 7: 100.00% uptime, 32 checks
Aug 8: 100.00% uptime, 32 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 100.00% uptime, 32 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 40 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 40 checks
Aug 16: 100.00% uptime, 32 checks
Aug 17: 100.00% uptime, 24 checks
Jul 19 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

fra
41ms
DNS 0ms TCP 1ms TLS 6ms TTFB 33ms
gru
62ms
DNS 0ms TCP 4ms TLS 12ms TTFB 52ms
iad
43ms
DNS 0ms TCP 2ms TLS 8ms TTFB 36ms
jnb
36ms
DNS 0ms TCP 0ms TLS 8ms TTFB 29ms
lax
48ms
DNS 0ms TCP 1ms TLS 6ms TTFB 42ms
lhr
47ms
DNS 1ms TCP 2ms TLS 7ms TTFB 38ms
nrt
31ms
DNS 0ms TCP 1ms TLS 5ms TTFB 26ms
ord
47ms
DNS 0ms TCP 2ms TLS 7ms TTFB 39ms
sin
42ms
DNS 0ms TCP 1ms TLS 8ms TTFB 36ms

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 all 18 regions to find out where it breaks.

Test it yourself

Related services

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 — 8 of them answered the most recent check.
  • 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. We only change the 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. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Discord (for communities) goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required