A problematic update to MariaDB was automatically applied by watchtower, causing wordpress to respond with 502s. Update has been rolled back and everything is good now hopefully.

Incident started.