Website Uptime Monitoring: How to Know the Moment Your Site Goes Down

Most website owners discover downtime the worst possible way: a customer emails to say the site is broken, or they happen to open their own URL and find a server error staring back at them.

By that point, the damage is already done. Visitors have bounced. Sales have been lost. If you run any kind of SaaS, e-commerce store, or client-facing service, every minute of undetected downtime has a measurable cost.

Website uptime monitoring is the solution. It checks your site at regular intervals (every minute, in GhostlyX's case) and alerts you the moment something goes wrong, so you find out before anyone else does.

What website uptime monitoring actually is

Website uptime monitoring is an automated process that sends HTTP requests to your site on a defined schedule and records whether it responds correctly. If the site fails to respond, responds too slowly, or returns an error status code, the monitoring service flags the check as failed and notifies you immediately.

The core metric it tracks is uptime percentage: the proportion of time your site is available and responding correctly. An uptime of 99.9% sounds impressive, but it still means around 8.7 hours of downtime per year. For a busy e-commerce store or a SaaS product with paying customers, that is a significant exposure.

Uptime monitoring is distinct from performance monitoring (which tracks page load speeds for real users) and error tracking (which catches application exceptions). Uptime monitoring answers one specific question: is the site up or down right now?

Why downtime is more expensive than most people realise

Downtime costs are easy to underestimate because many of them are invisible.

Direct revenue loss is the obvious one. If your checkout page is returning a 503 error, every visitor who attempts to purchase during that window is lost. For a site converting at 2% with average order values of $80, even 30 minutes of downtime during peak traffic can mean thousands of dollars in missed revenue.

SEO impact is less obvious but real. Google crawls websites continuously. If Googlebot hits your site during a period of downtime, it records an error. Repeated crawl errors can affect how frequently your site is crawled and, over longer periods, can influence rankings. A site that is frequently unavailable signals instability to search engines.

Customer trust is the hardest to quantify and the hardest to recover. A visitor who lands on a broken site does not wait around. They leave and, in many cases, find a competitor. Research by Gartner found that the average cost of IT downtime is around $5,600 per minute for enterprises, and even for smaller businesses, the reputational damage from downtime often outlasts the technical incident itself.

Email deliverability can also be affected. If your site is down and your DNS or mail server is implicated in the cause, transactional emails (password resets, order confirmations, notifications) may queue or fail during the outage window.

How uptime monitoring works

The mechanics are straightforward. A monitoring service sends an HTTP GET request (or HEAD request) to your URL at a set interval. Your web server processes that request and returns a response with an HTTP status code.

Status codes in the 2xx range (200 OK, 201 Created) indicate a healthy response. Status codes in the 4xx range indicate client errors (404 Not Found, 403 Forbidden). Status codes in the 5xx range indicate server errors (500 Internal Server Error, 503 Service Unavailable). Most monitors treat anything outside the 2xx range as a failed check.

The monitor records:

• Response time: how long the server took to respond, measured in milliseconds
• Status code: the HTTP code returned
• Result: up or down, based on your configured threshold

When a check fails, the monitor typically waits for a confirmation check before triggering an alert, to avoid false positives from transient network hiccups. Once a failure is confirmed, the alert goes out immediately.

GhostlyX runs these checks from multiple locations every sixty seconds. That one-minute check interval means you will know about downtime within one to two minutes of it starting, not an hour later when a customer calls.

What the GhostlyX uptime monitor tracks

GhostlyX uptime monitoring is built into the same dashboard where you track your website analytics. You do not need a separate tool or account. Add a URL to monitor, and GhostlyX starts checking it every minute.

For each monitor, you get:

Current status. A clear up or down indicator showing whether your site is responding correctly right now.

Response time. How quickly your server is responding to each check, displayed as a timeline. Spikes in response time are often an early warning sign of an overloaded server before a full outage occurs.

30-day uptime percentage. Your availability record over the past month, expressed as a percentage. This gives you an honest view of your site's reliability over time, not just whether it happens to be up at the moment you check.

ECG view. A visual timeline of every check result, shown as a series of green and red markers that let you see at a glance when outages occurred, how long they lasted, and how frequently they happen.

Email alerts. When a monitor detects a failure, GhostlyX sends an email alert immediately. When the site recovers, you get a recovery notification so you know the incident is resolved.

Response time as an early warning system

Pure up/down monitoring catches outages, but response time data catches problems before they become outages.

A server that normally responds in 80 milliseconds but suddenly takes 4 seconds to respond is not technically down, but something is wrong. It might be a database query that has started full-scanning a table, a memory leak that is slowing request processing, or a traffic spike that is pushing server resources to their limits.

Watching response time trends lets you act before visitors start experiencing slow page loads and before the server tips into a full outage. The GhostlyX ECG view shows response times alongside up/down results, so you can see the relationship between performance degradation and availability incidents.

Setting up uptime monitoring on GhostlyX

Adding a monitor takes less than a minute.

1. Open your GhostlyX dashboard and navigate to the Uptime section.
2. Click Add monitor and enter the URL you want to check. This is typically your homepage, but you can monitor any URL including your checkout page, your API health endpoint, or a specific landing page.
3. Save the monitor. GhostlyX will run its first check within sixty seconds and start building your uptime history immediately.

You can add multiple monitors for different URLs on the same site or across different sites. If you run several properties, you can see the status of all of them in one place without logging into separate accounts.

Uptime monitoring is available on the Business and Scale plans.

What to monitor beyond your homepage

Your homepage is the obvious starting point, but it is rarely the most important URL to monitor from a business perspective.

Your checkout or payment page. This is where revenue is generated. A broken checkout is a direct line to lost sales. Monitoring this URL separately means you will know immediately if the payment flow is broken even if the rest of the site appears fine.

Your API health endpoint. If your product has an API that customers integrate with, a dedicated health check endpoint (typically /health or /status) gives your monitor a reliable target that reflects the full stack, including database connections, cache availability, and application logic, rather than just whether the web server is responding.

Your login page. If customers cannot log in, they cannot use your product. Authentication failures often surface at the login endpoint before they affect other parts of the application.

Your most-trafficked landing page. If a high-traffic paid advertising campaign is sending visitors to a specific landing page, that URL deserves its own monitor. A broken landing page during an active campaign is an expensive problem that is easy to miss if you are only monitoring your homepage.

Uptime monitoring and your analytics data

There is a useful relationship between uptime data and your website analytics that most monitoring tools ignore, because they are separate products.

In GhostlyX, both live in the same dashboard. When you see an unexpected drop in pageviews in your analytics, you can immediately check your uptime history for the same time period to see if an outage explains it. When you spot a spike in response time on your uptime ECG, you can check whether it coincides with a bounce rate increase in your analytics.

This correlation is not possible when your analytics and uptime monitoring live in separate tools. Having both in one place makes incident analysis faster and more complete.

The difference between uptime monitoring and status pages

A status page is a public-facing page (often at status.yourdomain.com) that communicates your site's operational status to customers. Some businesses build these to keep customers informed during incidents.

Uptime monitoring is the internal, automated system that detects those incidents in the first place. The two are related but distinct. You need uptime monitoring regardless of whether you have a status page. A status page is only useful if you have a reliable way to detect that there is something to communicate.

A note on uptime percentage targets

The industry standard targets for uptime are often expressed as "nines":

• 99% uptime: 87.6 hours of downtime per year
• 99.9% uptime: 8.76 hours of downtime per year
• 99.95% uptime: 4.38 hours of downtime per year
• 99.99% uptime: 52.6 minutes of downtime per year

Most shared hosting plans advertise 99.9% uptime. Most managed cloud infrastructure targets 99.95% or better. The gap between 99.9% and 99.99% is nearly 8 hours of downtime per year, which is meaningful for any site doing real business.

Your GhostlyX uptime dashboard shows your actual 30-day uptime percentage, so you can compare your real-world availability against whatever your hosting provider promises in their SLA.

Stop finding out from your customers

Downtime is inevitable. Every website, every server, every infrastructure component will experience a failure at some point. The question is not whether your site will go down. The real question is how quickly you will know about it and how long it will take to resolve.

Without uptime monitoring, the answer to the first question is "when a customer tells you." With GhostlyX uptime monitoring, the answer is "within one to two minutes, automatically, before anyone else knows."

That shift, from reactive to proactive, is what separates a minor incident from a significant one.

Frequently asked questions

Q: What is website uptime monitoring? A: Website uptime monitoring is an automated service that sends regular HTTP requests to your website and checks whether it responds correctly. If the site fails to respond, returns an error code, or takes too long to load, the monitor triggers an alert. GhostlyX checks every sixty seconds, so you know about downtime within one to two minutes of it starting.

Q: How often does GhostlyX check my site? A: GhostlyX runs uptime checks every sixty seconds. This means the maximum time between a site going down and you receiving an alert is approximately one to two minutes, accounting for the confirmation check that prevents false positives from transient network issues.

Q: What HTTP status codes are treated as downtime? A: GhostlyX treats any response outside the 2xx range as a failed check. This includes 4xx client errors (such as 404 Not Found) and 5xx server errors (such as 500 Internal Server Error and 503 Service Unavailable). Timeouts (where the server does not respond within the allowed window) are also treated as failures.

Q: Can I monitor multiple URLs? A: Yes. You can add as many monitors as you need, covering different URLs across one or multiple sites. This lets you monitor your homepage, checkout page, API endpoint, and login page independently, each with its own uptime history and alert settings.

Q: What does the ECG view show? A: The ECG view is a visual timeline of every uptime check result. Green markers indicate successful checks; red markers indicate failures. The timeline lets you see at a glance when outages occurred, how long they lasted, and whether they were isolated incidents or part of a pattern. Response times are overlaid on the same timeline.

Q: Which GhostlyX plans include uptime monitoring? A: Uptime monitoring is available on the Business plan ($29/month) and the Scale plan ($69/month). Both plans include multiple monitors with one-minute check intervals, response time tracking, ECG history, and email alerts for downtime and recovery events.

Q: How is uptime monitoring different from performance monitoring? A: Uptime monitoring answers one question: is the site available right now? It checks whether your server responds at all, and how quickly. Performance monitoring measures the full page load experience for real visitors, including time to first byte, render times, and resource loading. GhostlyX uptime monitoring focuses on availability and server response time, not full page load performance.