Uptime, SSL and the public status page

Exception tracking tells you the app is failing; uptime monitoring tells you it isn't answering at all. Quiet Guard probes a URL you choose, alerts on the transition, keeps a latency history, watches the TLS certificate, and can share it all on a public status page.

The active probe

Set a check URL in the project's Settings (Uptime monitoring section). Every five minutes, Quiet Guard sends a GET request:

• Any status below 400 counts as up (redirects included), with the response time recorded as latency.
• A 4xx/5xx, a timeout (10 s) or a connection error counts as down.
• The URL must be public: private and internal addresses are rejected by the same anti-SSRF guard that protects webhooks.

Prefer a lightweight endpoint like Laravel's /up health route over a heavy homepage: you are measuring availability, not rendering time.

Down / recovered alerts

Alerts fire on transitions, not on every failing check: one alert when the site goes down, one when it comes back. Subscribe channels to the uptime.down and uptime.recovered events on the project's Alerts tab (see Alerting). Alert-storm protection applies.

Because probes run every five minutes, an outage shorter than the gap between two checks can go unnoticed, the probe is a smoke detector, not a packet analyzer.

Latency history

Every probe stores a sample. The project overview renders a 24-hour response-time chart (30-minute buckets, averages of successful checks; outage windows appear as gaps, never as fake zeros). Samples are kept seven days, independently of your plan's event retention.

TLS certificate expiry

For https check URLs, a daily job reads the certificate directly off the socket, it works even when the chain is broken, and stores the expiry date, shown on the project overview.

You are warned twice per certificate: once when it crosses 14 days to expiry, once more at 3 days (ssl_expiring event, same channels). A renewed certificate resets the cycle. An already expired certificate needs no special alert: the five-minute probe verifies peers, so the site simply goes down and alerts through that path.

The public status page

Flip Public status page in the project's Settings and share the generated link, an unguessable token is the whole URL. The page shows:

• the current state and, when down, since when;
• 7-day availability: overall and as one bar per day;
• current and 24-hour average latency;
• the TLS certificate's validity date;
• the last five outage windows.

Nothing sensitive is exposed: visitors see the project's display name and probe results, never the probed URL, tokens or any application data. Disabling the page keeps the token, so re-enabling restores the same address, links you shared stay valid.

Embeddable badge

The same token also serves a flat SVG badge at /status/{token}/badge.svg: green with the 7-day availability when the site is up, red "down" during an outage, gray "n/a" before the first check. Drop it in a README:

![uptime](https://your-monitor.example/status/{token}/badge.svg)

The exact snippet, with your real token, is shown under the status-page toggle in the project's Settings. The badge refreshes with the same one-minute cache as the page.