Is PageWatch - page-to-data extraction and change monitoring down?
Down
Yes, PageWatch - page-to-data extraction and change monitoring is down.
It has failed every check since 18 Oct 2026, 18:29 UTC (15 h 8 min, 2 checks). Latest error: Connection failed (ENOTFOUND). It last passed on 18 Oct 2026, 08:00 UTC.
Latest check
- Last check
- 6 h ago (19 Oct 2026, 03:23 UTC)
- Response time
- Not measured (typical 163 ms)
- Next check
- In about 3 h
- How often
- About every 10 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 10 hours over the last 7 days.
Outages in the last 30 days
1 outage, 15 h 8 min of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 18 Oct 2026, 18:29 UTC | Ongoing, 15 h 8 min so far | 2 | Connection failed (ENOTFOUND) |
Times are when our checks ran, about every 10 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 19 Oct 2026, 03:23 UTC | Connection failed (ENOTFOUND) | - | - |
| 18 Oct 2026, 18:29 UTC | Connection failed (ENOTFOUND) | - | - |
| 18 Oct 2026, 08:00 UTC | Passed | 200 | 163 ms |
| 17 Oct 2026, 21:24 UTC | Passed | 200 | 192 ms |
| 17 Oct 2026, 10:59 UTC | Passed | 200 | 180 ms |
| 17 Oct 2026, 00:43 UTC | Passed | 200 | 151 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 10 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.