So, basically, this broke at some point a couple months ago and has been using its cached values ever since. Victim of an unreported API update?