Yes, https://quox.ai is up. I asked our uptime specialist, Beacon, to check it just now.
•Status:200 OK
•Response time:469 ms
•TLS and errors: none. The HTTPS request completed cleanly, with no certificate or
connection problems.
There's nothing to act on. I can keep watching it or check it again if you want.
26.3s · 1 tool · 0 approvals
A real turn on our own install (CLI 0.3.0, 17 Oct 2026), replayed at speed. Names changed. Type the same words into quox. ✔ Machine verified against the CLI on 17 Oct 2026 · test report mvcnp7
Quox asked BEACON, the uptime agent, to check the site. It reported the status code, the response time and that the HTTPS connection was clean.
Run the same uptime check. It takes a list of addresses, so you can check several at once:
uptime
$ quox tool exec uptime_check --input '{"urls":["https://quox.ai"]}' --select responseHere is exactly what the uptime check returned (source: uptime_check).**https://quox.ai is up.**| Field | Value ||-------|-------|| URL | https://quox.ai || HTTP status | 200 || Latency | 756 ms || Healthy | yes |Summary: 1 checked, 1 healthy, 0 unhealthy. Nothing was changed, this was a read-only probe.
From a real run on our own install, later the same day as the conversation above. The check runs through BEACON, so the reply is BEACON's summary of the tool's result.
Pass "urls" as a list, even for one address. --select response keeps just the answer.