When split DNS made a Firebase site appear offline
Resolver comparison exposed an over-broad private DNS redirect while the public deployment remained healthy.
Read the incident analysisThese articles preserve the reasoning behind diagnosis, maintenance, networking, recovery, and architecture decisions without exposing private infrastructure.
Resolver comparison exposed an over-broad private DNS redirect while the public deployment remained healthy.
Read the incident analysiskubectl drain is not enoughDrain success does not prove replacement placement, endpoint continuity, storage safety, quorum, or recovery.
Read the maintenance articleA completed backup job does not prove that data, identity, storage, and bootstrap dependencies restore in order.
Read the recovery articleFollowing each request-path handoff reveals where declared intent first diverges from observed behavior.
Read the networking articleA guided route through platform boundaries, service routing, recovery proof, and lifecycle decisions.
Open the evidence guide