It's been a bit, and has anyone else noticed...


Just curious.
Yeah, seems to be down at the moment. Perhaps maintenance.
It seems to be working ok for me right now for both HTTP and HTTPS, although seems to be non-compliant with RFC 7234 § and §, by serving an aged response to a Cache-Control: max-age=0, no-cache request.
Working fine for me from NYC.

I'd also say, IMHO, the subject line should have been more descriptive. If in a hurry that's the type of subject line I'd ignore. A subject of down? would have gotten far more people checking, and let people know there might be a problem.