@mediatemple thanks :) Looks like it was a temporary problem - I'm guessing a network problem over here. All resolving problems have gone :)