Is Postgresql Terminal History down?
Up
No, Postgresql Terminal History is up.
It passed its latest check 6 min ago in 396 ms, and every check since we started checking it on 19 Oct 2026.
Latest check
- Last check
- 6 min ago (7 Nov 2026, 15:49 UTC)
- Response time
- 396 ms (typical 377 ms)
- Next check
- In about 7 h
- How often
- About every 8 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 8 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 |
|---|---|---|---|
| 7 Nov 2026, 15:49 UTC | Passed | 402 | 396 ms |
| 7 Nov 2026, 08:58 UTC | Passed | 402 | 234 ms |
| 7 Nov 2026, 02:41 UTC | Passed | 402 | 412 ms |
| 6 Nov 2026, 21:39 UTC | Passed | 402 | 363 ms |
| 6 Nov 2026, 16:37 UTC | Passed | 402 | 442 ms |
| 6 Nov 2026, 10:43 UTC | Passed | 402 | 428 ms |
| 6 Nov 2026, 03:22 UTC | Passed | 402 | 377 ms |
| 5 Nov 2026, 17:50 UTC | Passed | 402 | 429 ms |
| 5 Nov 2026, 08:27 UTC | Passed | 402 | 400 ms |
| 4 Nov 2026, 23:10 UTC | Passed | 402 | 397 ms |
Price and payment address
- Price
- $0.003 per call on Base
- Pays to
- 0xaCe6…107E
| Date | Change |
|---|---|
| 21 Oct 2026 | Price changed from $0.0025 to $0.003 |
How we check
Up means the endpoint answered an unpaid test request with a valid x402 payment challenge. We never pay, so we can't see whether the paid response works.
Checks come from our server, about every 8 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. To see what an agent gets right now, check it yourself.