Is Feason Context down?
Up
No, Feason Context is up.
It passed its latest check 4 h ago in 385 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 4 h ago (16 Oct 2026, 12:53 UTC)
- Response time
- 385 ms (typical 472 ms)
- 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 |
|---|---|---|---|
| 16 Oct 2026, 12:53 UTC | Passed | 401 | 385 ms |
| 16 Oct 2026, 03:12 UTC | Passed | 401 | 602 ms |
| 15 Oct 2026, 16:56 UTC | Passed | 401 | 419 ms |
| 15 Oct 2026, 06:54 UTC | Passed | 401 | 558 ms |
| 14 Oct 2026, 20:48 UTC | Passed | 401 | 382 ms |
| 14 Oct 2026, 11:07 UTC | Passed | 401 | 472 ms |
| 14 Oct 2026, 01:46 UTC | Passed | 401 | 389 ms |
| 13 Oct 2026, 16:48 UTC | Passed | 401 | 1.1 s |
| 13 Oct 2026, 07:59 UTC | Passed | 401 | 504 ms |
| 12 Oct 2026, 22:38 UTC | Passed | 401 | 281 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.