Is Asia/Dushanbe 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/Dushanbe clock is up.

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

Latest check

Last check: 7 h ago (18 Oct 2026, 21:56 UTC)
Response time: 37 ms (typical 50 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:56 UTC	Passed	200	37 ms
18 Oct 2026, 11:31 UTC	Passed	200	61 ms
18 Oct 2026, 00:15 UTC	Passed	200	220 ms
17 Oct 2026, 13:41 UTC	Passed	200	299 ms
17 Oct 2026, 03:05 UTC	Passed	200	369 ms
16 Oct 2026, 16:12 UTC	Passed	200	56 ms
16 Oct 2026, 06:30 UTC	Passed	200	300 ms
15 Oct 2026, 20:43 UTC	Passed	200	60 ms
15 Oct 2026, 10:53 UTC	Passed	200	357 ms
15 Oct 2026, 00:31 UTC	Passed	200	3.1 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 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.