Is PulseGate down?
Failing our checks
Yes, PulseGate is failing our checks.
Our latest check was refused with HTTP 429 (rate limited), so we can't tell whether it works for you. It has failed every check since 17 Oct 2026, 03:02 UTC (34 h 59 min, 3 checks). It last passed on 16 Oct 2026, 16:15 UTC.
Latest check
- Last check
- 14 h ago (17 Oct 2026, 23:58 UTC)
- Response time
- Not measured (typical 293 ms)
- Next check
- In about 9 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, 34 h 59 min of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 17 Oct 2026, 03:02 UTC | Ongoing, 34 h 59 min so far | 3 | initialize returned HTTP 429 |
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 |
|---|---|---|---|
| 17 Oct 2026, 23:58 UTC | initialize returned HTTP 429 | 429 | 193 ms |
| 17 Oct 2026, 13:22 UTC | initialize returned HTTP 429 | 429 | 185 ms |
| 17 Oct 2026, 03:02 UTC | initialize returned HTTP 429 | 429 | 236 ms |
| 16 Oct 2026, 16:15 UTC | Passed | 200 | 215 ms |
| 16 Oct 2026, 06:21 UTC | Passed | 200 | 250 ms |
| 15 Oct 2026, 20:52 UTC | Passed | 200 | 289 ms |
| 15 Oct 2026, 11:00 UTC | Passed | 200 | 287 ms |
| 15 Oct 2026, 01:39 UTC | Passed | 200 | 332 ms |
| 14 Oct 2026, 15:55 UTC | Passed | 200 | 382 ms |
| 14 Oct 2026, 06:16 UTC | Passed | 200 | 450 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 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.