1. Home
  2. Outages
  3. Discord
  4. 30 Oct 2026

OutageFriday 30 October 2026Ended 31 Oct, 00:30

Discord outage on 30 October 2026

Problem reports about Discord rose to outage level at 15:56 Central European time on Friday 30 October 2026, in 2 separate spikes over 8 h 35 min (1 h 19 min at outage level in all).

They peaked at 195 reports in 15 minutes at 16:13, about 16 times the usual level for that time of day, and 419 reports came in while the outage lasted.

Reports reached outage level in 13 countries, the US, Germany, the UK, Belgium and more.

12 other services had an outage spike at the same time.

Is Discord down right now? 5 outages of Discord

Started
15:56
Fri 30 Oct, Central European time
At outage level
1 h 19 min
Ended 00:30 on 31 Oct
Busiest 15 minutes
195
reports, at 16:13
Reports during the outage
419
Peak about 16× the usual level
Timeline

Reports from Fri 09:45 to Sat 06:45

One bar per 15 minutes, Central European time. Red bars are the outage; the dashed line is what a usual day sees at that time.

Problem reports about Discord rose to outage level at 15:56 Central European time on Friday 30 October 2026, in 2 separate spikes over 8 h 35 min (1 h 19 min at outage level in all). They peaked at 195 reports in 15 minutes at 16:13, about 16 times the usual level for that time of day, and 419 reports came in while the outage lasted. Reports reached outage level in 13 countries, the US, Germany, the UK, Belgium and more. 12 other services had an outage spike at the same time.
Around the world

Where people reported it that day

Each country's reports on 30 October, against the usual level there. Outage means reports stayed at outage level for half an hour or more; above usual, for an hour or more.

CountryThat dayReports
The USOutage1,680
GermanyOutage545
The UKOutage482
BelgiumOutage333
JapanOutage310
FranceOutage309
The PhilippinesOutage253
PolandOutage238
CanadaOutage182
The NetherlandsNormal177
BrazilNormal109
SpainNormal103
Same time

Other services with an outage at the same time

Their reports also reached outage level while Discord's did. Many services failing together can point to a shared cause, such as a network or cloud provider, but reports alone cannot show it.

More

Discord: live status and other outages

Check whether Discord is down right now: the live page shows the last 24 hours and fixes to try. This site keeps a page for each of Discord's 5 outages since the archive began.

Earlier: 29 Oct 2026 Later: 31 Oct 2026 October 2026 outage report All recent outages

Embed

Put this outage in an article

Copy a frame with the chart and numbers above, or an image of the same card for places that do not allow frames, such as newsletters. Both link back to this page. More for journalists.

Discord outage on 30 October 2026: problem reports over time

<iframe src="https://isitdownrightnow.app/embed/discord/2026-10-30/" title="Discord outage on 30 October 2026" width="100%" height="230" style="border:0;max-width:560px" loading="lazy"></iframe> <p><a href="https://isitdownrightnow.app/services/discord/outages/2026-10-30/">Discord outage on 30 October 2026</a> from IsItDownRightNow.app</p>Frame: the chart and numbers, as a small card
<a href="https://isitdownrightnow.app/services/discord/outages/2026-10-30/"><img src="https://isitdownrightnow.app/share/discord/2026-10-30.png" alt="Discord outage on 30 October 2026: problem reports over time" width="600" height="315" loading="lazy"></a>Image: the same card as a picture
[![Discord outage on 30 October 2026](https://isitdownrightnow.app/share/discord/2026-10-30.png)](https://isitdownrightnow.app/services/discord/outages/2026-10-30/)Markdown: the image, for README files and forums

Where these numbers come from

The numbers are problem reports that users sent to a public outage-reporting service, counted in 15-minute windows and kept as this site's live page showed them. A spike counts as an outage when reports are more than twice the usual level and far above the day's average. Reports show that many people had trouble at the same time, not what caused it; the service's own status page is the place for that.