Is exascale.build down?
Up
No, exascale.build is up.
It passed its latest check 9 h ago in 582 ms, and every check in the last 30 days.
Latest check
- Last check
- 9 h ago (10 Nov 2026, 07:21 UTC)
- Response time
- 582 ms (typical 448 ms)
- Next check
- In about 3 h
- How often
- About every 12 hours over the last 7 days
Uptime
Last 24 hours100%2 checks
Last 7 days100%13 checks
Last 30 days100%65 checks
All checks passedSome failedAll failedNot checked
Uptime is the share of checks that passed. We checked it about every 12 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 |
|---|---|---|---|
| 10 Nov 2026, 07:21 UTC | Passed | 200 | 582 ms |
| 9 Nov 2026, 19:43 UTC | Passed | 200 | 478 ms |
| 9 Nov 2026, 08:48 UTC | Passed | 200 | 447 ms |
| 8 Nov 2026, 22:31 UTC | Passed | 200 | 448 ms |
| 8 Nov 2026, 10:20 UTC | Passed | 200 | 426 ms |
| 7 Nov 2026, 23:47 UTC | Passed | 200 | 455 ms |
| 7 Nov 2026, 12:42 UTC | Passed | 200 | 475 ms |
| 7 Nov 2026, 00:09 UTC | Passed | 200 | 441 ms |
| 6 Nov 2026, 13:07 UTC | Passed | 200 | 488 ms |
| 6 Nov 2026, 01:34 UTC | Passed | 200 | 578 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 12 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.