Website monitoring

What it is

vibePulse sends HTTP requests to a URL on a schedule and checks status codes and latency — similar to what a user’s browser sees: “does this open from the outside?”

When to use it

1. 1

   Landing or main service page

   Catch 502/404 from DNS, SSL, or CDN misconfigurations before users report it.

2. 2

   Public API health endpoint

   Verify an open endpoint like `/health` or `/api/status` returns 200 without auth.

3. 3

   Payment or webhook receiver URL

   Ensure the public path that receives Stripe or Polar webhooks stays up after deploys.

4. 4

   Staging vs production

   Register prod and staging URLs separately so you know which environment failed.

When is it marked down

On each scheduled check, vibePulse requests your URL. If the first try succeeds, that is the whole check. If it fails, we wait 5 seconds and try up to two more times. We mark Down and send alerts only when all three attempts fail. Any success in between counts as OK for that cycle.

• Recovery: one successful check on the next cycle closes the incident automatically.
• Hover the status badge on the dashboard or monitor detail for the same rules in a tooltip.
• Brief deploy glitches often recover on the 2nd or 3rd attempt, which reduces false alarms.

Limitations

• Internal URLs that require login or API keys are hard to check as-is.
• URL checks cannot tell if a process is stuck, leaking memory, or deadlocked.
• Pure background scripts with no public URL are better suited to heartbeats.