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: noindex

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

Coverage

Checks attempted
4220
Pages actually loaded
4219
Could not vouch for
1
Watching since
2026-08-27 18:26:56
Last good look
2026-11-07 22:23:46
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
17m
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-11-07 22:22:45noindex appearedcriticalconfirmed22:23:46—email 22:23:48
2026-11-07 19:16:46status became errorcriticalresolved19:17:4720:18:46email:resolved 20:18:47
email 19:17:48
2026-11-07 18:14:46noindex appearedcriticalresolved18:15:4719:16:46email:resolved 19:16:47
email 18:15:48
2026-11-07 15:08:45status became errorcriticalresolved15:09:4616:10:45email:resolved 16:10:46
email 15:09:48
2026-11-07 14:06:45noindex appearedcriticalresolved14:07:4615:08:45email:resolved 15:08:47
email 14:07:48
2026-11-07 11:00:45status became errorcriticalresolved11:01:4612:02:45email:resolved 12:02:47
email 11:01:48
2026-11-07 10:29:45noindex appearedcriticalresolved10:30:4511:00:45email:resolved 11:00:47
email 10:30:47
2026-11-07 07:23:45status became errorcriticalresolved07:24:4508:25:45email:resolved 08:25:47
email 07:24:47
2026-11-07 06:21:45noindex appearedcriticalresolved06:22:4507:23:45email:resolved 07:23:47
email 06:22:47
2026-11-07 03:15:46status became errorcriticalresolved03:16:4604:17:46email:resolved 04:17:47
email 03:16:48
2026-11-07 02:13:46noindex appearedcriticalresolved02:14:4703:15:46email:resolved 03:15:47
email 02:14:48
2026-11-06 23:07:45status became errorcriticalresolved23:08:4600:09:46email:resolved 00:09:47
email 23:08:47
2026-11-06 22:05:45noindex appearedcriticalresolved22:06:4623:07:45email:resolved 23:07:46
email 22:06:47
2026-11-06 19:30:45status became errorcriticalresolved19:31:4520:01:45email:resolved 20:01:47
email 19:31:47
2026-11-06 18:28:45noindex appearedcriticalresolved18:29:4619:30:45email:resolved 19:30:47
email 18:29:48
2026-11-06 15:22:45status became errorcriticalresolved15:23:4516:24:45email:resolved 16:24:47
email 15:23:47
2026-11-06 14:20:45noindex appearedcriticalresolved14:21:4615:22:45email:resolved 15:22:47
email 14:21:48
2026-11-06 11:15:24status became errorcriticalresolved11:16:2512:17:24email:resolved 12:17:25
email 11:16:26
2026-11-06 10:13:24noindex appearedcriticalresolved10:14:2511:15:24email:resolved 11:15:25
email 10:14:26
2026-11-06 07:07:24status became errorcriticalresolved07:08:2508:09:24email:resolved 08:09:25
email 07:08:26

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-11-07 22:23:46200noindex—1msloaded
2026-11-07 22:22:45200noindex—11msloaded
2026-11-07 21:51:45200——47msloaded
2026-11-07 21:20:45200——8msloaded
2026-11-07 20:49:46200——39msloaded
2026-11-07 20:18:46200——43msloaded
2026-11-07 19:47:46503——61msloaded
2026-11-07 19:17:47503——<1msloaded
2026-11-07 19:16:46503——54msloaded
2026-11-07 18:45:46200noindex—41msloaded
2026-11-07 18:15:47200noindex—1msloaded
2026-11-07 18:14:46200noindex—40msloaded
2026-11-07 17:43:46200——39msloaded
2026-11-07 17:12:45200——51msloaded
2026-11-07 16:41:45200——47msloaded
2026-11-07 16:10:45200——53msloaded
2026-11-07 15:39:45503——9msloaded
2026-11-07 15:09:46503——1msloaded
2026-11-07 15:08:45503——21msloaded
2026-11-07 14:37:45200noindex—92msloaded
2026-11-07 14:07:46200noindex—<1msloaded
2026-11-07 14:06:45200noindex—83msloaded
2026-11-07 13:35:45200——53msloaded
2026-11-07 13:04:45200——11msloaded
2026-11-07 12:33:45200——14msloaded
2026-11-07 12:02:45200——10msloaded
2026-11-07 11:31:45503——11msloaded
2026-11-07 11:01:46503——<1msloaded
2026-11-07 11:00:45503——14msloaded
2026-11-07 10:30:45200noindex—<1msloaded
2026-11-07 10:29:45200noindex—9msloaded
2026-11-07 09:58:45200——38msloaded
2026-11-07 09:27:45200——23msloaded
2026-11-07 08:56:45200——41msloaded
2026-11-07 08:25:45200——19msloaded
2026-11-07 07:54:45503——40msloaded
2026-11-07 07:24:45503——1msloaded
2026-11-07 07:23:45503——11msloaded
2026-11-07 06:52:45200noindex—21msloaded
2026-11-07 06:22:45200noindex—<1msloaded

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-11-07 22:36:14 UTC. stillindexed.com