Is 0n3 — every app you own, one sign-in, AI that executes down?
Up
No, 0n3 — every app you own, one sign-in, AI that executes is up.
It passed its latest check 2 h ago in 301 ms. It has passed every check since 26 Oct 2026, 12:09 UTC.
Latest check
- Last check
- 2 h ago (27 Oct 2026, 14:05 UTC)
- Response time
- 301 ms (typical 265 ms)
- Next check
- In about 11 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
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 |
|---|---|---|---|
| 27 Oct 2026, 14:05 UTC | Passed | 401 | 301 ms |
| 27 Oct 2026, 00:29 UTC | Passed | 401 | 244 ms |
| 26 Oct 2026, 12:09 UTC | Passed | 401 | 265 ms |
| 23 Oct 2026, 12:25 UTC | initialize returned HTTP 308 | 308 | 139 ms |
| 20 Oct 2026, 14:31 UTC | initialize returned HTTP 308 | 308 | 224 ms |
| 19 Oct 2026, 10:05 UTC | initialize returned HTTP 308 | 308 | 346 ms |
| 18 Oct 2026, 07:22 UTC | initialize returned HTTP 308 | 308 | 166 ms |
| 17 Oct 2026, 00:33 UTC | initialize returned HTTP 308 | 308 | 151 ms |
| 15 Oct 2026, 20:21 UTC | initialize returned HTTP 308 | 308 | 134 ms |
| 14 Oct 2026, 18:25 UTC | initialize returned HTTP 308 | 308 | 333 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 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.