Every router serves the same routes, and a copy stops only once none sends it visitors

An App's or a balancer's change counts served only once every Runtime router serves it, so a deploy's old copies stop only after no router can still send them a visit. A router that has never had its route table yet answers router_not_ready (503, Retry-After: 1) instead of no_route. See Networking.