Is Caesar down?
Down
Yes, Caesar is down.
It has failed every check since 14 Oct 2026, 19:09 UTC (4 days 16 h, 6 checks). Latest error: initialize returned HTTP 500. It last passed on 14 Oct 2026, 09:02 UTC.
Latest check
- Last check
- 6 h ago (19 Oct 2026, 05:01 UTC)
- Response time
- Not measured (typical 117 ms)
- Next check
- In about 21 h
- How often
- About every 10 hours over the last 7 days
Uptime
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
1 outage, 4 days 16 h of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 14 Oct 2026, 19:09 UTC | Ongoing, 4 days 16 h so far | 6 | initialize returned HTTP 500 |
Times are when our checks ran, about every 10 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 19 Oct 2026, 05:01 UTC | initialize returned HTTP 500 | 500 | 90 ms |
| 18 Oct 2026, 01:29 UTC | initialize returned HTTP 500 | 500 | 111 ms |
| 16 Oct 2026, 20:21 UTC | Timed out | - | - |
| 15 Oct 2026, 14:37 UTC | initialize returned HTTP 500 | 500 | 68 ms |
| 15 Oct 2026, 05:19 UTC | initialize returned HTTP 500 | 500 | 154 ms |
| 14 Oct 2026, 19:09 UTC | initialize returned HTTP 500 | 500 | 113 ms |
| 14 Oct 2026, 09:02 UTC | Passed | 401 | 113 ms |
| 13 Oct 2026, 23:26 UTC | Passed | 401 | 120 ms |
| 13 Oct 2026, 14:37 UTC | Passed | 401 | 169 ms |
| 13 Oct 2026, 05:21 UTC | Passed | 401 | 117 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.