Datvero automation observatory · discordstatus.com
No. Discord's status page reports all systems operational for Discord: API, Gateway, Voice and 8 other components (checked November 6, 2026, 18:15 UTC; this page refreshes every 5 minutes).
Read from Discord's official status API at November 6, 2026, 18:15 UTC. Datvero republishes what Discord states; it is not an independent uptime measurement.
From January 25 to November 6, 2026, discordstatus.com lists 52 incidents: 3 critical, 32 major, 9 minor and 8 with no impact (the vendor's own classification). Median time from first post to resolution, impact incidents only: 1.1 h. Longest: “Issues establishing voice call” (October 31, 2026), 6.3 h. In the last 30 days: 2 incidents, 2 of them major or critical.
| Posted (UTC) | Incident | Impact | Components | Duration |
|---|---|---|---|---|
| Oct 31, 15:26 | Issues establishing voice call | major | 6.3 h | |
| Oct 30, 15:23 | Issues establishing voice calls | major | 55 min | |
| Oct 1, 19:48 | Elevated API error rate | minor | API, Media Proxy | 1.1 h |
| Sep 24, 02:08 | Age group status mismatch across devices | major | Android | 1.4 h |
| Sep 17, 18:18 | Issue / Delay in establishing call connection | major | 2.4 h | |
| Sep 16, 21:32 | Issue establishing voice call | major | 1 h | |
| Sep 16, 19:03 | API Errors | none | API | 25 min |
| Sep 16, 16:15 | Google Pay Outage | major | 28 min | |
| Sep 15, 14:26 | Session Unavailability | none | 50 min | |
| Sep 11, 16:24 | Media Proxy Latency High | minor | Media Proxy | 1.4 h |
| Sep 11, 04:21 | Issue with establishing voice calls | major | 2.3 h | |
| Sep 3, 21:31 | Some Servers Unavailable | none | 56 min | |
| Sep 3, 14:35 | Some servers unavailable | major | 1 h | |
| Sep 2, 23:26 | Voice endpoint selection issues | major | 16 min | |
| Sep 2, 16:12 | Server Unavailability | major | 2.2 h |
Retry with a growing delay, send failures to an error workflow, and get alerted when runs stop succeeding. In n8n, every node has a Retry On Fail setting; Make has Break error handlers that retry incomplete executions; Zapier can replay failed runs with Autoreplay. Datvero watches the runs of your n8n, Make and Zapier workflows and alerts you when they fail, whatever the cause.
No. Discord's status page reports all systems operational for Discord: API, Gateway, Voice and 8 other components (checked November 6, 2026, 18:15 UTC; this page refreshes every 5 minutes).
From January 25 to November 6, 2026, discordstatus.com lists 52 incidents: 3 critical, 32 major, 9 minor and 8 with no impact (the vendor's own classification). Median time from first post to resolution, impact incidents only: 1.1 h. Longest: “Issues establishing voice call” (October 31, 2026), 6.3 h. In the last 30 days: 2 incidents, 2 of them major or critical.
Discord publishes it at https://discordstatus.com/. This page republishes its public feed every 5 minutes with timestamps. Datvero is not affiliated with Discord.
When the status page is green but your bot or webhook fails, read the HTTP code. The Discord API answers 429 when a rate limit is exceeded, with a JSON body whose retry_after field gives the seconds to wait before the next request. That is a limit, not an outage.
The status page lists what Discord has declared. If it is green and you still see errors, read the error code, retry with a growing delay, and check whether the problem is specific to your account, your region or one integration. A green page does not prove that every request to Discord succeeds.
Retry with a growing delay, send failures to an error workflow, and get alerted when runs stop succeeding. In n8n, every node has a Retry On Fail setting; Make has Break error handlers that retry incomplete executions; Zapier can replay failed runs with Autoreplay. Datvero watches the runs of your n8n, Make and Zapier workflows and alerts you when they fail, whatever the cause.
Method: Discord's public status API (discordstatus.com/api/v2) is read every 5 minutes, its incident list every 15 minutes, and each incident is kept with its official timestamps. Durations run from the first post to the resolved post. Machine readable copy: services.json. HTTP codes: Discord Developer Docs, Rate Limits. Official source: https://discordstatus.com/.
Statuses, incident names and texts belong to Discord. Datvero is not affiliated with Discord. A green status page does not mean every workflow that calls Discord succeeds.