I also confirm that it now seems to be fixed after several hours of problems. Good call by RiderOfGiraffes on the cookie. At first I thought it might've been a

I also confirm that it now seems to be fixed after several hours of problems. Good call by RiderOfGiraffes on the cookie. At first I thought it might've been a DNS caching issue with Firefox, but after Wiresharking the connection it was clear that it was asking the right server, but the response was timing out (30s for Firefox). This didn't happen from other browsers or by going to 174.132.225.106 directly. In retrospect, these were all situations where the cookie would not be included...