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

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

Latest check

Last check: 2 h ago (19 Oct 2026, 03:13 UTC)
Response time: 36 ms (typical 43 ms)
Next check: In about 8 h
How often: About every 10 hours over the last 7 days

Uptime

Last 24 hours100%3 checks

Last 7 days100%17 checks

Last 30 days100%19 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
19 Oct 2026, 03:13 UTC	Passed	200	36 ms
18 Oct 2026, 19:02 UTC	Passed	200	92 ms
18 Oct 2026, 08:45 UTC	Passed	200	42 ms
17 Oct 2026, 22:13 UTC	Passed	200	36 ms
17 Oct 2026, 12:02 UTC	Passed	200	43 ms
17 Oct 2026, 01:30 UTC	Passed	200	33 ms
16 Oct 2026, 15:34 UTC	Passed	200	65 ms
16 Oct 2026, 05:05 UTC	Passed	200	291 ms
15 Oct 2026, 18:46 UTC	Passed	200	315 ms
15 Oct 2026, 09:35 UTC	Passed	200	58 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.