Screenshots

Not screenshots — the actual interface, rendered on this page with sample data. What you see below is the same code that runs when you sign in, so it cannot quietly fall out of date.

The monitor view

shop.example.comHealthy
Uptime · 24h
95.00%
38 of 40 checks
Average response
70 ms
successful checks
Last check
76 ms
1 min ago
Checked from
ARN
Stockholm, Sweden

Uptime history

2026-09-21 11:03:05 UTC — Healthy — HTTP 200 — 67 ms2026-09-21 11:04:05 UTC — Healthy — HTTP 200 — 74 ms2026-09-21 11:05:05 UTC — Healthy — HTTP 200 — 80 ms2026-09-21 11:06:05 UTC — Healthy — HTTP 200 — 85 ms2026-09-21 11:07:05 UTC — Healthy — HTTP 200 — 88 ms2026-09-21 11:08:05 UTC — Healthy — HTTP 200 — 85 ms2026-09-21 11:09:05 UTC — Healthy — HTTP 200 — 85 ms2026-09-21 11:10:05 UTC — Healthy — HTTP 200 — 84 ms2026-09-21 11:11:05 UTC — Healthy — HTTP 200 — 81 ms2026-09-21 11:12:05 UTC — Healthy — HTTP 200 — 77 ms2026-09-21 11:13:05 UTC — Healthy — HTTP 200 — 67 ms2026-09-21 11:14:05 UTC — Healthy — HTTP 200 — 63 ms2026-09-21 11:15:05 UTC — Healthy — HTTP 200 — 59 ms2026-09-21 11:16:05 UTC — Healthy — HTTP 200 — 56 ms2026-09-21 11:17:05 UTC — Healthy — HTTP 200 — 54 ms2026-09-21 11:18:05 UTC — Healthy — HTTP 200 — 49 ms2026-09-21 11:19:05 UTC — Healthy — HTTP 200 — 51 ms2026-09-21 11:20:05 UTC — Healthy — HTTP 200 — 54 ms2026-09-21 11:21:05 UTC — Healthy — HTTP 200 — 59 ms2026-09-21 11:22:05 UTC — Healthy — HTTP 200 — 65 ms2026-09-21 11:23:05 UTC — Healthy — HTTP 200 — 66 ms2026-09-21 11:24:05 UTC — Healthy — HTTP 200 — 73 ms2026-09-21 11:25:05 UTC — Down — HTTP 503 — 31 ms2026-09-21 11:26:05 UTC — Down — HTTP 503 — 31 ms2026-09-21 11:27:05 UTC — Healthy — HTTP 200 — 88 ms2026-09-21 11:28:05 UTC — Healthy — HTTP 200 — 85 ms2026-09-21 11:29:05 UTC — Healthy — HTTP 200 — 85 ms2026-09-21 11:30:05 UTC — Healthy — HTTP 200 — 84 ms2026-09-21 11:31:05 UTC — Healthy — HTTP 200 — 93 ms2026-09-21 11:32:05 UTC — Healthy — HTTP 200 — 89 ms2026-09-21 11:33:05 UTC — Healthy — HTTP 200 — 80 ms2026-09-21 11:34:05 UTC — Healthy — HTTP 200 — 75 ms2026-09-21 11:35:05 UTC — Healthy — HTTP 200 — 71 ms2026-09-21 11:36:05 UTC — Healthy — HTTP 200 — 68 ms2026-09-21 11:37:05 UTC — Healthy — HTTP 200 — 66 ms2026-09-21 11:38:05 UTC — Healthy — HTTP 200 — 61 ms2026-09-21 11:39:05 UTC — Healthy — HTTP 200 — 63 ms2026-09-21 11:40:05 UTC — Healthy — HTTP 200 — 66 ms2026-09-21 11:41:05 UTC — Healthy — HTTP 200 — 71 ms2026-09-21 11:42:05 UTC — Healthy — HTTP 200 — 76 ms
HealthyDownOldest → newest

Response time, split into phases

