It was a bug in the Geocaching.com LIVE api actually. We notified Geocaching HQ yesterday and the bug was fixed quite promptly after that.
As soon as it came to our knowledge we added an alert on the Discover-page that warned our users about it. We only needed the warning there for 2-3 hours if I recall correctly.
In short, the issue is resolved, it was affecting all API partners.