Is Asia/Almaty clock down?

MCP serverBy agent-observatory-sensor.nolimit-observatory.workers.dev. How to connect and its trust score are on the listing page.

No, Asia/Almaty clock is up.

It passed its latest check 7 h ago in 54 ms, and every check since we started checking it on 11 Oct 2026.

Latest check

Last check: 7 h ago (18 Oct 2026, 21:51 UTC)
Response time: 54 ms (typical 58 ms)
Next check: In about 3 h
How often: About every 10 hours over the last 7 days

Uptime

Last 24 hours100%2 checks

Last 7 days100%17 checks

Last 30 days100%18 checks

All checks passedSome failedAll failedNot checked

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
18 Oct 2026, 21:51 UTC	Passed	200	54 ms
18 Oct 2026, 10:59 UTC	Passed	200	374 ms
18 Oct 2026, 00:16 UTC	Passed	200	406 ms
17 Oct 2026, 13:51 UTC	Passed	200	309 ms
17 Oct 2026, 03:26 UTC	Passed	200	130 ms
16 Oct 2026, 16:32 UTC	Passed	200	157 ms
16 Oct 2026, 05:58 UTC	Passed	200	58 ms
15 Oct 2026, 19:56 UTC	Passed	200	89 ms
15 Oct 2026, 09:54 UTC	Passed	200	360 ms
14 Oct 2026, 23:55 UTC	Passed	200	51 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.