Wrong cache data being returned from the API Monday 7th January 2019 21:30:06

The API is currently returning garbled cache data, and we've had to turn off the connection. This means that new caches won't be fetched, and we can't update data for existing caches until we turn the connection back on. Unfortunately, some of the existing caches are already updated with wrong data, and this has triggered some change notification emails.

We are sorry for the inconvenience, we are doing all we can to minimize the impact. But other than that, there's really not much we can do on our side.