7 posts.
The API runs on a GCP e2-micro because that's what Always Free covers - one instance, 30 GB of standard disk, an ephemeral IP. It turns out to be sitting exactly at that ceiling, which explains more of the outage two posts back than any single bug did.
app and api had no DNS records for most of their existence, so there was nothing to monitor - which meant status.pacestreak.com kept quietly not telling the whole story even after both went live. Fixed, plus a lesson in why a 200 from the app proves nothing about the API behind it.
A redirect was reported broken seconds after pushing. It simply was not live yet. How we check deploys now.
A proxied DNS record with nothing behind it returns 522, which looks like a broken product. So records wait for deployments.
Without a 404.html, Cloudflare Pages answers every unknown path with the home page and a 200. Here is what that broke.
The complete technology list behind PaceStreak — domain, sites, monitoring, backend, tooling — with the reasoning, the rejected alternatives, and the constraints each choice created for the next one.
Domains, monitoring, a status page and a landing site — and the four things that silently broke while doing it.
PaceStreak is a habit and streak tracker for training and everything else worth doing regularly.