We have resolved this issue. It was caused by an update which was put in to production at the time of incident which has now been reverted. Thank you for your patience.

Our API is currently unavailable, which has caused a knock-on to cause an "An error has been encountered" error for users who sign-in. We expect this to be fixed in the next minutes.