Is Memory down?
Up
No, Memory is up again.
It passed its latest check 3 h ago in 1.2 s. Before that it failed our checks for 3 days 4 h, from 15 Oct 2026, 01:00 UTC.
Latest check
- Last check
- 3 h ago (18 Oct 2026, 15:19 UTC)
- Response time
- 1.2 s (typical 1.4 s)
- Next check
- In about 7 h
- How often
- About every 9 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 9 hours over the last 7 days.
Outages in the last 30 days
1 outage, 3 days 4 h of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 15 Oct 2026, 01:00 UTC | 3 days 4 h | 4 | initialize returned HTTP 530 |
Times are when our checks ran, about every 9 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 18 Oct 2026, 15:19 UTC | Passed | 200 | 1.2 s |
| 18 Oct 2026, 05:01 UTC | Passed | 200 | 1.2 s |
| 17 Oct 2026, 00:35 UTC | initialize returned HTTP 503 | 503 | 1.1 s |
| 15 Oct 2026, 19:53 UTC | initialize returned HTTP 530 | 530 | 202 ms |
| 15 Oct 2026, 10:21 UTC | initialize returned HTTP 530 | 530 | 338 ms |
| 15 Oct 2026, 01:00 UTC | initialize returned HTTP 530 | 530 | 145 ms |
| 14 Oct 2026, 15:45 UTC | Passed | 200 | 1.3 s |
| 14 Oct 2026, 06:08 UTC | Passed | 200 | 1.8 s |
| 13 Oct 2026, 21:16 UTC | Passed | 200 | 2.2 s |
| 13 Oct 2026, 12:10 UTC | Passed | 200 | 1.6 s |
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 9 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.