Is pg.ddx.io: the PostgreSQL community's memory down?
Up
No, pg.ddx.io: the PostgreSQL community's memory is up.
It passed its latest check 10 h ago in 205 ms, and every check since we started checking it on 23 Oct 2026.
Latest check
- Last check
- 10 h ago (28 Oct 2026, 18:37 UTC)
- Response time
- 205 ms (typical 183 ms)
- Next check
- In about 2 h
- How often
- About every 12 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 12 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 |
|---|---|---|---|
| 28 Oct 2026, 18:37 UTC | Passed | 200 | 205 ms |
| 28 Oct 2026, 05:12 UTC | Passed | 200 | 254 ms |
| 27 Oct 2026, 16:14 UTC | Passed | 200 | 216 ms |
| 27 Oct 2026, 03:18 UTC | Passed | 200 | 177 ms |
| 26 Oct 2026, 14:17 UTC | Passed | 200 | 150 ms |
| 26 Oct 2026, 02:28 UTC | Passed | 200 | 142 ms |
| 25 Oct 2026, 14:11 UTC | Passed | 200 | 211 ms |
| 25 Oct 2026, 02:34 UTC | Passed | 200 | 182 ms |
| 24 Oct 2026, 15:54 UTC | Passed | 200 | 185 ms |
| 24 Oct 2026, 04:32 UTC | Passed | 200 | 178 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 12 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.