What the monitor did about the canary

The canary is a page that breaks itself on a published schedule. It is watched by the same pipeline as a paying customer's pages, and everything below is what that pipeline actually recorded. Nothing here is illustrative.

right now: healthy

Next change 2026-09-19 18:00 UTC, to noindex. Schedule: UTC hour mod 4: 0 and 1 healthy, 2 noindex, 3 error (503). One full cycle every 4 hours.

Coverage

Checks attempted
1341
Pages actually loaded
1341
Could not vouch for
0
Watching since
2026-08-27 18:26:56
Last good look
2026-09-19 15:54:44
Checked every
30 minutes

The cadence is the one this account is entitled to, the same as a paying Starter account, so the delay between a scheduled break above and its incident below is the delay you would get. It is not tuned to make this page look fast.

Detection latency

Incidents measured
200
Change → detected, median
15m
Change → detected, p90
28m
Change → confirmed, median
16m
Change → confirmed, p90
29m
Change → first alert delivered, median
16m
Change → first alert delivered, p90
29m

Measured on a 30-minute cadence; a paid Agency site is checked every 15 minutes, so its numbers are shorter; we publish the slower one. "Change" is the scheduled break time from the published 4-hour rotation, so it is known to the minute without trusting our own logs. Unconfirmed incidents are excluded from the confirmed and delivered figures rather than counted as fast.

Incidents

Detected (UTC)WhatSeverityStateConfirmedResolvedDelivered to
2026-09-19 15:23:44status became errorcriticalconfirmed15:24:45email 15:24:47
2026-09-19 14:21:44noindex appearedcriticalresolved14:22:4515:23:44email:resolved 15:23:46
email 14:22:47
2026-09-19 11:15:44status became errorcriticalresolved11:16:4412:17:44email:resolved 12:17:46
email 11:16:46
2026-09-19 10:13:44noindex appearedcriticalresolved10:14:4511:15:44email:resolved 11:15:45
email 10:14:47
2026-09-19 07:07:44status became errorcriticalresolved07:08:4508:09:44email:resolved 08:09:46
email 07:08:46
2026-09-19 06:05:44noindex appearedcriticalresolved06:06:4507:07:44email:resolved 07:07:45
email 06:06:47
2026-09-19 03:30:44status became errorcriticalresolved03:31:4504:01:44email:resolved 04:01:46
email 03:31:46
2026-09-19 02:28:44noindex appearedcriticalresolved02:29:4503:30:44email:resolved 03:30:46
email 02:29:46
2026-09-18 23:22:44status became errorcriticalresolved23:23:4500:24:44email:resolved 00:24:46
email 23:23:47
2026-09-18 22:20:44noindex appearedcriticalresolved22:21:4523:22:44email:resolved 23:22:45
email 22:21:47
2026-09-18 19:14:44status became errorcriticalresolved19:15:4520:16:44email:resolved 20:16:46
email 19:15:47
2026-09-18 18:12:44noindex appearedcriticalresolved18:13:4419:14:44email:resolved 19:14:45
email 18:13:46
2026-09-18 15:06:44status became errorcriticalresolved15:07:4516:08:44email:resolved 16:08:46
email 15:07:47
2026-09-18 14:04:44noindex appearedcriticalresolved14:05:4415:06:44email:resolved 15:06:45
email 14:05:47
2026-09-18 11:29:44status became errorcriticalresolved11:30:4512:00:44email:resolved 12:00:46
email 11:30:47
2026-09-18 10:27:44noindex appearedcriticalresolved10:28:4511:29:44email:resolved 11:29:46
email 10:28:47
2026-09-18 07:21:44status became errorcriticalresolved07:22:4508:23:44email:resolved 08:23:46
email 07:22:46
2026-09-18 06:19:44noindex appearedcriticalresolved06:20:4507:21:44email:resolved 07:21:46
email 06:20:46
2026-09-18 03:13:44status became errorcriticalresolved03:14:4504:15:44email:resolved 04:15:46
email 03:14:47
2026-09-18 02:11:44noindex appearedcriticalresolved02:12:4503:13:44email:resolved 03:13:46
email 02:12:47

A change never confirms on the run that created it. Suppressed rows are ones the flap pass decided were noise, and they are shown rather than hidden.

Every check, newest first

When (UTC)Statusmeta robotsX-Robots-TagTookResult
2026-09-19 15:54:4450389msloaded
2026-09-19 15:24:455031msloaded
2026-09-19 15:23:4450356msloaded
2026-09-19 14:52:44200noindex54msloaded
2026-09-19 14:22:45200noindex1msloaded
2026-09-19 14:21:44200noindex62msloaded
2026-09-19 13:50:4420052msloaded
2026-09-19 13:19:4420025msloaded
2026-09-19 12:48:4420087msloaded
2026-09-19 12:17:4420092msloaded
2026-09-19 11:46:4450366msloaded
2026-09-19 11:16:44503<1msloaded
2026-09-19 11:15:4450361msloaded
2026-09-19 10:44:44200noindex51msloaded
2026-09-19 10:14:45200noindex1msloaded
2026-09-19 10:13:44200noindex60msloaded
2026-09-19 09:42:4420058msloaded
2026-09-19 09:11:4420095msloaded
2026-09-19 08:40:4420084msloaded
2026-09-19 08:09:4420020msloaded
2026-09-19 07:38:4450368msloaded
2026-09-19 07:08:45503<1msloaded
2026-09-19 07:07:4450325msloaded
2026-09-19 06:36:44200noindex60msloaded
2026-09-19 06:06:45200noindex1msloaded
2026-09-19 06:05:44200noindex29msloaded
2026-09-19 05:34:4420064msloaded
2026-09-19 05:03:4420056msloaded
2026-09-19 04:32:4420055msloaded
2026-09-19 04:01:4420051msloaded
2026-09-19 03:31:455031msloaded
2026-09-19 03:30:4450348msloaded
2026-09-19 02:59:44200noindex87msloaded
2026-09-19 02:29:45200noindex1msloaded
2026-09-19 02:28:44200noindex44msloaded
2026-09-19 01:57:4420060msloaded
2026-09-19 01:26:4420012msloaded
2026-09-19 00:55:4420058msloaded
2026-09-19 00:24:4420051msloaded
2026-09-18 23:53:4450350msloaded

Why this exists

This product has no customers yet, so it has no testimonials, and the people it is built for would not believe one anyway. A URL you can fetch against a schedule published in advance is the only evidence we can honestly offer.

If the log disagrees with the schedule, the monitor is wrong and you should not buy it. That is the bet.

Rendered 2026-09-19 16:25:42 UTC. stillindexed.com