Datvero automation observatory · discordstatus.com
No. Discord's status page reports all 15 voice regions operational, with no open incident whose title mentions “voice” (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 11 incidents whose title mentions “voice”: 0 critical, 9 major, 0 minor and 2 with no impact (the vendor's own classification). Median time from first post to resolution, impact incidents only: 1.7 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 | |
| Sep 16, 21:32 | Issue establishing voice call | major | 1 h | |
| Sep 11, 04:21 | Issue with establishing voice calls | major | 2.3 h | |
| Sep 2, 23:26 | Voice endpoint selection issues | major | 16 min | |
| Aug 31, 22:54 | Some servers and other services (voice calls, activities) not available for some users | major | 1.9 h | |
| Jul 22, 23:32 | unable to establish voice connection | major | 25 min | |
| Mar 20, 02:47 | Failure to start new voice calls | major | 3.2 h | |
| Mar 2, 20:02 | A/V E2EE Enforcement for Non-stage Voice Calls | none | 8.9 days | |
| Feb 27, 21:52 | Unavailable Servers and Voice Calls | none | 34 min | |
| Jan 27, 21:23 | Voice and video errors | major | 1.7 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 15 voice regions operational, with no open incident whose title mentions “voice” (checked November 6, 2026, 18:15 UTC; this page refreshes every 5 minutes).
From January 25 to November 6, 2026, discordstatus.com lists 11 incidents whose title mentions “voice”: 0 critical, 9 major, 0 minor and 2 with no impact (the vendor's own classification). Median time from first post to resolution, impact incidents only: 1.7 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.
This page covers Voice (15 voice regions), as named on the official status page. This feed does not attach incidents to these components, so the table lists the incidents whose title contains “voice”. For all of Discord, see the Discord page.
Discord publishes it at https://discordstatus.com/. This page republishes its public feed every 5 minutes with timestamps. Datvero is not affiliated with Discord.
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 Voice 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. 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 Voice succeeds.