Is AncestralFire down?
Up
No, AncestralFire is up.
It passed its latest check 4 h ago in 809 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 4 h ago (25 Oct 2026, 05:43 UTC)
- Response time
- 809 ms (typical 1.2 s)
- Next check
- In about 6 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
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 |
|---|---|---|---|
| 25 Oct 2026, 05:43 UTC | Passed | 401 | 809 ms |
| 24 Oct 2026, 18:33 UTC | Passed | 401 | 1.0 s |
| 24 Oct 2026, 07:23 UTC | Passed | 401 | 955 ms |
| 23 Oct 2026, 20:56 UTC | Passed | 401 | 776 ms |
| 23 Oct 2026, 10:23 UTC | Passed | 401 | 1.2 s |
| 22 Oct 2026, 23:41 UTC | Passed | 401 | 129 ms |
| 22 Oct 2026, 13:18 UTC | Passed | 401 | 903 ms |
| 22 Oct 2026, 03:48 UTC | Passed | 401 | 534 ms |
| 21 Oct 2026, 18:11 UTC | Passed | 401 | 1.4 s |
| 21 Oct 2026, 08:59 UTC | Passed | 401 | 1.3 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.