Product

Uptime monitoring

HTTP checks from EU locations — with confirmation logic that filters transient failures before anyone gets paged.

EU flag Hosted in the EU
GDPR-friendly by design
No US cloud in the data path

How it works

  • Watchcat sends HTTP checks at defined intervals
  • Responses are evaluated (status, timing)
  • Failures trigger alerts after confirmation
  • Recovery is detected automatically

How it works in detail

Scheduled checks

  • Checks run at the interval you choose, such as every 1 minute or 3 minutes.
  • Each check stores the observed status and response time.

Failure detection

  • The first failed check is recorded, but the monitor is not marked down immediately.
  • Watchcat waits for a confirmation period before changing the monitor to DOWN.
  • Short transient failures can clear before an incident is opened, which helps reduce noise.

Recovery and incidents

  • An incident is created when the monitor transitions to DOWN.
  • Recovery requires stable successful checks, not just one lucky response.
  • The incident is resolved when the service has recovered.

Monitoring locations

Uptime checks run from configured European locations.

  • Germany flag Germany
  • Finland flag Finland

Why it matters

  • Checks run from EU infrastructure — no monitoring data routed through US providers
  • Confirmation logic waits for failure to stabilise — fewer false pages
  • Response time tracked per check — spot degradation before it becomes an outage

Typical use cases

  • A checkout API — you need to know within minutes if it stops responding
  • A customer-facing app on a VPS you manage alone, with no ops team behind it
  • An internal tool the team relies on but no one outside will ever report as down

Start monitoring for free.

5 monitors free · no credit card required

Start free