World: r3wp

This is annoying. I do not know why, but in Chrome, I am de facto 
unable to log in to CC. Do you have any idea, what may be the culprit?

Works for me using Chrome

I usually have to wait, until Chrome tells the page is currently 
unavailable

and a different browser is okay?

In IE it seems to work in a snappy way

I don't have issues in Chrome.

It works from here with Chrome too. It might be an internal Chrome 
prefetching or DNS caching issue.

internal Chrome prefetching

 - looks more like postfetching taking into account how sluggish it 
 is

Way back when I reported that I was getting an error with the head.rsp 
file. Well, after being on a fix it binge, I decided to take a look 
at what was going on. It turns out that there were multiple instances 
of Cheyenne running. I am not referring to the multiple instances 
on normally sees but from another build altogether. I still don't 
know where that is getting launched from (I checked the startup and 
all the services etc in msconfig) but by kludging it and renaming 
the build I didn't want, it fixed the issue.

The domain issue.cc has expired since yesterday and is no more reachable. 
It seems I've missed something when transferring it to another registrar, 
so it might be unavailable for one or two more days.

Domain issue.cc is up again.

Perfect, doc.

Domain issue.cc is down again, it seems that the configuration wasn't 
completed after the transfert. I've fixed the config options so it 
should be back online in 24 hours max.