Answers from the incident where every dashboard looked politely wrong.
The release-api deployment had already been marked complete when the invoice page began returning 503s. The new container was serving traffic, the PostgreSQL migration had committed, and the feature flag was on. A NetworkPolicy added in another repository prevented the new pod from reaching tax-rate-cache.
The application team saw errors, the database team saw a clean migration, and Platform saw green nodes. By the time we put all three facts in one incident channel, 63 deployment messages had buried the one that mattered.
“Is This Actually A DevOps Failure Or Just One Bad Deploy?”
It was a DevOps failure because four teams completed valid local work and nobody owned the release handoff between them.
