Websites
Site Uptime Monitoring
Every site on KapsuleHost is checked automatically every 60 seconds, and the Uptime tab shows you the result: current status, uptime percentage, response times, and a full incident history. This guide covers how to read it and what to do when something goes wrong.
Where Uptime Lives in KPanel
Uptime belongs to a site, so you reach it from the site rather than from the main sidebar:
- Sign in to KPanel.
- Click Websites in the left sidebar, then click the site.
- In the site's own tab strip, open Performance, then Uptime.
The direct address is /websites/<site-id>/uptime.
There is no Uptime item in the main KPanel sidebar. That sidebar lists Dashboard, Websites, Orbit, Email, Domains, Apps, Cloud Servers, Dedicated Servers, Store, Billing, Migrations, and Settings. Uptime sits one level down, inside a specific site, under Performance.
What Is Being Checked
Your site is requested every 60 seconds from our monitoring node. Nothing needs to be enabled and there is no agent to install: checks begin automatically. A check is a real HTTP request, so it exercises DNS, TLS, the web server, and the application, in that order.
If you have just created a site and the page reads No uptime data yet, that is expected. The first checks land within a couple of minutes.
The Three Numbers at the Top
| Card | What it means |
|---|---|
| Current status | UP or DOWN, from the most recent check |
| Uptime | The percentage of successful checks in the window you selected |
| Avg response time | The mean response time in milliseconds across the window |
The window is set by the 24h, 7d, and 30d buttons above the cards, and every panel on the page follows it. Switching window changes the uptime percentage and the average, because it changes which checks are counted.
Average response time is worth watching over weeks rather than minutes. A single slow check is noise. A number that has doubled since last month is a signal, and usually means the site has grown past its current plan or picked up something expensive. Site Performance and APM is the next place to look.
The Response Time Chart
Below the cards is a bar per check, up to the last 60, oldest on the left. Bar height is response time relative to the slowest check in the window.
Colour carries the meaning:
- Blue is a successful check under three seconds.
- Amber is a successful check over three seconds. The site answered, but slowly.
- Red, drawn as a stub, is a failed check.
Hover any bar to see its response time, or the error message if it failed.
A wall of blue bars at a consistent height is a healthy site. A sawtooth pattern usually means something is running on a schedule and competing with your visitors: a cron job, a backup, or a plugin doing bulk work.
Incident History
An incident opens when checks start failing and closes when they succeed again. The table lists:
| Column | What it tells you |
|---|---|
| Started | When the first failed check landed, in your local time |
| Resolved | When checks recovered, or Ongoing if it is still failing |
| Duration | How long the incident lasted, in minutes |
| Reason | The failure message from the check |
If you have had no incidents, the table says so plainly.
The Reason column is where most of the diagnostic value is. Common ones and what they usually mean:
- Connection timed out. The server did not answer at all. Usually the host is down, overloaded, or a firewall rule is dropping traffic.
- Connection refused. The host answered but nothing was listening on the port. The web server is stopped.
- SSL or certificate errors. The certificate has expired, or does not cover the hostname being checked. Open the site's Security tab, which shows the certificate and its days remaining, and lets you renew it. See Site Security.
- HTTP 5xx. The application itself errored. Your logs and Site Performance and APM are the next stop.
- HTTP 4xx. Often a redirect or access rule catching the checker. If you have just added password protection to the whole site, that is why: see Password-Protecting a Site.
Multi-Region Status
Some sites also show a Multi-region status panel with a tile per probe region, each showing whether the region sees the site as up and how long it took to respond.
This is the panel that tells you whether a problem is yours or the internet's. If one region reports slow or down while the others are fine, the fault is usually in routing or at a network in between, not on your server. If every region agrees, the problem is at your end.
If the panel says results are still being provisioned, the monitor is being set up and per-region results appear within a few minutes. If the panel is absent entirely, multi-region probing is not active for that site and the single-node checks above are the source of truth.
Refreshing and Exporting
The refresh icon in the page header re-reads the data on demand. The page does not poll continuously, so refresh after you have made a change and want to see whether it took effect.
Troubleshooting
Uptime shows down but the site loads for me. Check the incident reason first. A 401 or 403 means an access rule is blocking the checker rather than the site being broken: password protection over the whole site, an IP block, or country filtering are the usual causes. See Site Security and Country Blocking for a Site.
Uptime percentage looks wrong for the window. The percentage is checks passed divided by checks made in that window. A short outage looks far worse over 24 hours than over 30 days. Compare like with like before concluding anything.
Response times jumped and nothing changed. Something did change, just not by you: a plugin update, a traffic increase, a database that has grown, or a scheduled job. Look at the chart for a pattern, then at Site Performance and APM for the slow endpoints.
Repeated short incidents at the same time each day. Look at your scheduled tasks. A heavy cron job that saturates the server will show as a cluster of failures at a fixed hour.
The site is genuinely down and you need to get back. If the last change you made broke it, restoring is faster than debugging. See Restoring From a Backup.
Related Pages
- Site Analytics for traffic volume and where visitors come from.
- Site Performance and APM for response time percentiles and slow queries.
- Site Security for certificates, malware scanning, and access rules.
- Taking a Backup before you change anything you might need to undo.
If a site keeps going down and the reason is not obvious, open a ticket from Support in KPanel or email support@kapsulehost.com with the site name and the timestamps from the incident table.