We have reverted the incorrect configuration and all services are operating again. We will be reviewing our runbooks to ensure we avoid these situations moving forward. Our apologies for the disruption and appreciation for your understanding.

While performing an optimization change, an engineer introduced an incorrect configuration which is rendering a 502 Bad Gateway for some redirection requests. We are reverting the change now and full service should be restored momentarily. The web console and API are not impacted.