Is Code Refactor down?
Up
No, Code Refactor is up.
It passed its latest check 4 h ago in 1.6 s. It has passed every check since 7 Nov 2026, 21:54 UTC.
Latest check
- Last check
- 4 h ago (10 Nov 2026, 06:08 UTC)
- Response time
- 1.6 s (typical 5.5 s)
- Next check
- In about 7 h
- How often
- About every 12 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 12 hours over the last 7 days.
Outages in the last 30 days
2 outages, 3 days 6 h of failed checks in total, the longest 2 days 2 h.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 29 Oct 2026, 01:22 UTC | 27 h 9 min | 2 | Timed out |
| 21 Oct 2026, 20:17 UTC | 2 days 2 h | 3 | initialize returned HTTP 501 |
Times are when our checks ran, about every 12 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 10 Nov 2026, 06:08 UTC | Passed | 200 | 1.6 s |
| 9 Nov 2026, 18:52 UTC | Passed | 200 | 5.5 s |
| 9 Nov 2026, 07:44 UTC | Passed | 200 | 5.4 s |
| 8 Nov 2026, 21:05 UTC | Passed | 200 | 5.6 s |
| 8 Nov 2026, 09:11 UTC | Passed | 200 | 5.6 s |
| 7 Nov 2026, 21:54 UTC | Passed | 200 | 5.2 s |
| 7 Nov 2026, 10:23 UTC | Timed out | - | - |
| 6 Nov 2026, 22:49 UTC | Passed | 200 | 2.8 s |
| 6 Nov 2026, 11:38 UTC | Passed | 200 | 2.5 s |
| 5 Nov 2026, 23:35 UTC | Passed | 200 | 4.5 s |
How we check
Up means the MCP handshake and the tool list worked, or the server asked for sign-in or payment.
Checks come from our server, about every 12 hours for this listing over the last 7 days. A failure can also mean the service blocks our checks. Two failed checks in a row count as an outage, which ends at the next passing check.
If you think a check is wrong, contact hello@toolvet.app. More on how we check and score.