Uptime & SSL Monitoring

XAXA checks every site once a minute and shows the result on the Sites list (green, red or grey dot) and on each site's Overview:

• Uptime for the last 24 hours and 7 days,
• average response time and a chart of the latest checks,
• days until the certificate expires (shown in red below 14 days).

How checks work

Each site is requested over HTTPS on the server itself (127.0.0.1, with the site's domain as host name). A response below 500 counts as up; 5xx answers and timeouts (10 seconds) count as down. Two failed checks in a row are needed before the site is marked down, so one slow or failed request sends no alert. This measures whether nginx and your app answer on this server — it does not depend on DNS, so it also works before the domain points here.

When a site goes down or comes back, an event (site.down / site.up) is written to Admin → Events. Check history is kept for 7 days.

A site in maintenance mode is not checked: its dot turns amber and it sends no down alert (see Site settings → Maintenance mode).

Traffic and server errors

The Traffic card on Overview reads the site's nginx access log every 5 minutes: requests, the share of server errors (5xx), average response time and the slowest 5% for the last 24 hours, with a chart of requests per hour. The uptime check only requests the home page; the traffic count also catches a checkout or API route that fails while the home page works.

When at least 20 requests in 5 minutes arrive and 10% or more of them end with a 5xx error, admins get an alert (at most once an hour per site). Traffic history is kept for 30 days. Counting starts with the first 5-minute round after the update; when the log is rotated at night, the last lines of the old file are not counted.

Disk usage

Overview → Details shows how much the site's home folder uses (files, releases, mail; backups are stored elsewhere), measured every 3 hours. Set a Disk alert under Settings → General to get an alert when the site grows past it; files are not blocked.