Is Noonlaunch down?
Up
No, Noonlaunch is up.
It passed its latest check 9 h ago in 5.5 s. It has passed every check since 5 Nov 2026, 09:45 UTC.
Latest check
- Last check
- 9 h ago (8 Nov 2026, 00:05 UTC)
- Response time
- 5.5 s (typical 975 ms)
- Next check
- In about 3 h
- How often
- About every 13 hours over the last 7 days
Uptime
Last 24 hours100%2 checks
Last 7 days84.6%13 checks
Last 30 days89.5%19 checks
All checks passedSome failedAll failedNot checked
Uptime is the share of checks that passed. We checked it about every 13 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 |
|---|---|---|---|
| 8 Nov 2026, 00:05 UTC | Passed | 200 | 5.5 s |
| 7 Nov 2026, 12:23 UTC | Passed | 200 | 774 ms |
| 7 Nov 2026, 00:01 UTC | Passed | 200 | 1.0 s |
| 6 Nov 2026, 13:11 UTC | Passed | 200 | 882 ms |
| 6 Nov 2026, 01:10 UTC | Passed | 200 | 975 ms |
| 5 Nov 2026, 09:45 UTC | Passed | 200 | 1.1 s |
| 4 Nov 2026, 18:32 UTC | Connection failed (UND_ERR_INFO) | - | - |
| 4 Nov 2026, 04:12 UTC | Passed | 200 | 822 ms |
| 3 Nov 2026, 14:08 UTC | Passed | 200 | 3.4 s |
| 2 Nov 2026, 23:30 UTC | Timed out | - | - |
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 13 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.