During routine background maintenance, a configuration overlap briefly allowed some public requests to be directed to a process that was not intended to serve website traffic. This caused a small number of temporary (502) errors. We corrected the separation between maintenance work and public request handling, verified the updated routing, and are monitoring the next maintenance run.
