Communication tools
Is Discord down?
Live Discord status, measured independently. We probe 4 Discord endpoints from monitoring regions on every continent and record every outage we detect.
Discord is up
Our probes are reaching Discord normally from every region we check from.
Checked every minute from 6 regions on every continent.
- Uptime, 24 hoursUptime, last 24 hours
- Uptime, 7 daysUptime, last 7 days
- Uptime, 30 daysUptime, last 30 days
- Website100% uptime, 30 days6 regions, 34 to 51 msUnknownp50median response43 msp95slowest 5% of checks76 ms100 ms50024 h ago12 h agonow
- API gateway discovery100% uptime, 30 days6 regions, 20 to 31 msUnknownp50median response25 msp95slowest 5% of checks53 ms50 ms25024 h ago12 h agonow
- Media CDN100% uptime, 30 days6 regions, 29 to 68 msUnknownp50median response43 msp95slowest 5% of checks150 ms100 ms50024 h ago12 h agonow
- Official status feed83.32% uptime, 30 days6 regions, 171 to 474 msUnknownp50median response300 msp95slowest 5% of checks515 ms500 ms250024 h ago12 h agonow
Daily strip:99.9% or better95–99.9%below 95%no data yet
Get notified when Discord goes down
Follow these 4 checks from your own workspace and get alerted through Slack, email, webhooks, or on-call the moment Discord goes down. They don't count against your monitor quota. Free plan, no card required.
About Discord outages
Discord hosts communities, support servers, and a growing number of developer teams, and its API and webhooks are a common alert destination. Discord incidents often affect the gateway that clients and bots connect through, so messages stop flowing while the website loads fine.
What we check
Every row is a real monitor in upti.my, running from each of our regions. A failure in some regions marks the row degraded; failures from every region mark it down and open an outage.
| Check | Target | Expects | Interval |
|---|---|---|---|
Website discord.com is unreachable. | httpdiscord.com | HTTP 200 | 1 min |
API gateway discovery The Discord API is failing. Bots cannot connect and webhooks cannot deliver. | httpdiscord.com/api/v10/gateway | HTTP 200 | 1 min |
Media CDN Discord's media CDN is failing. Avatars, attachments, and embeds do not load. | httpcdn.discordapp.com/embed/avatars/0.png | HTTP 200 | 1 min |
Official status feed Discord's status page is unreachable. | httpdiscordstatus.com/api/v2/status.json | HTTP 200 | 5 min |
For component-level detail and incident write-ups from the vendor, see Discord's official status page.
Recent Discord outages we detected
An outage is recorded when a probe fails from every monitoring region and closed when it recovers. Partial and single-region problems show as degraded above but are not listed here.
Discord is up. Is your Discord integration?
The incidents that actually hurt are usually not global outages. They are the parts of your own system that depend on Discord and fail quietly. Here is what teams that rely on Discord monitor on their side.
Alerts routed to Discord
If your alerts land in a Discord channel, add a second channel for critical severities so a Discord incident cannot hide your own.
Alert routingBots you operate
A bot that loses its gateway connection and does not reconnect is silent. A heartbeat from the bot process catches it.
Heartbeat monitoringDiscord status: frequently asked questions
Check whether the API gateway probe is failing. Discord's most common incidents affect message delivery or voice in specific regions and are listed with affected components on the official page.
Look at the per-region results above. If our probes fail from every region, Discord has a real outage and it will appear in the outage list. If they succeed everywhere, the problem is most likely on your side: your network, DNS resolver, a browser extension, a corporate proxy, or your own integration. If only some regions fail, Discord may have a regional incident that does not affect you.
Every probe runs at least every five minutes from each monitoring region, and most run every minute. This page refreshes its data every minute. Uptime figures are calculated from all checks across all regions.
Official status is updated by people after an incident is confirmed and often lags the first failures by many minutes; our probes react within a minute or two. In the other direction, we only see public endpoints, so an internal incident may not show on our probes. Use both.
Yes. Use "Notify me about Discord" above: your upti.my workspace follows these exact checks, free plan included, and every outage opens an incident there and routes alerts to Slack, email, webhooks, or on-call. Nothing is duplicated and it doesn't use your monitor quota. Better still, also monitor your own dependency on Discord: the API route, webhook receiver, or scheduled job that calls it, so you learn about the failure that actually affects your users.
Related
Other communication tools
upti.my is not affiliated with Discord. Discord and related marks are the property of their respective owners and are used here only to identify the service being measured. Results reflect the reachability of public endpoints from our monitoring regions and may differ from the vendor's own reporting.