# Discord outage reports and status

Canonical page: https://iszdown.com/now/discord

Status: Provider reports operational

24-hour window (UTC): 2026-10-19T23:30:00.000Z to 2026-10-20T23:30:00.000Z

Recorded outage reports in this window: 0

Last successful estimated-activity check: 2026-10-20T12:23:07.000Z

Discord is great for playing games and chilling with friends, or even building a worldwide community. Customize your own space to talk, play, and hang out.

## How to interpret this page

Estimated down reports are based on US problem-related activity. Values are relative activity from 0 to 100, not counts of submitted reports. The HTML chart averages samples into ten-minute intervals. Partial samples are excluded and missing samples are not invented.

Recorded outage reports and estimated activity are separate signals. Neither confirms that every user is affected. Missing or stale data does not establish that a service is working.

Methodology: https://iszdown.com/methodology

## Citation

Cite [Discord on Iszdown](https://iszdown.com/now/discord), include your access time and the observation time above, and qualify estimated activity as an estimate. Recheck before describing current status. Iszdown is independent of the monitored provider.

## Estimated activity samples

| Observation time (UTC) | Relative activity (0–100) |
| --- | --- |
| 2026-10-19T23:36:00.000Z | 0 |
| 2026-10-19T23:44:00.000Z | 0 |
| 2026-10-19T23:52:00.000Z | 0 |
| 2026-10-20T00:00:00.000Z | 0 |
| 2026-10-20T00:08:00.000Z | 0 |
| 2026-10-20T00:16:00.000Z | 0 |
| 2026-10-20T00:24:00.000Z | 0 |
| 2026-10-20T00:32:00.000Z | 0 |
| 2026-10-20T00:40:00.000Z | 0 |
| 2026-10-20T00:48:00.000Z | 0 |
| 2026-10-20T00:56:00.000Z | 0 |
| 2026-10-20T01:04:00.000Z | 0 |
| 2026-10-20T01:12:00.000Z | 0 |
| 2026-10-20T01:20:00.000Z | 0 |
| 2026-10-20T01:28:00.000Z | 0 |
| 2026-10-20T01:36:00.000Z | 0 |
| 2026-10-20T01:44:00.000Z | 0 |
| 2026-10-20T01:52:00.000Z | 0 |
| 2026-10-20T02:00:00.000Z | 0 |
| 2026-10-20T02:08:00.000Z | 0 |
| 2026-10-20T02:16:00.000Z | 0 |
| 2026-10-20T02:24:00.000Z | 0 |
| 2026-10-20T02:32:00.000Z | 0 |
| 2026-10-20T02:40:00.000Z | 0 |
| 2026-10-20T02:48:00.000Z | 0 |
| 2026-10-20T02:56:00.000Z | 0 |
| 2026-10-20T03:04:00.000Z | 0 |
| 2026-10-20T03:12:00.000Z | 0 |
| 2026-10-20T03:20:00.000Z | 0 |
| 2026-10-20T03:28:00.000Z | 0 |
| 2026-10-20T03:36:00.000Z | 0 |
| 2026-10-20T03:44:00.000Z | 48 |
| 2026-10-20T03:52:00.000Z | 40 |
| 2026-10-20T04:00:00.000Z | 0 |
| 2026-10-20T04:08:00.000Z | 0 |
| 2026-10-20T04:16:00.000Z | 0 |
| 2026-10-20T04:24:00.000Z | 0 |
| 2026-10-20T04:32:00.000Z | 0 |
| 2026-10-20T04:40:00.000Z | 0 |
| 2026-10-20T04:48:00.000Z | 0 |
| 2026-10-20T04:56:00.000Z | 0 |
| 2026-10-20T05:04:00.000Z | 0 |
| 2026-10-20T05:12:00.000Z | 0 |
| 2026-10-20T05:20:00.000Z | 67 |
| 2026-10-20T05:28:00.000Z | 100 |
| 2026-10-20T05:36:00.000Z | 0 |
| 2026-10-20T05:44:00.000Z | 0 |
| 2026-10-20T05:52:00.000Z | 0 |
| 2026-10-20T06:00:00.000Z | 0 |
| 2026-10-20T06:08:00.000Z | 0 |
| 2026-10-20T06:16:00.000Z | 0 |
| 2026-10-20T06:24:00.000Z | 0 |
| 2026-10-20T06:32:00.000Z | 0 |
| 2026-10-20T06:40:00.000Z | 0 |
| 2026-10-20T06:48:00.000Z | 0 |
| 2026-10-20T06:56:00.000Z | 0 |
| 2026-10-20T07:04:00.000Z | 0 |
| 2026-10-20T07:12:00.000Z | 0 |
| 2026-10-20T07:20:00.000Z | 0 |
| 2026-10-20T07:28:00.000Z | 0 |
| 2026-10-20T07:36:00.000Z | 0 |
| 2026-10-20T07:44:00.000Z | 0 |
| 2026-10-20T07:52:00.000Z | 0 |
| 2026-10-20T08:00:00.000Z | 0 |
| 2026-10-20T08:08:00.000Z | 0 |
| 2026-10-20T08:16:00.000Z | 0 |
| 2026-10-20T08:24:00.000Z | 0 |
| 2026-10-20T08:32:00.000Z | 0 |
| 2026-10-20T08:40:00.000Z | 0 |
| 2026-10-20T08:48:00.000Z | 0 |
| 2026-10-20T08:56:00.000Z | 0 |
| 2026-10-20T09:04:00.000Z | 0 |
| 2026-10-20T09:12:00.000Z | 0 |
| 2026-10-20T09:20:00.000Z | 0 |
| 2026-10-20T09:28:00.000Z | 0 |
| 2026-10-20T09:36:00.000Z | 0 |
| 2026-10-20T09:44:00.000Z | 0 |
| 2026-10-20T09:52:00.000Z | 0 |
| 2026-10-20T10:00:00.000Z | 0 |
| 2026-10-20T10:08:00.000Z | 0 |
| 2026-10-20T10:16:00.000Z | 0 |
| 2026-10-20T10:24:00.000Z | 0 |
| 2026-10-20T10:32:00.000Z | 0 |
| 2026-10-20T10:40:00.000Z | 0 |
| 2026-10-20T10:48:00.000Z | 0 |
| 2026-10-20T10:56:00.000Z | 0 |
| 2026-10-20T11:04:00.000Z | 0 |
| 2026-10-20T11:12:00.000Z | 0 |
| 2026-10-20T11:20:00.000Z | 0 |
| 2026-10-20T11:28:00.000Z | 0 |
| 2026-10-20T11:36:00.000Z | 0 |
| 2026-10-20T11:44:00.000Z | 0 |
| 2026-10-20T11:52:00.000Z | 0 |
| 2026-10-20T12:00:00.000Z | 0 |
| 2026-10-20T12:08:00.000Z | 0 |

## Evidence and recovery

Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary.

No recent recovery can be established from available evidence.

## Website measurements

Successful sampled checks (24h): 100% (266/266). Restricted checks: 0. Median response: 62 ms. P95 response: 99 ms.

These are sampled public website checks from one US server, not continuous uptime or authenticated app/API tests. Missing data stays unknown.

## Official provider evidence

Updated 2026-10-20T23:35:02.000Z.

- API: operational
- CloudFlare: operational
- Desktop: operational
- Atlanta: operational
- Brazil: operational
- Media Proxy: operational
- Tax Calculation Service: operational
- iOS: operational
- Rotterdam: operational
- Creator Payouts: operational
- Gateway: operational
- Android: operational
- Hong Kong: operational
- Push Notifications: operational
- Web: operational
- India: operational
- Search: operational
- Voice: operational
- Japan: operational
- Russia: operational
- Client: operational
- Singapore: operational
- Third-party: operational
- South Africa: operational
- Server Web Pages: operational
- South Korea: operational
- Payments: operational
- Sydney: operational
- Marketing Site: operational
- US Central: operational
- US East: operational
- US South: operational
- US West: operational

- [Elevated API error rate](https://stspg.io/d34fn55r326n): resolved; updated 2026-10-01T13:52:47.201-07:00
- [Age group status mismatch across devices](https://stspg.io/4pqvfhkn61px): resolved; updated 2026-09-23T20:32:10.678-07:00
- [Issue / Delay in establishing call connection](https://stspg.io/pf0pn82rjd7q): resolved; updated 2026-09-17T13:39:23.324-07:00
- [Issue establishing voice call](https://stspg.io/7qgn414rhr5z): resolved; updated 2026-09-16T15:35:09.343-07:00
- [API Errors](https://stspg.io/b8prjyxdvwf7): resolved; updated 2026-09-16T12:28:01.396-07:00
- [Google Pay Outage](https://stspg.io/9qdnzmhbn0pk): resolved; updated 2026-09-16T09:43:18.948-07:00
- [Session Unavailability](https://stspg.io/d5h0d8347s4l): resolved; updated 2026-09-15T08:16:18.190-07:00
- [Media Proxy Latency High](https://stspg.io/mpwbwtx3wm5q): resolved; updated 2026-09-11T10:46:19.613-07:00


## Daily outage history

Dates use America/New_York. Green means no issues observed with sufficient monitoring; pink means official incidents, repeated website failures, or reports from at least three network addresses. Gray means insufficient coverage. These are daily evidence summaries, not guaranteed uptime.

| Date | Daily assessment | Observed hours | Official incidents |
| --- | --- | --- | --- |
| 2026-01-24 | Service issues detected | 0 | 1 |
| 2026-01-25 | Service issues detected | 0 | 1 |
| 2026-01-27 | Service issues detected | 0 | 1 |
| 2026-02-28 | Service issues detected | 0 | 2 |
| 2026-03-04 | Service issues detected | 0 | 1 |
| 2026-03-05 | Service issues detected | 0 | 1 |
| 2026-03-09 | Service issues detected | 0 | 1 |
| 2026-03-11 | Service issues detected | 0 | 1 |
| 2026-03-12 | Service issues detected | 0 | 2 |
| 2026-03-19 | Service issues detected | 0 | 1 |
| 2026-03-20 | Service issues detected | 0 | 1 |
| 2026-03-25 | Service issues detected | 0 | 2 |
| 2026-03-28 | Service issues detected | 0 | 1 |
| 2026-04-06 | Service issues detected | 0 | 1 |
| 2026-04-16 | Service issues detected | 0 | 1 |
| 2026-04-18 | Service issues detected | 0 | 1 |
| 2026-04-28 | Service issues detected | 0 | 1 |
| 2026-05-02 | Service issues detected | 0 | 1 |
| 2026-05-08 | Service issues detected | 0 | 1 |
| 2026-05-21 | Service issues detected | 0 | 1 |
| 2026-06-09 | Service issues detected | 0 | 1 |
| 2026-06-10 | Service issues detected | 0 | 1 |
| 2026-06-29 | Service issues detected | 0 | 1 |
| 2026-07-10 | Service issues detected | 0 | 1 |
| 2026-07-16 | Service issues detected | 0 | 1 |
| 2026-07-22 | Service issues detected | 0 | 1 |
| 2026-07-27 | Service issues detected | 0 | 1 |
| 2026-08-04 | Service issues detected | 0 | 1 |
| 2026-08-07 | Service issues detected | 0 | 1 |
| 2026-08-14 | Service issues detected | 0 | 1 |
| 2026-08-31 | Service issues detected | 0 | 1 |
| 2026-09-02 | Service issues detected | 0 | 2 |
| 2026-09-03 | Service issues detected | 0 | 1 |
| 2026-09-11 | Service issues detected | 0 | 2 |
| 2026-09-16 | Service issues detected | 0 | 2 |
| 2026-09-17 | Service issues detected | 0 | 1 |
| 2026-09-23 | Service issues detected | 0 | 1 |
| 2026-10-01 | Service issues detected | 0 | 1 |
| 2026-10-19 | No issues observed | 24 | 0 |
| 2026-10-20 | Good so far | 20 | 0 |


## About Discord monitoring

This page combines the available Discord report activity, official product status, public website measurements, and daily history. Each measurement has its own observation time. A search spike alone does not confirm downtime, and a reachable website does not establish that sign-in or every product feature works.

## Troubleshooting

### Messages, calls, or sign-in fail

Compare messaging with voice or video, and compare the web app with your usual client. Record which feature fails instead of assuming every Discord feature is down.

## Frequently asked questions

### Is Discord down right now?

Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-10-20T23:35:14.000Z.

### How many Discord outage reports are there today?

The displayed rolling 24-hour window contains 0 recorded reports, from 2026-10-19T23:30:00.000Z to 2026-10-20T23:30:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.

### Why does Discord show operational when it is not working for me?

An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Discord feature.

### When was Discord status last updated?

The latest status observation was 2026-10-20T23:35:02.000Z. Only matched product components and incidents are shown. The assessment is recent.

### Has Discord had outages before?

The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.

### How do I follow Discord or report a problem?

Use “Watch this service” to save Discord in this browser’s watchlist, then return to compare its status with other saved services. The watchlist does not send notifications. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.


## Related services

- [Discord](https://iszdown.com/now/discord)