Is It Down? zoovilleforum.net
DOWN
Current
HTTP Code
3072
Response ms
68.4%
Uptime (20)
6
Outages
Error Details
Failed to connect to zoovilleforum.net port 443 after 3071 ms: No route to host
Response Time Last 19 Checks
UP DOWN
Recent Checks (Last 20 Pings)
| Time (America/New_York) | Status | HTTP Code | Response (ms) | |
|---|---|---|---|---|
| 21:11:21 · 27.07.2026 | DOWN | 3072 | ||
| 04:40:14 · 27.07.2026 | DOWN | 3104 | ||
| 04:39:06 · 27.07.2026 | DOWN | 2809 | ||
| 18:13:32 · 26.07.2026 | DOWN | 6001 | ||
| 17:55:42 · 26.07.2026 | DOWN | 6001 | ||
| 23:33:17 · 23.07.2026 | UP | 200 | 344 | |
| 11:18:36 · 23.07.2026 | UP | 301 | 235 | |
| 11:18:34 · 23.07.2026 | UP | 200 | 345 | |
| 09:01:48 · 23.07.2026 | UP | 200 | 346 | |
| 03:19:27 · 23.07.2026 | UP | 200 | 351 | |
| 12:09:29 · 22.07.2026 | UP | 200 | 347 | |
| 11:19:57 · 19.07.2026 | UP | 200 | 373 | |
| 10:54:58 · 19.07.2026 | UP | 200 | 374 | |
| 07:45:41 · 19.07.2026 | UP | 200 | 371 | |
| 03:41:19 · 18.07.2026 | UP | 200 | 373 | |
| 03:40:18 · 18.07.2026 | UP | 200 | 389 | |
| 10:31:24 · 15.07.2026 | UP | 200 | 385 | |
| 10:29:15 · 15.07.2026 | UP | 200 | 383 | |
| 18:12:20 · 08.07.2026 | DOWN | 58 |
21:11:21
27.07.2026
DOWN HTTP · 3072ms
04:40:14
27.07.2026
DOWN HTTP · 3104ms
04:39:06
27.07.2026
DOWN HTTP · 2809ms
18:13:32
26.07.2026
DOWN HTTP · 6001ms
17:55:42
26.07.2026
DOWN HTTP · 6001ms
23:33:17
23.07.2026
UP HTTP 200 · 344ms
11:18:36
23.07.2026
UP HTTP 301 · 235ms
11:18:34
23.07.2026
UP HTTP 200 · 345ms
09:01:48
23.07.2026
UP HTTP 200 · 346ms
03:19:27
23.07.2026
UP HTTP 200 · 351ms
12:09:29
22.07.2026
UP HTTP 200 · 347ms
11:19:57
19.07.2026
UP HTTP 200 · 373ms
10:54:58
19.07.2026
UP HTTP 200 · 374ms
07:45:41
19.07.2026
UP HTTP 200 · 371ms
03:41:19
18.07.2026
UP HTTP 200 · 373ms
03:40:18
18.07.2026
UP HTTP 200 · 389ms
10:31:24
15.07.2026
UP HTTP 200 · 385ms
10:29:15
15.07.2026
UP HTTP 200 · 383ms
18:12:20
08.07.2026
DOWN HTTP · 58ms
Last Detected Downtime
Failed to connect to zoovilleforum.net port 443 after 3071 ms: No route to host
All Recorded Outages
| Time (America/New_York) | HTTP | Response (ms) | Error | |
|---|---|---|---|---|
| 2026-07-27 21:11:21 | 3072 | |||
| 2026-07-27 04:40:14 | 3104 | |||
| 2026-07-27 04:39:06 | 2809 | |||
| 2026-07-26 18:13:32 | 6001 | |||
| 2026-07-26 17:55:42 | 6001 | |||
| 2026-07-08 18:12:20 | 58 |
21:11:21
27.07.2026
DOWN
HTTP · 3072ms
04:40:14
27.07.2026
DOWN
HTTP · 3104ms
04:39:06
27.07.2026
DOWN
HTTP · 2809ms
18:13:32
26.07.2026
DOWN
HTTP · 6001ms
17:55:42
26.07.2026
DOWN
HTTP · 6001ms
18:12:20
08.07.2026
DOWN
HTTP · 58ms
Recently Checked Sites
| Website | Status | HTTP | Response | Uptime | |
|---|---|---|---|---|---|
| DOWN | 3072 ms | 68.4% |
|||
| UP | 200 | 91 ms | 100% |
||
| UP | 200 | 946 ms | 100% |
||
| UP | 200 | 592 ms | 100% |
||
| DOWN | 0 ms | 0% |
|||
| UP | 200 | 270 ms | 100% |
||
| UP | 200 | 388 ms | 100% |
||
| DOWN | 6002 ms | 0% |
|||
| UP | 200 | 240 ms | 100% |
||
| UP | 403 | 22 ms | 100% |
About This Check
We send an HTTP HEAD request from our Frankfurt, Germany server to zoovilleforum.net. 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.