The cynical possibility: perhaps due to being Firefox/Gecko-based, which usually entails being privacy-oriented
The statistical possibility: market share for Chromium browsers is so much bigger than Gecko's that developers didn't bother to implement compatibility after an update - or are experimenting to see if it's worthy it
The hopeful possibility: it was a glitch, the site or the browser having updated something that changed the user-agent or the expected one, and the site didn't know what to do with the current one.