It was a bad roll out of DB migrations + code at the same time. DB migrations happen when meta is built. So it was a case of old (pre-migration) code running against new DB schema. The issue fixed itself once everything was deployed to all servers across all tiers (meta & sites).
Rest assured, The Wheel of Blame has been spun.