Is Legacy-Code-Migrator down?
Up
No, Legacy-Code-Migrator is up.
It passed its latest check 4 h ago in 77 ms. It has passed every check since 14 Oct 2026, 16:55 UTC.
Latest check
- Last check
- 4 h ago (16 Oct 2026, 07:42 UTC)
- Response time
- 77 ms (typical 97 ms)
- Next check
- In about 5 h
- How often
- About every 10 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 10 hours over the last 7 days.
Outages in the last 30 days
No outages in the last 30 days. An outage starts when two checks in a row fail and ends at the next passing check.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 16 Oct 2026, 07:42 UTC | Passed | 402 | 77 ms |
| 15 Oct 2026, 21:46 UTC | Passed | 402 | 77 ms |
| 15 Oct 2026, 12:31 UTC | Passed | 402 | 97 ms |
| 15 Oct 2026, 02:47 UTC | Passed | 402 | 170 ms |
| 14 Oct 2026, 16:55 UTC | Passed | 402 | 125 ms |
| 13 Oct 2026, 14:38 UTC | SSE endpoint did not open an event stream | 402 | 76 ms |
| 12 Oct 2026, 12:35 UTC | SSE endpoint did not open an event stream | 402 | 57 ms |
| 12 Oct 2026, 03:49 UTC | SSE endpoint did not open an event stream | 402 | 73 ms |
| 11 Oct 2026, 17:56 UTC | SSE endpoint did not open an event stream | 402 | 151 ms |
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 10 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.