Is It Down? — twitch.tv
UP
Current
200
HTTP Code
84
Response ms
100%
Uptime (20)
1
Outages
Response Time — Last 20 Checks
UP DOWN
Recent Checks (Last 20 Pings)
| Time (America/New_York) | Status | HTTP Code | Response (ms) | |
|---|---|---|---|---|
| 06:34:48 · 15.03.2026 | UP | 200 | 84 | |
| 06:20:05 · 15.03.2026 | UP | 200 | 86 | |
| 06:00:05 · 15.03.2026 | UP | 200 | 81 | |
| 05:40:05 · 15.03.2026 | UP | 200 | 77 | |
| 05:20:05 · 15.03.2026 | UP | 200 | 79 | |
| 05:00:05 · 15.03.2026 | UP | 200 | 84 | |
| 04:55:34 · 15.03.2026 | UP | 200 | 90 | |
| 04:40:05 · 15.03.2026 | UP | 200 | 78 | |
| 04:20:05 · 15.03.2026 | UP | 200 | 87 | |
| 04:00:05 · 15.03.2026 | UP | 200 | 77 | |
| 03:40:05 · 15.03.2026 | UP | 200 | 86 | |
| 03:20:05 · 15.03.2026 | UP | 200 | 99 | |
| 03:00:05 · 15.03.2026 | UP | 200 | 80 | |
| 02:40:05 · 15.03.2026 | UP | 200 | 77 | |
| 02:23:49 · 15.03.2026 | UP | 200 | 80 | |
| 02:20:05 · 15.03.2026 | UP | 200 | 74 | |
| 02:16:04 · 15.03.2026 | UP | 200 | 88 | |
| 02:00:04 · 15.03.2026 | UP | 200 | 82 | |
| 01:56:20 · 15.03.2026 | UP | 200 | 76 | |
| 01:40:06 · 15.03.2026 | UP | 200 | 73 |
06:34:48
15.03.2026
UP HTTP 200 · 84ms
06:20:05
15.03.2026
UP HTTP 200 · 86ms
06:00:05
15.03.2026
UP HTTP 200 · 81ms
05:40:05
15.03.2026
UP HTTP 200 · 77ms
05:20:05
15.03.2026
UP HTTP 200 · 79ms
05:00:05
15.03.2026
UP HTTP 200 · 84ms
04:55:34
15.03.2026
UP HTTP 200 · 90ms
04:40:05
15.03.2026
UP HTTP 200 · 78ms
04:20:05
15.03.2026
UP HTTP 200 · 87ms
04:00:05
15.03.2026
UP HTTP 200 · 77ms
03:40:05
15.03.2026
UP HTTP 200 · 86ms
03:20:05
15.03.2026
UP HTTP 200 · 99ms
03:00:05
15.03.2026
UP HTTP 200 · 80ms
02:40:05
15.03.2026
UP HTTP 200 · 77ms
02:23:49
15.03.2026
UP HTTP 200 · 80ms
02:20:05
15.03.2026
UP HTTP 200 · 74ms
02:16:04
15.03.2026
UP HTTP 200 · 88ms
02:00:04
15.03.2026
UP HTTP 200 · 82ms
01:56:20
15.03.2026
UP HTTP 200 · 76ms
01:40:06
15.03.2026
UP HTTP 200 · 73ms
Last Detected Downtime
Resolving timed out after 10000 milliseconds
All Recorded Outages
| Time (America/New_York) | HTTP | Response (ms) | Error | |
|---|---|---|---|---|
| 2026-02-25 16:10:46 | — | 28028 |
16:10:46
25.02.2026
DOWN
HTTP — · 28028ms
Recently Checked Sites
| Website | Status | HTTP | Response | Uptime | |
|---|---|---|---|---|---|
| UP | 200 | 43 ms | 100% |
||
| UP | 200 | 289 ms | 100% |
||
| UP | 200 | 84 ms | 100% |
||
| UP | 200 | 229 ms | 100% |
||
| UP | 200 | 322 ms | 100% |
||
| UP | 200 | 347 ms | 81.3% |
||
| UP | 200 | 109 ms | 100% |
||
| UP | 200 | 109 ms | 100% |
||
| UP | 200 | 327 ms | 100% |
||
| UP | 200 | 731 ms | 100% |
About This Check
We send an HTTP HEAD request from our Frankfurt, Germany server to twitch.tv. 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 — twitch.tv.