Skip to content
PulseWatchOUTAGE.INTEL
Discord logo

Communication

Is Discord down right now?

NormalOfficial status last polled Oct 2, 2026 07:35 UTCdiscord.comOfficial status page

Discord chat and voice for communities

Are you on the Discord team and see something inaccurate? Report it to us. We respond within one business day.

Is Discord down right now?

No. Discord has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 2, 2026 07:36 UTC

Normal

Discord is operating normally

As of Oct 2, 2026 07:36 UTC

No elevated reports in the last 15 minutes. Baseline 7 reports/hour.

Reports 24h

0

Last incident

Oct 1, 2026 21:20 UTC

Trend

0/15m

Baseline

7/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Discord.

5

Incident days

25

No recorded incident

14h 10m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Discord. Hover a day for detail.

Sep 3Sep 8Sep 13Sep 18Sep 23Sep 2801234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

5

Days with incidents

3 incidents

Busiest day

14h 10m

Recorded duration

Report volume

0 reports in last 24H

07:30 AM11:00 AM02:30 PM06:00 PM09:30 PM01:00 AM04:30 AM00.751.52.253baseline 2

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Discord outage on October 1 — 1h 30m disruption

Oct 1, 07:50 PM → Oct 1, 09:20 PM · 1h 30m · medium

A service disruption affecting Discord was detected on October 1, 2026, at 19:50 UTC. This incident was identified through automated monitoring and the vendor's status page. Service was restored at 21:20 UTC on the same day.

Peak reports
0
in 15 min
Total reports
0
during outage
Duration
1h 30m
until recovery

Impact

During the 1 hour and 30 minute disruption, Discord experienced a medium-severity incident. This event was identified through automated monitoring systems and the vendor's own status page. No user-reported data, including specific issue types or affected regions, was collected for this incident.

Outage timeline

  1. Oct 1, 07:50 PM

    PulseWatch detected the incident from automated vendor and probe signals (medium severity)

  2. Oct 1, 07:50 PM

    Status updated: possible issue

  3. Oct 1, 09:20 PM

    Signals cleared — incident resolved

Official updates

  1. Oct 1, 07:50 PM

    Discord status page acknowledged the incident.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on aggregated user-report signals.

Reliability

Detected by PulseWatch

30-day uptime

97.7%

90-day uptime

99.18%

Calculated from Discord's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other communication services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
ResolvedMedium

Discord: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

10/1/2026, 7:50:08 PM · 1h 30m

07:50 PM09:20 PM
Detection10/1/2026, 7:50:08 PM · 11h ago

Detected — medium severity

Discord: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedHigh

Discord: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Discord or have an alert rule on it can be alerted, labelled vendor-reported.

9/24/2026, 2:12:45 AM · 2h 33m

02:12 AM04:45 AM
Detection9/24/2026, 2:12:45 AM · 8d ago

Detected — high severity

Discord: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Discord or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedHigh

Discord: the vendor reports a major disruption on its own status page. Single origin, not independently confirmed; no customer alert is sent until a second independent source agrees.

9/17/2026, 6:19:04 PM · 3h 38m

06:19 PM09:57 PM
Detection9/17/2026, 6:19:04 PM · 14d ago

Detected — high severity

Discord: the vendor reports a major disruption on its own status page. Single origin, not independently confirmed; no customer alert is sent until a second independent source agrees.

ResolvedHigh

Discord: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Discord or have an alert rule on it can be alerted, labelled vendor-reported.

9/16/2026, 9:37:42 PM · 1h 49m

09:37 PM11:27 PM
Detection9/16/2026, 9:37:42 PM · 15d ago

Detected — high severity

Discord: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Discord or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedMedium

Discord: the vendor reports an incident on its own status page without a structured impact level. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/16/2026, 7:07:47 PM · 1h 9m

07:07 PM08:17 PM
Detection9/16/2026, 7:07:47 PM · 15d ago

Detected — medium severity

Discord: the vendor reports an incident on its own status page without a structured impact level. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Discord enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Normal
Monitoring
Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).
Coverage
Verified against the vendor's own incident history
Reports (24h)
0
Baseline / hour
7
Open threshold
3x

Official site

discord.com