Is It Down? discord.com
UP
Current
200
HTTP Code
56
Response ms
100%
Uptime (20)
0
Outages
Response Time Last 20 Checks
UP DOWN
Recent Checks (Last 20 Pings)
| Time (America/New_York) | Status | HTTP Code | Response (ms) | |
|---|---|---|---|---|
| 20:53:51 · 12.05.2026 | UP | 200 | 56 | |
| 20:40:04 · 12.05.2026 | UP | 200 | 53 | |
| 20:20:04 · 12.05.2026 | UP | 200 | 76 | |
| 20:00:05 · 12.05.2026 | UP | 200 | 63 | |
| 19:40:04 · 12.05.2026 | UP | 200 | 67 | |
| 19:20:05 · 12.05.2026 | UP | 200 | 81 | |
| 19:00:05 · 12.05.2026 | UP | 200 | 50 | |
| 18:40:05 · 12.05.2026 | UP | 200 | 48 | |
| 18:20:05 · 12.05.2026 | UP | 200 | 74 | |
| 18:00:05 · 12.05.2026 | UP | 200 | 55 | |
| 17:40:04 · 12.05.2026 | UP | 200 | 65 | |
| 17:20:05 · 12.05.2026 | UP | 200 | 49 | |
| 17:00:05 · 12.05.2026 | UP | 200 | 58 | |
| 16:40:05 · 12.05.2026 | UP | 200 | 71 | |
| 16:20:05 · 12.05.2026 | UP | 200 | 72 | |
| 16:00:05 · 12.05.2026 | UP | 200 | 90 | |
| 15:40:04 · 12.05.2026 | UP | 200 | 62 | |
| 15:20:05 · 12.05.2026 | UP | 200 | 56 | |
| 15:00:07 · 12.05.2026 | UP | 200 | 108 | |
| 14:40:05 · 12.05.2026 | UP | 200 | 69 |
20:53:51
12.05.2026
UP HTTP 200 · 56ms
20:40:04
12.05.2026
UP HTTP 200 · 53ms
20:20:04
12.05.2026
UP HTTP 200 · 76ms
20:00:05
12.05.2026
UP HTTP 200 · 63ms
19:40:04
12.05.2026
UP HTTP 200 · 67ms
19:20:05
12.05.2026
UP HTTP 200 · 81ms
19:00:05
12.05.2026
UP HTTP 200 · 50ms
18:40:05
12.05.2026
UP HTTP 200 · 48ms
18:20:05
12.05.2026
UP HTTP 200 · 74ms
18:00:05
12.05.2026
UP HTTP 200 · 55ms
17:40:04
12.05.2026
UP HTTP 200 · 65ms
17:20:05
12.05.2026
UP HTTP 200 · 49ms
17:00:05
12.05.2026
UP HTTP 200 · 58ms
16:40:05
12.05.2026
UP HTTP 200 · 71ms
16:20:05
12.05.2026
UP HTTP 200 · 72ms
16:00:05
12.05.2026
UP HTTP 200 · 90ms
15:40:04
12.05.2026
UP HTTP 200 · 62ms
15:20:05
12.05.2026
UP HTTP 200 · 56ms
15:00:07
12.05.2026
UP HTTP 200 · 108ms
14:40:05
12.05.2026
UP HTTP 200 · 69ms
Last Detected Downtime
Recently Checked Sites
| Website | Status | HTTP | Response | Uptime | |
|---|---|---|---|---|---|
| DOWN | 6001 ms | 0% |
|||
| DOWN | 42 ms | 0% |
|||
| UP | 200 | 602 ms | 87.5% |
||
| UP | 200 | 60 ms | 100% |
||
| DOWN | 406 | 461 ms | 0% |
||
| UP | 200 | 4487 ms | 100% |
||
| UP | 200 | 46 ms | 100% |
||
| UP | 200 | 145 ms | 100% |
||
| UP | 200 | 332 ms | 15% |
||
| UP | 200 | 85 ms | 100% |
About This Check
We send an HTTP HEAD request from our Frankfurt, Germany server to discord.com. A response of HTTP 200–399 within 10 seconds = UP. Any timeout, DNS failure, or error code = DOWN. A rolling history of the last 20 checks is stored and displayed above.
If the site shows UP here but you can't access it, the issue is local flush your DNS cache (ipconfig /flushdns on Windows / sudo dscacheutil -flushcache on macOS) or try a different network.
For community-reported outage data and user comments, check DownDetector discord.com.