Uptime and certificate probes
The Lookout
The Lookout checks your sites from Zipper’s edge on a schedule you set: does the page answer, how fast, and is the HTTPS certificate still valid and far from expiring. Every probe records status, latency, and the certificate’s remaining life, so you get a history rather than a single ping. It warns you well before a certificate runs out and raises an alert the moment a site stops answering, with the outage length once it recovers. Results stay inside your workspace. This is reachability and certificate watching for your own sites — not a global synthetic-testing network and not a status page you have to build yourself. Included on every Zipper plan.
Cloudflare analogue: Uptime Monitoring
What it is
The Lookout checks your sites from Zipper’s edge on a schedule you set: does the page answer, how fast, and is the HTTPS certificate still valid and far from expiring. Every probe records status, latency, and the certificate’s remaining life, so you get a history rather than a single ping. It warns you well before a certificate runs out and raises an alert the moment a site stops answering, with the outage length once it recovers. Results stay inside your workspace. This is reachability and certificate watching for your own sites — not a global synthetic-testing network and not a status page you have to build yourself.
Closest analogue: Uptime Monitoring. SLA 99.95% · p99 120ms. Operators add targets and tune intervals. Alerts stay inside the owning workspace.
- ▸Scheduled probes from the edge
- ▸Certificate expiry warnings before it bites
- ▸Latency history per target
- ▸Down alerts with time-to-recover
How it works
Add a target — a hostname you want watched. The Lookout probes it from the edge on the interval you set and records status and latency.
Certificate checks run alongside: remaining validity is recorded, and a warning opens once expiry is closer than your warning threshold.
Two consecutive failed probes open an alert. The next successful probe closes it and records how long the site was down.
Alerts and history stay inside the owning workspace. This is reachability and certificate watching for your own sites.
Use cases
Concrete ways teams use this service on day one.
Know before a certificate expires
A cert silently expired over a weekend and the site showed a browser warning.
- Add each customer hostname as a target.
- Set the certificate warning to fourteen days.
- The Lookout warns while there is still time to renew — and alerts if the cert ever fails.
Catch a down site fast
A deploy took production down and nobody noticed for an hour.
- Set a probe interval of five minutes with a five-second timeout.
- Two failed probes open an alert.
- When the site recovers, the alert closes with the outage length recorded.
Set it up in the dashboard
Dashboard → Networking & Delivery → The Lookout → Targets: hostnames, interval, last status, certificate days left.
Checks: recent probe results with status and latency.
Alerts: open and resolved incidents with time-to-recover.
Configure: probe interval, timeout, certificate warning days, follow redirects, probe source.
API
Control-plane: GET|POST /api/v1/lookout/targets · GET /api/v1/lookout/checks · GET /api/v1/lookout/alerts. Send Authorization: Bearer tz_live_YOUR_TOKEN.
Creates count against the plan quota. A 402 plan_limit means you are at the cap — upgrade or delete an unused resource.
Add a target to watch
curl -sS -X POST https://tinyzipper.com/api/v1/lookout/targets \
-H "Authorization: Bearer tz_live_YOUR_TOKEN" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{"hostname":"shop.example.com","intervalSeconds":300}'Read recent checks
curl -sS https://tinyzipper.com/api/v1/lookout/checks?limit=20 \ -H "Authorization: Bearer tz_live_YOUR_TOKEN"
List the same resource in JavaScript
const res = await fetch("https://tinyzipper.com/api/v1/lookout/targets", {
method: "GET",
headers: {
Authorization: `Bearer ${process.env.ZIPPER_TOKEN}`,
"Content-Type": "application/json"
}
});
const json = await res.json();
if (!res.ok) throw new Error(json.error ?? res.statusText);
console.log(json);Tips
Warn well before expiry — set the certificate warning to fourteen days or more.
Shorter intervals catch outages faster but probe more often; five minutes suits most sites.
Two failures before an alert keeps a single slow response from paging anyone.
Not a global synthetic-testing network and not a hosted status page.
- ▸SOC 2
- ▸TLS 1.2+
- ▸Per-workspace targets
Runbook
Probes run from the edge on the interval you set. Warnings fire well before certificate expiry; an alert opens when two consecutive probes fail and closes when a probe succeeds again.
Next: The Coffer · All docs · Create a free account