How this site is built.
Small on purpose. A status page should answer at a glance, load instantly, work everywhere, and never be the thing that's down.
Answers first
Each page answers one question, at the top, in a sentence: "All quiet in the woods." Then rows you can scan, then the detail, each one step further away. What needs attention comes first, and every link lands on the problem.
Honest numbers
- Rounded for reading, never in our favour. "200 ms", not 199.4; uptime rounds down, so 100% means no failed check at all. The exact value is a hover or a table away.
- The picture never misleads. Charts start at zero, a gap in the data is drawn as a gap, and the headline number is the typical one, not the latest noisy check.
- Words say what was measured, with its period, and early days say so ("since Nov 11") instead of claiming 90 clean ones.
Calm by default
- Colour means status and nothing else: green, amber and red for up, trouble and down, one blue for links, and a symbol beside every colour.
- Type does the hierarchy: your system's own font, no web font, and numbers that line up in their columns and don't jiggle as they update.
- Flat, with boxes only where you can act, and frosted glass only for controls, never for content.
- Motion explains a change and is never decoration, and it's off when your system asks for less.
Built light
- Plain HTML from the server. Every page works with JavaScript off: forms post, links go, sections open. One small script adds live updates, local times and the interactive charts.
- One stylesheet, no framework, and no chart library. Charts, share cards and badges are drawn on the server.
- The server does the thinking, the browser only draws: time windows, labels, rounding and time zones are decided in one place, so every page agrees.
- Live without reloading: every 30 seconds a status page fetches itself and swaps only what changed, and the tab's title and icon change with it, so a pinned tab works as an alarm.
Fast, and up when we're not
The same page for everyone, kept for a minute by our server and by Cloudflare in front of it, so no visit waits for the database. If our server goes down, Cloudflare keeps serving the last copy for a day: the status page outlives what it reports on. The stylesheet and script are on their way before the page is, and a link you hover is fetched ahead.
For everyone
A skip link, a visible focus ring, real buttons and links, charts you can step through with the keyboard and read as a table, underlined links in running text, contrast checked by a test in light and dark, both following your system, and pages that fit a phone without sideways scrolling. Agents get the same facts in forms they read: ready for agents →
In character
The woods are in the moments that carry no data: headlines, empty states, the 404 ("Lost in the woods"), share cards at dusk under the aurora, and a fallen tree when a site went down. The data itself stays plain.
The share cards and badges are inspired by Mind Polling, which tracks AI model answers over time: a card answers for a period, says its date, and gets a new address when its numbers change, so an old link never shows a stale answer.
What we leave out
Frameworks, modals, toasts, web fonts, tabs that split evidence apart, and columns hidden to look simpler. Restraint is most of what makes a page feel modern.
Behind it
TypeScript on Node, with Postgres, hosted on Railway behind Cloudflare. Checks are plain requests from the outside, from both US coasts, plus a real browser once a day and AI agents that try a site's tasks. It watches itself too, from a monitor that runs apart from these pages. The code is private for now; it's written by Geeks in the Woods, with AI helping on the code, and we score it with our own open-source agent and search readiness audit.
Last updated .