From Outage to Alert in Seconds: How ismysiteup Works Under the Hood

What Happens in Those Few Seconds

When your site goes down and you get an alert moments later, a lot happens behind the scenes. Understanding it helps you trust the tool — and configure it better. Here's the journey from outage to alert.

Step 1: The Check

A dedicated background worker continuously polls your monitored URLs on the schedule you set — anywhere from every 30 seconds to every 12 hours, depending on your plan. Each check is a real HTTP request from our servers to your URL, with a timeout you control. The worker records:

• The HTTP status code returned
• The response time
• Whether the request timed out or failed to connect

Step 2: The Evaluation

The result is compared against what you expect. A check is considered a failure if:

• The status code doesn't match your expected code (more on that in API monitoring beyond status 200)
• The request times out
• The connection is refused or DNS fails
• (For HTTPS) the SSL certificate is invalid

If everything checks out, nothing happens — we don't spam you with "still up" messages. We only store and act on problems.

Step 3: The Alert

The instant a check fails, the first alert goes out to your connected channels — email, WhatsApp, Telegram, or Slack (here's how to pick the right one). It doesn't wait for the next check cycle. After that, follow-up alerts are batched intelligently, so a site that keeps flapping up and down can't spam you.

Step 4: The Record

Failures are written to your incident history so you can look back and spot patterns — a host that flakes every night, a page that slows down under load, a cert that nearly expired. You won't wade through thousands of "still up" entries — the history focuses on what went wrong and when, while recent response times are kept so you can spot slowdowns.

Step 5: The Recovery

When a previously-down site comes back up, the monitor notices, updates its status, and sends you a recovery alert — so you also know when the problem is over, not just when it started.

Why This Design Matters

• Independent worker — monitoring runs separately from the website you see, so it keeps watching even under load.
• Short intervals — detection speed is limited mainly by how often you check, which you control.
• Smart batching — you get signal, not noise.

Try It Yourself

You can see a slice of this live right now: the free instant checker on the homepage resolves DNS, finds the server IP and location, measures response time, and inspects the SSL certificate for any URL — no account needed. Then sign up free to put your sites under continuous watch.

Related reading: How to Choose a Check Interval · What Is Uptime Monitoring?