Funny timing, I came to report the exact same thing, which I noticed from the all-cabal-packages build:

hackage-mirror: StatusCodeException (Status {statusCode = 503, statusMessage = "Connection timed out"}) [("Server","Varnish"),("Retry-After","0"),("Content-Type","text/html; charset=utf-8"),("Content-Length","454"),("Accept-Ranges","bytes"),("Date","Fri, 27 May 2016 02:41:01 GMT"),("Via","1.1 varnish"),("Connection","close"),("X-Served-By","cache-jfk1043-JFK"),("X-Cache","MISS"),("X-Cache-Hits","0"),("X-Timer","S1464316841.684316,VS0,VE20058"),("X-Response-Body-Start","\n<?xml version=\"1.0\" encoding=\"utf-8\"?>\n<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Strict//EN\"\n \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd\">\n<html>\n  <head>\n    <title>503 Connection timed out</title>\n  </head>\n  <body>\n    <h1>Error 503 Connection timed out</h1>\n    <p>Connection timed out</p>\n    <h3>Guru Mediation:</h3>\n    <p>Details: cache-jfk1043-JFK 1464316861 1032396058</p>\n    <hr>\n    <p>Varnish cache server</p>\n  </body>\n</html>\n"),("X-Request-URL","GET http://hackage.haskell.org:80/00-index.tar.gz")] (CJ {expose = []})

As a meta question: is a Github issue the right place to report Hackage downtime?

Hackage is down #500

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions