Current Status

Error

Last checked: 7/2/2025, 10:43:25 AM

Response Time

240 ms

Uptime

0.00%
Uptime Last 1 Days

Each bar represents a check. Hover for details.

Monitoring History
144 Checks
Time Status Response Time Message
7/2/2025, 10:43:25 AM Error 240 ms Service returned unexpected status code: 404
7/2/2025, 10:33:24 AM Error 194 ms Service returned unexpected status code: 404
7/2/2025, 10:23:24 AM Error 291 ms Service returned unexpected status code: 404
7/2/2025, 10:13:28 AM Error 161 ms Service returned unexpected status code: 404
7/2/2025, 10:03:23 AM Error 197 ms Service returned unexpected status code: 404
7/2/2025, 9:53:23 AM Error 261 ms Service returned unexpected status code: 404
7/2/2025, 9:43:27 AM Error 192 ms Service returned unexpected status code: 404
7/2/2025, 9:33:22 AM Error 164 ms Service returned unexpected status code: 404
7/2/2025, 9:23:24 AM Error 245 ms Service returned unexpected status code: 404
7/2/2025, 9:18:57 AM Error 206 ms Service returned unexpected status code: 404
7/2/2025, 9:08:48 AM Error 129 ms Service returned unexpected status code: 404
7/2/2025, 8:58:50 AM Error 199 ms Service returned unexpected status code: 404
7/2/2025, 8:46:21 AM Error 131 ms Service returned unexpected status code: 404
7/2/2025, 8:36:23 AM Error 158 ms Service returned unexpected status code: 404
7/2/2025, 8:26:20 AM Error 226 ms Service returned unexpected status code: 404
7/2/2025, 8:16:19 AM Error 151 ms Service returned unexpected status code: 404
7/2/2025, 8:06:29 AM Error 137 ms Service returned unexpected status code: 404
7/2/2025, 7:56:19 AM Error 165 ms Service returned unexpected status code: 404
7/2/2025, 7:46:20 AM Error 1057 ms Service returned unexpected status code: 404
7/2/2025, 7:36:23 AM Error 181 ms Service returned unexpected status code: 404
7/2/2025, 7:26:25 AM Error 126 ms Service returned unexpected status code: 404
7/2/2025, 7:16:21 AM Error 208 ms Service returned unexpected status code: 404
7/2/2025, 7:06:19 AM Error 149 ms Service returned unexpected status code: 404
7/2/2025, 6:56:19 AM Error 146 ms Service returned unexpected status code: 404
7/2/2025, 6:46:19 AM Error 144 ms Service returned unexpected status code: 404
7/2/2025, 6:36:17 AM Error 118 ms Service returned unexpected status code: 404
7/2/2025, 6:26:19 AM Error 202 ms Service returned unexpected status code: 404
7/2/2025, 6:16:17 AM Error 157 ms Service returned unexpected status code: 404
7/2/2025, 6:06:18 AM Error 218 ms Service returned unexpected status code: 404
7/2/2025, 5:56:18 AM Error 129 ms Service returned unexpected status code: 404
7/2/2025, 5:46:19 AM Error 231 ms Service returned unexpected status code: 404
7/2/2025, 5:36:18 AM Error 150 ms Service returned unexpected status code: 404
7/2/2025, 5:26:14 AM Error 131 ms Service returned unexpected status code: 404
7/2/2025, 5:16:21 AM Error 160 ms Service returned unexpected status code: 404
7/2/2025, 5:06:13 AM Error 212 ms Service returned unexpected status code: 404
7/2/2025, 4:56:12 AM Error 136 ms Service returned unexpected status code: 404
7/2/2025, 4:46:15 AM Error 137 ms Service returned unexpected status code: 404
7/2/2025, 4:36:15 AM Error 140 ms Service returned unexpected status code: 404
7/2/2025, 4:26:14 AM Error 225 ms Service returned unexpected status code: 404
7/2/2025, 4:16:15 AM Error 344 ms Service returned unexpected status code: 404
7/2/2025, 4:06:15 AM Error 229 ms Service returned unexpected status code: 404
7/2/2025, 3:56:14 AM Error 118 ms Service returned unexpected status code: 404
7/2/2025, 3:46:13 AM Error 152 ms Service returned unexpected status code: 404
7/2/2025, 3:36:14 AM Error 142 ms Service returned unexpected status code: 404
7/2/2025, 3:26:13 AM Error 160 ms Service returned unexpected status code: 404
7/2/2025, 3:16:13 AM Error 210 ms Service returned unexpected status code: 404
7/2/2025, 3:06:14 AM Error 139 ms Service returned unexpected status code: 404
7/2/2025, 2:56:18 AM Error 127 ms Service returned unexpected status code: 404
7/2/2025, 2:46:13 AM Error 198 ms Service returned unexpected status code: 404
7/2/2025, 2:36:13 AM Error 124 ms Service returned unexpected status code: 404
7/2/2025, 2:26:14 AM Error 148 ms Service returned unexpected status code: 404
7/2/2025, 2:16:14 AM Error 172 ms Service returned unexpected status code: 404
7/2/2025, 2:06:15 AM Error 141 ms Service returned unexpected status code: 404
7/2/2025, 1:56:15 AM Error 119 ms Service returned unexpected status code: 404
7/2/2025, 1:46:16 AM Error 125 ms Service returned unexpected status code: 404
7/2/2025, 1:36:13 AM Error 149 ms Service returned unexpected status code: 404
7/2/2025, 1:26:14 AM Error 180 ms Service returned unexpected status code: 404
7/2/2025, 1:16:13 AM Error 151 ms Service returned unexpected status code: 404
7/2/2025, 1:06:14 AM Error 143 ms Service returned unexpected status code: 404
7/2/2025, 12:56:13 AM Error 259 ms Service returned unexpected status code: 404
7/2/2025, 12:46:12 AM Error 131 ms Service returned unexpected status code: 404
7/2/2025, 12:36:18 AM Error 147 ms Service returned unexpected status code: 404
7/2/2025, 12:26:15 AM Error 289 ms Service returned unexpected status code: 404
7/2/2025, 12:16:15 AM Error 211 ms Service returned unexpected status code: 404
7/2/2025, 12:06:14 AM Error 117 ms Service returned unexpected status code: 404
7/1/2025, 11:56:14 PM Error 119 ms Service returned unexpected status code: 404
7/1/2025, 11:46:14 PM Error 169 ms Service returned unexpected status code: 404
7/1/2025, 11:36:14 PM Error 246 ms Service returned unexpected status code: 404
7/1/2025, 11:26:16 PM Error 130 ms Service returned unexpected status code: 404
7/1/2025, 11:16:13 PM Error 133 ms Service returned unexpected status code: 404
7/1/2025, 11:06:13 PM Error 165 ms Service returned unexpected status code: 404
7/1/2025, 10:56:14 PM Error 119 ms Service returned unexpected status code: 404
7/1/2025, 10:46:14 PM Error 146 ms Service returned unexpected status code: 404
7/1/2025, 10:36:14 PM Error 188 ms Service returned unexpected status code: 404
7/1/2025, 10:26:16 PM Error 479 ms Service returned unexpected status code: 404
7/1/2025, 10:16:17 PM Error 203 ms Service returned unexpected status code: 404
7/1/2025, 10:06:13 PM Error 181 ms Service returned unexpected status code: 404
7/1/2025, 9:56:14 PM Error 194 ms Service returned unexpected status code: 404
7/1/2025, 9:46:14 PM Error 156 ms Service returned unexpected status code: 404
7/1/2025, 9:36:14 PM Error 160 ms Service returned unexpected status code: 404
7/1/2025, 9:26:13 PM Error 139 ms Service returned unexpected status code: 404
7/1/2025, 9:16:14 PM Error 135 ms Service returned unexpected status code: 404
7/1/2025, 9:06:16 PM Error 218 ms Service returned unexpected status code: 404
7/1/2025, 8:56:12 PM Error 130 ms Service returned unexpected status code: 404
7/1/2025, 8:46:12 PM Error 224 ms Service returned unexpected status code: 404
7/1/2025, 8:36:14 PM Error 162 ms Service returned unexpected status code: 404
7/1/2025, 8:26:13 PM Error 142 ms Service returned unexpected status code: 404
7/1/2025, 8:16:14 PM Error 238 ms Service returned unexpected status code: 404
7/1/2025, 8:06:12 PM Error 210 ms Service returned unexpected status code: 404
7/1/2025, 7:56:17 PM Error 223 ms Service returned unexpected status code: 404
7/1/2025, 7:46:13 PM Error 147 ms Service returned unexpected status code: 404
7/1/2025, 7:36:13 PM Error 169 ms Service returned unexpected status code: 404
7/1/2025, 7:26:12 PM Error 131 ms Service returned unexpected status code: 404
7/1/2025, 7:16:12 PM Error 164 ms Service returned unexpected status code: 404
7/1/2025, 7:06:12 PM Error 117 ms Service returned unexpected status code: 404
7/1/2025, 6:56:12 PM Error 122 ms Service returned unexpected status code: 404
7/1/2025, 6:46:22 PM Error 502 ms Service returned unexpected status code: 404
7/1/2025, 6:36:14 PM Error 198 ms Service returned unexpected status code: 404
7/1/2025, 6:26:13 PM Error 222 ms Service returned unexpected status code: 404
7/1/2025, 6:16:14 PM Error 161 ms Service returned unexpected status code: 404
7/1/2025, 6:06:13 PM Error 240 ms Service returned unexpected status code: 404
7/1/2025, 5:56:14 PM Error 181 ms Service returned unexpected status code: 404
7/1/2025, 5:46:14 PM Error 151 ms Service returned unexpected status code: 404
7/1/2025, 5:36:18 PM Error 208 ms Service returned unexpected status code: 404
7/1/2025, 5:26:12 PM Error 109 ms Service returned unexpected status code: 404
7/1/2025, 5:16:14 PM Error 157 ms Service returned unexpected status code: 404
7/1/2025, 5:06:14 PM Error 158 ms Service returned unexpected status code: 404
7/1/2025, 4:56:12 PM Error 163 ms Service returned unexpected status code: 404
7/1/2025, 4:46:12 PM Error 145 ms Service returned unexpected status code: 404
7/1/2025, 4:36:14 PM Error 180 ms Service returned unexpected status code: 404
7/1/2025, 4:26:27 PM Error 144 ms Service returned unexpected status code: 404
7/1/2025, 4:16:12 PM Error 167 ms Service returned unexpected status code: 404
7/1/2025, 4:06:13 PM Error 105 ms Service returned unexpected status code: 404
7/1/2025, 3:56:13 PM Error 268 ms Service returned unexpected status code: 404
7/1/2025, 3:46:14 PM Error 202 ms Service returned unexpected status code: 404
7/1/2025, 3:36:14 PM Error 168 ms Service returned unexpected status code: 404
7/1/2025, 3:26:18 PM Error 150 ms Service returned unexpected status code: 404
7/1/2025, 3:16:13 PM Error 162 ms Service returned unexpected status code: 404
7/1/2025, 3:06:12 PM Error 128 ms Service returned unexpected status code: 404
7/1/2025, 2:56:14 PM Error 194 ms Service returned unexpected status code: 404
7/1/2025, 2:46:13 PM Error 181 ms Service returned unexpected status code: 404
7/1/2025, 2:36:14 PM Error 166 ms Service returned unexpected status code: 404
7/1/2025, 2:26:15 PM Error 342 ms Service returned unexpected status code: 404
7/1/2025, 2:16:16 PM Error 181 ms Service returned unexpected status code: 404
7/1/2025, 2:06:12 PM Error 127 ms Service returned unexpected status code: 404
7/1/2025, 1:56:14 PM Error 230 ms Service returned unexpected status code: 404
7/1/2025, 1:46:14 PM Error 185 ms Service returned unexpected status code: 404
7/1/2025, 1:36:14 PM Error 144 ms Service returned unexpected status code: 404
7/1/2025, 1:26:14 PM Error 150 ms Service returned unexpected status code: 404
7/1/2025, 1:16:15 PM Error 203 ms Service returned unexpected status code: 404
7/1/2025, 1:06:17 PM Error 143 ms Service returned unexpected status code: 404
7/1/2025, 12:56:13 PM Error 242 ms Service returned unexpected status code: 404
7/1/2025, 12:46:12 PM Error 137 ms Service returned unexpected status code: 404
7/1/2025, 12:36:18 PM Error 281 ms Service returned unexpected status code: 404
7/1/2025, 12:26:14 PM Error 124 ms Service returned unexpected status code: 404
7/1/2025, 12:16:14 PM Error 131 ms Service returned unexpected status code: 404
7/1/2025, 12:06:14 PM Error 151 ms Service returned unexpected status code: 404
7/1/2025, 11:56:18 AM Error 149 ms Service returned unexpected status code: 404
7/1/2025, 11:46:13 AM Error 260 ms Service returned unexpected status code: 404
7/1/2025, 11:36:14 AM Error 186 ms Service returned unexpected status code: 404
7/1/2025, 11:26:14 AM Error 197 ms Service returned unexpected status code: 404
7/1/2025, 11:16:14 AM Error 231 ms Service returned unexpected status code: 404
7/1/2025, 11:06:14 AM Error 145 ms Service returned unexpected status code: 404
7/1/2025, 10:56:12 AM Error 112 ms Service returned unexpected status code: 404