Well, my best guess is that there was a window of time that one could choose US/Pacific-New as a timezone, and this user did. And now some library fails for users with that time zone.
UserOption.where(“timezone like ‘%Pacific-New%’”)
finds no other users with that timezone, so I guess it won’t happen again on this site.