Is Statscan down?
Down
Yes, Statscan is down.
It has not passed a check since we started checking it on 11 Oct 2026. Latest error: initialize returned HTTP 400.
Latest check
- Last check
- 14 h ago (19 Oct 2026, 11:56 UTC)
- Response time
- Not measured
- Next check
- In about 15 h
- How often
- About every 29 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 29 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 |
|---|---|---|---|
| 19 Oct 2026, 11:56 UTC | initialize returned HTTP 400 | 400 | 270 ms |
| 18 Oct 2026, 11:24 UTC | initialize returned HTTP 400 | 400 | 133 ms |
| 17 Oct 2026, 08:50 UTC | initialize returned HTTP 400 | 400 | 49 ms |
| 16 Oct 2026, 03:56 UTC | initialize returned HTTP 400 | 400 | 79 ms |
| 14 Oct 2026, 23:20 UTC | initialize returned HTTP 400 | 400 | 207 ms |
| 13 Oct 2026, 18:04 UTC | initialize returned HTTP 400 | 400 | 1.5 s |
| 12 Oct 2026, 13:57 UTC | initialize returned HTTP 400 | 400 | 56 ms |
| 12 Oct 2026, 03:45 UTC | initialize returned HTTP 400 | 400 | 45 ms |
| 11 Oct 2026, 18:46 UTC | initialize returned HTTP 400 | 400 | 46 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 29 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.