Is It Down? sc.gov
UP
Current
403
HTTP Code
21
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) | |
|---|---|---|---|---|
| 05:04:03 · 15.06.2026 | UP | 403 | 21 | |
| 05:03:02 · 15.06.2026 | UP | 403 | 31 | |
| 09:29:57 · 03.06.2026 | UP | 403 | 80 | |
| 03:36:47 · 01.06.2026 | UP | 403 | 77 | |
| 11:41:54 · 31.05.2026 | UP | 403 | 82 | |
| 04:02:55 · 31.05.2026 | UP | 403 | 80 | |
| 09:59:25 · 30.05.2026 | UP | 403 | 95 | |
| 18:40:48 · 29.05.2026 | UP | 403 | 91 | |
| 06:33:20 · 25.05.2026 | UP | 403 | 84 | |
| 06:12:33 · 24.05.2026 | UP | 403 | 57 | |
| 17:16:48 · 23.05.2026 | UP | 403 | 88 | |
| 07:36:52 · 23.05.2026 | UP | 403 | 78 | |
| 22:39:17 · 21.05.2026 | UP | 403 | 80 | |
| 08:26:15 · 20.05.2026 | UP | 403 | 82 | |
| 13:28:39 · 18.05.2026 | UP | 403 | 97 | |
| 12:14:07 · 18.05.2026 | UP | 403 | 77 | |
| 07:00:25 · 18.05.2026 | UP | 403 | 73 | |
| 01:17:45 · 13.05.2026 | UP | 403 | 51 | |
| 11:20:09 · 12.05.2026 | UP | 403 | 80 | |
| 10:20:34 · 12.05.2026 | UP | 403 | 66 |
05:04:03
15.06.2026
UP HTTP 403 · 21ms
05:03:02
15.06.2026
UP HTTP 403 · 31ms
09:29:57
03.06.2026
UP HTTP 403 · 80ms
03:36:47
01.06.2026
UP HTTP 403 · 77ms
11:41:54
31.05.2026
UP HTTP 403 · 82ms
04:02:55
31.05.2026
UP HTTP 403 · 80ms
09:59:25
30.05.2026
UP HTTP 403 · 95ms
18:40:48
29.05.2026
UP HTTP 403 · 91ms
06:33:20
25.05.2026
UP HTTP 403 · 84ms
06:12:33
24.05.2026
UP HTTP 403 · 57ms
17:16:48
23.05.2026
UP HTTP 403 · 88ms
07:36:52
23.05.2026
UP HTTP 403 · 78ms
22:39:17
21.05.2026
UP HTTP 403 · 80ms
08:26:15
20.05.2026
UP HTTP 403 · 82ms
13:28:39
18.05.2026
UP HTTP 403 · 97ms
12:14:07
18.05.2026
UP HTTP 403 · 77ms
07:00:25
18.05.2026
UP HTTP 403 · 73ms
01:17:45
13.05.2026
UP HTTP 403 · 51ms
11:20:09
12.05.2026
UP HTTP 403 · 80ms
10:20:34
12.05.2026
UP HTTP 403 · 66ms
Last Detected Downtime
Recently Checked Sites
| Website | Status | HTTP | Response | Uptime | |
|---|---|---|---|---|---|
| UP | 403 | 21 ms | 100% |
||
| UP | 200 | 255 ms | 100% |
||
| UP | 200 | 311 ms | 100% |
||
| UP | 200 | 735 ms | 100% |
||
| UP | 200 | 95 ms | 100% |
||
| UP | 200 | 302 ms | 100% |
||
| DOWN | 503 | 110 ms | 40% |
||
| UP | 200 | 172 ms | 100% |
||
| UP | 403 | 5052 ms | 100% |
||
| DOWN | 6001 ms | 0% |
About This Check
We send an HTTP HEAD request from our Frankfurt, Germany server to sc.gov. 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.