Is It Down? subspace9.com
DOWN
Current
HTTP Code
6001
Response ms
0%
Uptime (20)
1
Outages
Error Details
Connection timeout after 6001 ms
Response Time Last 1 Checks
UP DOWN
Recent Checks (Last 20 Pings)
| Time (America/New_York) | Status | HTTP Code | Response (ms) | |
|---|---|---|---|---|
| 18:54:19 · 18.06.2026 | DOWN | 6001 |
18:54:19
18.06.2026
DOWN HTTP · 6001ms
Last Detected Downtime
Connection timeout after 6001 ms
All Recorded Outages
| Time (America/New_York) | HTTP | Response (ms) | Error | |
|---|---|---|---|---|
| 2026-06-18 18:54:19 | 6001 |
18:54:19
18.06.2026
DOWN
HTTP · 6001ms
Recently Checked Sites
| Website | Status | HTTP | Response | Uptime | |
|---|---|---|---|---|---|
| DOWN | 6000 ms | 0% |
|||
| DOWN | 28 ms | 0% |
|||
| UP | 200 | 297 ms | 100% |
||
| UP | 200 | 463 ms | 100% |
||
| DOWN | 6001 ms | 0% |
|||
| UP | 200 | 339 ms | 100% |
||
| UP | 403 | 21 ms | 100% |
||
| UP | 200 | 255 ms | 100% |
||
| UP | 200 | 735 ms | 100% |
||
| UP | 200 | 95 ms | 100% |
About This Check
We send an HTTP HEAD request from our Frankfurt, Germany server to subspace9.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.