Is Discord down?
For agents
proceed
Proceed.
GET upbutler.com/status/discord/status.agent.json
MCP: upstream_status {"service":"discord"}
The gateway, REST API and webhooks that bots and alert channels use.
What Discord reports
Operational
Taken as is from Discord's own status page API. Incident titles and component names below are theirs.
Open discordstatus.comUpButler's independent probe
REST API is answeringHTTP 200 · 17 ms
One request without credentials to discord.com every two minutes. An answer shows the edge, TLS and routing work. It does not prove that authenticated calls succeed.
Checked · up since 2026-10-10 01:23 UTC
Discord components
30 operational
- APIOperational
- Media ProxyOperational
- GatewayOperational
- Push NotificationsOperational
- SearchOperational
- Server Web PagesOperational
- PaymentsOperational
- Marketing SiteOperational
Third-party
- CloudFlareOperational
- Tax Calculation ServiceOperational
- Creator PayoutsOperational
Client
- DesktopOperational
- iOSOperational
- AndroidOperational
- WebOperational
Voice
- AtlantaOperational
- BrazilOperational
- RotterdamOperational
- Hong KongOperational
- IndiaOperational
- JapanOperational
- RussiaOperational
- SingaporeOperational
- South AfricaOperational
- South KoreaOperational
- SydneyOperational
- US CentralOperational
- US EastOperational
- US SouthOperational
- US WestOperational
Discord incidents, last 90 days
1 finished incident seen since UpButler started tracking on 2026-10-10.
| Started (UTC) | Incident | Impact | Lasted |
|---|---|---|---|
| Elevated API error rate | minor | 1 h 5 min |
Tell your outage from Discord's
Declare that your project depends on Discord. When one of your monitors fails while Discord has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- discordcurl -s https://upbutler.com/status/discord/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "discord",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": {
"state": "up",
"statusCode": 200
}
}Questions
- Is Discord down right now?
- No. As of 2026-10-10 05:12 UTC, Discord is operational. This page reads the status again every 2 minutes.
- Where does this status come from?
- From Discord's own status page API at https://discordstatus.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Discord's words.
- What does UpButler's own Discord check prove?
- Every two minutes UpButler sends one request without credentials to the Discord REST API (discord.com). Any answer from the edge, usually HTTP 200, shows that DNS, TLS and routing work. It does not prove that authenticated requests succeed, so it can say "reachable" while Discord reports degraded service. It is useful the other way round: when the probe fails before their status page changes.
- How can my agent or app check Discord status?
- Fetch https://upbutler.com/status/discord/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"discord"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Discord's?
- Add "discord" to the dependencies of your UpButler workspace. When one of your monitors fails while Discord has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in messaging and realtime
UpButler is not affiliated with Discord. Status and incident text belong to Discord and are read from their public status source; the probe result is UpButler's own measurement.