Is Traffalyzer down?
Down
Yes, Traffalyzer is down.
It has not passed a check since we started checking it on 11 Oct 2026. Latest error: initialize returned HTTP 500.
Latest check
- Last check
- 13 h ago (19 Oct 2026, 06:35 UTC)
- Response time
- Not measured
- Next check
- In about 14 h
- How often
- About every 28 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 28 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, 06:35 UTC | initialize returned HTTP 500 | 500 | 356 ms |
| 18 Oct 2026, 06:22 UTC | initialize returned HTTP 500 | 500 | 827 ms |
| 17 Oct 2026, 00:26 UTC | initialize returned HTTP 500 | 500 | 317 ms |
| 15 Oct 2026, 20:38 UTC | initialize returned HTTP 500 | 500 | 1.3 s |
| 14 Oct 2026, 16:17 UTC | initialize returned HTTP 500 | 500 | 1.1 s |
| 13 Oct 2026, 12:35 UTC | initialize returned HTTP 500 | 500 | 933 ms |
| 12 Oct 2026, 10:55 UTC | initialize returned HTTP 500 | 500 | 873 ms |
| 12 Oct 2026, 02:33 UTC | initialize returned HTTP 500 | 500 | 1.0 s |
| 11 Oct 2026, 17:39 UTC | initialize returned HTTP 500 | 500 | 942 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 28 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.