Check the status page

As I've covered somewhat extensively in prior writing (see A month of OpEx quick wins and Self-hosting our GitHub Action runners), this year has been marked by a careful and deliberate shrinking of our stack, button down, with the goals of, in order, one, reduce long-term maintenance burden. Two, reduce operational expenses. Almost without us really meaning to, this has materialized indirectly as adopting a lot of Cloudflare stuff, which makes sense given that Cloudflare's primary positioning for almost all of their non-DNS infrastructure is a more cost-effective alternative to entrenched legacy alternatives like AWS. These savings have been real, and minus some hiccups here or there, the migrations have been extremely painless. However, we do find ourselves with the new problem of having accidentally introduced what at times feels like an SPOF. When Cloudflare's DNS infrastructure goes down, it impacts basically the entire world, and therefore I don't mind that much that it impacts…