Green Health Checks Hid a Homepage Stuck on Four-Day-Old Content
For four days, a company's homepage displayed the news as of Monday even though new entries were being published and the API and deployment reported healthy. Stale static files placed in front of dynamic routes were served to visitors instead of the current data, so every monitor, which checked layers beneath the problem, stayed green. A fix was delayed for three days because its prerequisite, migrating ten legacy entries into the entry store, had no owner. When the shadowing files were finally removed, the feed URL returned a 404 because a rewrite pointed to an intermediate endpoint and the platform does not chain rewrites. The author concludes that public checks should verify content freshness as a visitor sees it rather than relying on status codes.
