18th July 2016

Swift

We've identified and solved an issue with Swift. We've moved the main proxy to a stronger server and are keeping an eye on it.