How this site is run
A static page on a CDN almost never goes down, so an uptime number for it proves nothing. This site has one small dynamic path, so there is something real to operate.
How it works:
- A scheduled job checks this site's latest commit and build status every 10 minutes and stores a snapshot.
- Every page reads that snapshot into the footer. If the read fails, the page still serves without it.
- An external probe checks every 5 minutes that the snapshot is fresh. Two service level objectives sit on those results.
- Two small games add real traffic: Pulse run reports what the browser experiences, and Ludo times every roll and move on the server, with its own objectives on the dashboard.
- I break it on purpose, restore it, and write down what I learned. Postmortem: game day 1 (1 October 2026).
- When something breaks that I didn't plan, it gets the same treatment. Postmortem: a load test used up the day's database writes (2 October 2026).
- Everything that can expire and take the site down is listed on the dashboard, with its date read every day from the service that issued it. Reminders reach me by email at 90, 60 and 30 days, and close themselves once fixed. Dependencies we couldn't see (4 October 2026).
- If the site's own records can't be written, nothing pages anyone and nothing is lost: every reading is also logged, and missed readings are rebuilt from the logs on the next healthy run.
Status: the heartbeat and the external probe have been running since 30 September 2026. The first 30-day SLO numbers come after that window closes.
See the live reliability dashboard →
How it's built
Astro static pages served by one Cloudflare Worker, which also runs the scheduled job, the probe endpoint, an SLI ledger in a Durable Object, and the dashboard. Incidents go to a separate engine that runs on GitHub Actions, with GitHub Issues as the human gate. Both are public, with every decision written down.
- This site's code (Astro, TypeScript, Cloudflare Workers)
- Decision records, each with the option it rejected
- Game day 1, the raw record behind the postmortem
- The 2 October incident, the raw record behind its postmortem
- The incident engine's code (Python, GitHub Actions)