LexHost platform API — uptime monitor
An external health checker. It requests the platform's health endpoint every 1 minute and emails the on-call recipients when it stops answering, when it answers slower than 300 ms, and again when it recovers. A summary report goes out every 24 hours.
Platform: Operational
The platform answered the last health check.
Checked URLhttps://lexhost-dashboard-api.lexsoftapp.com/api/health
Last check0 s ago (2026-08-18 18:14:08 UTC)
Last responseHTTP 200 in 140 ms
Response budget300 ms — last answer was 160 ms under
Next checksoon (2026-08-18 18:15:08 UTC)
Checker: Running
checking on schedule
Running for0 s
Checks performed1 (0 failed)
Checking every1 minute
Alert recipients2 configured
Email deliveryverifying…
Memory (heap / rss)7.9 / 76.5 MB
Report window: 100% uptime
Everything since the last summary email — this is exactly what the next one will say. Sent every 24 h.
Window0 s — since 2026-08-18 18:14:08 UTC
Checks1 (1 ok, 0 failed)
Response timeavg 140 ms · min 140 ms · max 140 ms
Over budgetnone above 300 ms
Outagesnone
Next summary emailsoon (2026-08-19 18:14:08 UTC)
What this app is
- It runs on separate hosting, outside the platform — a monitor sharing a server with the thing it watches goes down with it.
- Every 1 minute it does one plain HTTP GET against the health endpoint. A response only counts as healthy if it is a 2xx and a real JSON health payload, so a maintenance or SPA fallback page cannot pass for a working API.
- The first failed check emails the recipients once, reminds them while the outage lasts, and emails again on recovery with the total downtime.
- A check that succeeds but takes longer than 300 ms (2 in a row) emails a slow response warning — degradation, not an outage — and one more when response times come back inside the budget.
- Every 24 hours it emails a summary: uptime, response times, failures and outages for the window shown above.
- Check now runs a check immediately instead of waiting for the next one — it joins the check already in flight rather than starting a second one.
- It stores nothing and changes nothing: no database, no access to the platform.
API
GET /healthIs this checker alive? 200 / 503 — for your own uptime toolingGET /statusFull JSON snapshot of everything on this pageGET /targetThe platform's state as a status code: 200 up, 503 downGET /checkRun a check right now and return the resultPOST /checkWhat the “Check now” button calls — public, throttled to one per 5 sGET /eventsThis page's live stream — pushed on every check