Thanks folks. I can confirm that this affected everyone, and was a mistake on our end—sorry about that.
New server scheduling rules for our application briefly excluded all workers (servers that do a bulk of the work), so the apps couldn’t find a place to run. Hence “no healthy upstream” message.
We will put process changes in place to make sure this doesn’t happen again.