Is Timezone Converter API down?
Down
Yes, Timezone Converter API is down.
It has not passed a check since we started checking it on 11 Oct 2026. Latest error: Connection failed (ERR_SSL_TLSV1_ALERT_INTERNAL_ERROR).
Latest check
- Last check
- 15 h ago (15 Oct 2026, 21:57 UTC)
- Response time
- Not measured
- Next check
- In about 10 h
- How often
- About every 25 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 25 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 |
|---|---|---|---|
| 15 Oct 2026, 21:57 UTC | Connection failed (ERR_SSL_TLSV1_ALERT_INTERNAL_ERROR) | - | - |
| 14 Oct 2026, 18:28 UTC | Connection failed (ERR_SSL_TLSV1_ALERT_INTERNAL_ERROR) | - | - |
| 13 Oct 2026, 13:18 UTC | Connection failed (ERR_SSL_TLSV1_ALERT_INTERNAL_ERROR) | - | - |
| 12 Oct 2026, 12:00 UTC | Connection failed (ERR_SSL_TLSV1_ALERT_INTERNAL_ERROR) | - | - |
| 12 Oct 2026, 02:22 UTC | Connection failed (ERR_SSL_TLSV1_ALERT_INTERNAL_ERROR) | - | - |
| 11 Oct 2026, 17:52 UTC | Connection failed (ERR_SSL_TLSV1_ALERT_INTERNAL_ERROR) | - | - |
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 25 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.