Yesterday, a faulty patch to ATS was deployed, but it was rejected by reload_config() because of the syntax error.
This morning, an unrelated but correct change to backend.yaml was deployed; that change involved a restart of ATS, including the bad config from yesterday.
That resulted in requests to /api/rest_v1 being sent to their fallback route, which is RESTBase. RESTBase didn't know what to do with them, so returned errors. Those errors resulted in a page (from ATS for elevated backend errors).
Reverting the faulty ATS change and restarting ATS resolved the incident.