StatusPost status, live

StatusPost

statuspost.org · 11 checks shown of 12 watched · last read 54 seconds ago · page generated 12 Oct 2026, 21:51 UTC
all 8answering on the latest pass This page renders straight from the runner's readings; each row says how often it is read. Latest reading 12 Oct 2026, 21:51 UTC. Percentages below count the last 30 days. Speed, email records and browser protections are shown for information and advice; they never raise an alert.
October 2026 so far: home page up 100% of the time, 6 interruptions, longest 2 minutes.

Everything watched

Each row says how often it is read. The count beside every percentage is the number of readings behind it; a percentage without its denominator is not a fact.
Browser protections checked daily 47ms all good checked daily, last read 11 Oct 2026, 21:54 UTC
Can people find you 211ms all good 5996 of 5996 readings clean since 22 Sep 2026, 01:33 UTC (100%), counting the last 30 days, checked every 5 minutes
Certificate checked daily 35ms could not read 1 of 1 readings clean since 14 Sep 2026, 21:56 UTC (100%), counting the last 30 days The certificate for statuspost.org is issued and renewed automatically by the service that sits in front of your site, so it does not expire the way a hand-managed one can. We cannot read its date from where we stand, and there is nothing for you to do.
Connector 205ms all good 39245 of 39247 readings clean since 12 Sep 2026, 21:51 UTC (99.99%), counting the last 30 days, checked every minute
Email records checked daily 73ms all good checked daily, last read 11 Oct 2026, 21:54 UTC
Home page 48ms all good 39247 of 39247 readings clean since 12 Sep 2026, 21:51 UTC (100%), counting the last 30 days, checked every minute
Old name forwards 21ms all good 39247 of 39247 readings clean since 12 Sep 2026, 21:51 UTC (100%), counting the last 30 days, checked every minute
Plain http forwards 32ms all good 39247 of 39247 readings clean since 12 Sep 2026, 21:51 UTC (100%), counting the last 30 days, checked every minute
Speed around the world checked hourly 696ms for information checked hourly, last read 12 Oct 2026, 21:11 UTC Measured from 8 places. Fastest from Prague at 28 ms, slowest from Dallas at 196 ms. Normal for both, judged against each place's own last week.
Web address renewal checked daily 223ms all good 27 of 27 readings clean since 14 Sep 2026, 21:49 UTC (100%), counting the last 30 days
www variant 17ms all good 39181 of 39247 readings clean since 12 Sep 2026, 21:51 UTC (99.83%), counting the last 30 days, checked every minute

Reading log