050 ms100 ms2026-09-21 11:03:05 UTC — HTTP 200 — 64 ms to first byte, 3 ms download2026-09-21 11:04:05 UTC — HTTP 200 — 70 ms to first byte, 4 ms download2026-09-21 11:05:05 UTC — HTTP 200 — 75 ms to first byte, 5 ms download2026-09-21 11:06:05 UTC — HTTP 200 — 79 ms to first byte, 6 ms download2026-09-21 11:07:05 UTC — HTTP 200 — 81 ms to first byte, 7 ms download2026-09-21 11:08:05 UTC — HTTP 200 — 82 ms to first byte, 3 ms download2026-09-21 11:09:05 UTC — HTTP 200 — 81 ms to first byte, 4 ms download2026-09-21 11:10:05 UTC — HTTP 200 — 79 ms to first byte, 5 ms download2026-09-21 11:11:05 UTC — HTTP 200 — 75 ms to first byte, 6 ms download2026-09-21 11:12:05 UTC — HTTP 200 — 70 ms to first byte, 7 ms download2026-09-21 11:13:05 UTC — HTTP 200 — 64 ms to first byte, 3 ms download2026-09-21 11:14:05 UTC — HTTP 200 — 59 ms to first byte, 4 ms download2026-09-21 11:15:05 UTC — HTTP 200 — 54 ms to first byte, 5 ms download2026-09-21 11:16:05 UTC — HTTP 200 — 50 ms to first byte, 6 ms download2026-09-21 11:17:05 UTC — HTTP 200 — 47 ms to first byte, 7 ms download2026-09-21 11:18:05 UTC — HTTP 200 — 46 ms to first byte, 3 ms download2026-09-21 11:19:05 UTC — HTTP 200 — 47 ms to first byte, 4 ms download2026-09-21 11:20:05 UTC — HTTP 200 — 49 ms to first byte, 5 ms download2026-09-21 11:21:05 UTC — HTTP 200 — 53 ms to first byte, 6 ms download2026-09-21 11:22:05 UTC — HTTP 200 — 58 ms to first byte, 7 ms download2026-09-21 11:23:05 UTC — HTTP 200 — 63 ms to first byte, 3 ms download2026-09-21 11:24:05 UTC — HTTP 200 — 69 ms to first byte, 4 ms download2026-09-21 11:25:05 UTC — HTTP 503 — 31 ms to first byte2026-09-21 11:26:05 UTC — HTTP 503 — 31 ms to first byte2026-09-21 11:27:05 UTC — HTTP 200 — 81 ms to first byte, 7 ms download2026-09-21 11:28:05 UTC — HTTP 200 — 82 ms to first byte, 3 ms download2026-09-21 11:29:05 UTC — HTTP 200 — 81 ms to first byte, 4 ms download2026-09-21 11:30:05 UTC — HTTP 200 — 79 ms to first byte, 5 ms download2026-09-21 11:31:05 UTC — HTTP 200 — 87 ms to first byte, 6 ms download2026-09-21 11:32:05 UTC — HTTP 200 — 82 ms to first byte, 7 ms download2026-09-21 11:33:05 UTC — HTTP 200 — 77 ms to first byte, 3 ms download2026-09-21 11:34:05 UTC — HTTP 200 — 71 ms to first byte, 4 ms download2026-09-21 11:35:05 UTC — HTTP 200 — 66 ms to first byte, 5 ms download2026-09-21 11:36:05 UTC — HTTP 200 — 62 ms to first byte, 6 ms download2026-09-21 11:37:05 UTC — HTTP 200 — 59 ms to first byte, 7 ms download2026-09-21 11:38:05 UTC — HTTP 200 — 58 ms to first byte, 3 ms download2026-09-21 11:39:05 UTC — HTTP 200 — 59 ms to first byte, 4 ms download2026-09-21 11:40:05 UTC — HTTP 200 — 61 ms to first byte, 5 ms download2026-09-21 11:41:05 UTC — HTTP 200 — 65 ms to first byte, 6 ms download2026-09-21 11:42:05 UTC — HTTP 200 — 69 ms to first byte, 7 ms download76 ms2026-09-21 11:032026-09-21 11:42
Time to first byteDownload
View as table (8 most recent)
Time (UTC)StatusCodeTTFBDownloadTotal
2026-09-21 11:42:05 UTCHealthy20069 ms7 ms76 ms
2026-09-21 11:41:05 UTCHealthy20065 ms6 ms71 ms
2026-09-21 11:40:05 UTCHealthy20061 ms5 ms66 ms
2026-09-21 11:39:05 UTCHealthy20059 ms4 ms63 ms
2026-09-21 11:38:05 UTCHealthy20058 ms3 ms61 ms
2026-09-21 11:37:05 UTCHealthy20059 ms7 ms66 ms
2026-09-21 11:36:05 UTCHealthy20062 ms6 ms68 ms
2026-09-21 11:35:05 UTCHealthy20066 ms5 ms71 ms

The latest check, in absolute numbers

69 msto first byte7 msdownloading76 mstotal

Time to first byte includes the DNS lookup, the connection and the TLS handshake. They cannot be measured separately.

Status at a glance

Every state carries an icon and a word, never a colour on its own — the same badge appears in the list, on the monitor page and in the alert.

HealthyDownPendingPaused

What a failure looks like

api.example.com/healthDown
Last check failed: Blocked by the target's bot protection (Cloudflare); Unexpected status code: 403

The status code alone would not have explained this. Recognising the challenge page in the body is what turns "403" into something you can act on — and the response body is kept for failed checks so you can read exactly what came back.

This is the whole product

There is no second, better dashboard behind the sign-up. Three monitors are free forever.

Get started — free