All systems are operational

Past Incidents

Monday 7th January 2019

Wrong cache data being returned from the API

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.

Sunday 6th January 2019

Unreliable authentication process

The authentication in the new API is very unreliable, and a lot of users are forced to re-authenticate on a daily basis. We understand that this is annoying, and we are truly sorry for all the problems you're experiencing now.

We are working as hard as we can to minimize the effect of this, but we depend on to fix the problem on their end.

Thursday 3rd January 2019

Degraded performance due to limitations in the new API

Limitations in the new API have severely degraded the performance, and we are having problems keeping caches and logs updated. We are truly sorry for the inconvenience caused by this, and we are doing as much as we can to make it better.