Is Workwae down?
Up
No, Workwae is up.
It passed its latest check 7 h ago in 100 ms. It has passed every check since 30 Oct 2026, 02:32 UTC.
Latest check
- Last check
- 7 h ago (1 Nov 2026, 19:34 UTC)
- Response time
- 100 ms (typical 588 ms)
- Next check
- In about 6 h
- How often
- About every 14 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 14 hours over the last 7 days.
Outages in the last 30 days
1 outage, 27 h of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 28 Oct 2026, 23:32 UTC | 27 h | 2 | api.workwae.com resolves to a private/reserved address |
Times are when our checks ran, about every 14 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 1 Nov 2026, 19:34 UTC | Passed | 403 | 100 ms |
| 1 Nov 2026, 09:40 UTC | Passed | 403 | 118 ms |
| 31 Oct 2026, 19:34 UTC | Passed | 403 | 117 ms |
| 31 Oct 2026, 05:12 UTC | Passed | 403 | 126 ms |
| 30 Oct 2026, 15:57 UTC | Passed | 403 | 205 ms |
| 30 Oct 2026, 02:32 UTC | Passed | 403 | 116 ms |
| 29 Oct 2026, 13:07 UTC | Connection failed (ENETUNREACH) | - | - |
| 28 Oct 2026, 23:32 UTC | api.workwae.com resolves to a private/reserved address | - | - |
| 28 Oct 2026, 09:50 UTC | Passed | 401 | 547 ms |
| 27 Oct 2026, 20:06 UTC | Passed | 401 | 2.3 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 14 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.