Our own mistakes go here first. A status page that hides its own findings is not worth trusting with yours.
11 Oct 2026, 22:30 UTCwww variant stopped answering normally, and was back 1 minute later. What we saw: www variant: the page answered but no longer says "VERIFY-LOOP-not-on-page".
10 Oct 2026, 22:13 UTCwww variant stopped answering normally, and was back 1 minute later. What we saw: www variant: the page answered but no longer says "VERIFY-LOOP-not-on-page".
10 Oct 2026, 21:31 UTCwww variant stopped answering normally, and was back 2 minutes later. What we saw: www variant: the page answered but no longer says "VERIFY-LOOP-not-on-page".
9 Oct 2026, 20:31 UTCwww variant stopped answering normally, and was back 1 minute later. What we saw: www variant: the page answered but no longer says "VERIFY-LOOP-not-on-page".
8 Oct 2026, 19:40 UTCwww variant stopped answering normally, and was back 1 minute later. What we saw: www variant: the page answered but no longer says "VERIFY-LOOP-not-on-page".
8 Oct 2026, 15:24 UTCwww variant stopped answering normally, and was back 1 minute later. What we saw: www variant: the page answered but no longer says "VERIFY-LOOP-not-on-page".
26 Sep 2026, 16:50 UTCwww variant stopped answering normally, and was back 1 minute later. What we saw: www variant: the page answered but no longer says "VERIFY-LOOP-not-on-page".
25 Sep 2026, 16:36 UTCwww variant stopped answering normally, and was back 1 minute later. What we saw: www variant: the page answered but no longer says "VERIFY-LOOP-not-on-page".
24 Sep 2026, 16:21 UTCwww variant stopped answering normally, and was back 2 minutes later. What we saw: www variant: the page answered but no longer says "VERIFY-LOOP-not-on-page".
23 Sep 2026, 16:05 UTCwww variant stopped answering normally, and was back 2 minutes later. What we saw: www variant: the page answered but no longer says "VERIFY-LOOP-not-on-page".
23 Sep 2026, 15:41 UTCwww variant stopped answering normally, and was back 19 minutes later. What we saw: www variant: answered 301 where 200 is the healthy answer; the page answered but no longer says "VERIFY-LOOP-not-on-page".
22 Sep 2026, 17:19 UTCwww variant stopped answering normally, and was back 3 minutes later. What we saw: www variant: answered 301 where 200 is the healthy answer.
22 Sep 2026, 03:59 UTCwww variant stopped answering normally, and was back 1 minute later. What we saw: www variant: the page answered but no longer says "VERIFY-LOOP-not-on-page".
15 Sep 2026, 03:59 UTCwww variant stopped answering normally, and was back 2 minutes later. What we saw: www variant: the page answered but no longer says "RETEST-not-on-page-RETEST".
14 Sep 2026, 20:49 UTCwww variant stopped answering normally, and was back 1 minute later. What we saw: www variant: the page answered but no longer says "QQQ-still-not-on-the-page-QQQ".
14 Sep 2026, 20:43 UTCwww variant stopped answering normally, and was back 2 minutes later. What we saw: www variant: the page answered but no longer says "ZZZ-this-phrase-is-not-on-the-page-ZZZ".
24 Aug, eveningsteadywatch.org registered, homepage deployed, and the three founding member status pages went live on their own domains.
25 Aug, 1:30 AMA full audit found these pages serving none of the browser protections they grade other sites on, and the content policy silently blocking the page analytics. Both fixed and verified within the hour.
25 Aug, 2:05 AMA second look found plain http serving the page instead of forwarding to the secure address. The forward is now in place. Both findings are also in the RSS feed.
26 Aug, 11:15 AMRenamed from SteadyWatch to StatusPost, because the old name was repeatedly misheard as "study watch". The site moved to statuspost.org in a V2C-owned account; steadywatch.org now permanently redirects, so no link ever shared has broken.
26 Aug, 12:45 PMAn adversarial audit of our own work found this page publishing the previous domain's certificate and registration dates relabelled as statuspost.org's, an incomplete rename: it said the certificate renews 22 November when statuspost.org's real certificate renews 24 November, and dated the registration a day early. It also found two rows still checking the retired domain, the Slack address above misspelled, three feed entries claiming the wrong weekday, and our own email records missing the sender record and forgery policy we grade members on. Every number on this page has been re-read from the live domain, and the email records are now in place. This entry exists because the deal on this page is that mistakes get written down.
26 Aug, 4:45 PMA second audit round caught this page still advertising its feed under another member's name (a copy-paste from the V2C template), the rename entry in the feed stamped with Eastern wall-clock time labelled as UTC, and the old domain's redirects arriving without their security headers. On the member pages it caught wrong weekday labels, history strips lighting hours no reading touched, and feeds counting four browser protections where the pages say six. All corrected the same afternoon.
26 Aug, nightThe first production break test surfaced a limit worth writing down: this page is served by the same program that runs the checks, and Cloudflare refuses to let a program call its own address, so the two checks that watched this page and its feed could not survive the move to live data. They are retired with their history kept, and watching the watchman goes to an outside witness in a later milestone, which is where it honestly belonged all along.
26 Aug, eveningPer-minute watching began: this page now renders directly from the readings the runner writes, instead of from hand-measured numbers. The history above is preserved from the hand-built page it replaces.
Follow these updates:RSS feedadd it to Slack:/feed subscribe https://status.statuspost.org/feed.xml

Watching the watchman is not a gimmick; it is the deal. Every rule a member page follows, this page follows, including the embarrassing parts.