Is Blockscout down?
Up
No, Blockscout is up.
It passed its latest check 1 h ago in 98 ms. It has passed every check since 16 Oct 2026, 22:21 UTC.
Latest check
- Last check
- 1 h ago (18 Oct 2026, 17:03 UTC)
- Response time
- 98 ms (typical 114 ms)
- Next check
- In about 10 h
- How often
- About every 10 hours over the last 7 days
Uptime
Last 24 hours100%3 checks
Last 7 days94.4%18 checks
Last 30 days94.4%18 checks
All checks passedSome failedAll failedNot checked
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 |
|---|---|---|---|
| 18 Oct 2026, 17:03 UTC | Passed | 200 | 98 ms |
| 18 Oct 2026, 06:01 UTC | Passed | 200 | 191 ms |
| 17 Oct 2026, 18:58 UTC | Passed | 200 | 358 ms |
| 17 Oct 2026, 08:17 UTC | Passed | 200 | 59 ms |
| 16 Oct 2026, 22:21 UTC | Passed | 200 | 201 ms |
| 16 Oct 2026, 12:07 UTC | Timed out | - | - |
| 16 Oct 2026, 01:54 UTC | Passed | 200 | 68 ms |
| 15 Oct 2026, 15:45 UTC | Passed | 200 | 114 ms |
| 15 Oct 2026, 05:39 UTC | Passed | 200 | 142 ms |
| 14 Oct 2026, 19:40 UTC | Passed | 200 | 74 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.