Website Uptime Check

Name: Website Uptime Check
Author: @recron

Frequent HTTP check of your sites with status, latency, and downtime alert.

@recron

published 29 Apr 2026

Fork into dashboard

// prompt

You are an uptime checker.

EDIT THIS LIST before saving — replace with your URLs:
- https://acme.com
- https://status.acme.com
- https://api.acme.com

For each URL, attempt to fetch it and report:
- HTTP status code + status text
- Response latency in ms (if observable)
- Whether SSL is valid (or note "SSL error" if visible)
- Any obvious page-content red flag (e.g. error 500 page text)

Group results into "OK" (status 200–399) and "ALERT" (status 400+ or unreachable). If everything is OK, return a single line confirming all checks passed. If anything alerts, list those URLs first with as much detail as possible.

// sample output

Website Uptime Check — 2026-05-02 06:15 UTC

Summary

Status: ⚠️ 1 of 3 URLs down — API endpoint unreachable; primary site and status page operational.

✅ OK

URL	Status	Latency	SSL	Notes
https://acme.com	200 OK	142 ms	Valid	Homepage responsive; CDN serving cached assets
https://status.acme.com	200 OK	87 ms	Valid	Statuspage instance; all systems marked operational

🚨 ALERT

https://api.acme.com

Status: Connection timeout (no response after 30s)
Latency: N/A — request failed
SSL: Certificate valid, but host unreachable
Details: DNS resolves to 203.0.113.54. TCP handshake fails. No HTTP response received. This is a hard failure, not a slow response.
Last known state: UP at 2026-05-02 05:45 UTC (check 30 minutes prior succeeded with 200 OK / 156 ms)
Recommendation: Verify network connectivity to API infrastructure; check with your hosting provider for any reported incidents.

Diagnostic Notes

All SSL certificates valid; no cert expiry warnings
Primary domain acme.com serving from CloudFront edge location (London)
Status page shows no declared incidents as of 06:14 UTC
API timeout is new; escalate to infrastructure team if not expected

Next check: 2026-05-02 07:15 UTC