FWIW, I see no downtime in my logs. On Tuesday, January 13, 2015, Asumu Takikawa <<a href="mailto:asumu@ccs.neu.edu">asumu@ccs.neu.edu</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all, I've been trying to update my Racket checkout and it's getting stuck on the `raco pkg update -a` phase of the Makefile. It's failed something like 9 times in a row for me with errors of the following form: tcp-connect: connection failed detail: host not found address: <a href="http://pkgs.racket-lang.org" target="_blank">pkgs.racket-lang.org</a> port number: 80 step: 1 system error: Name or service not known; errno=-2 context...: I've had errors like this before when trying to build Docker images for Racket. I would start out with a minimal Racket and then try to install all of the main distribution packages via the network. It would usually fail with a tcp-connect error like this. In the Docker case, I gave up and used a git checkout of all the packages and installed them locally. Can we improve reliability of the package server for this use case or alternatively set up a meta-repo of all the main distribution packages (that can be checked out at once) to avoid this kind of thing? Cheers, Asumu ____________________ Racket Users list: <a href="http://lists.racket-lang.org/users" target="_blank">http://lists.racket-lang.org/users</a> </blockquote> -- Jay McCarthy <a href="http://jeapostrophe.github.io" target="_blank">http://jeapostrophe.github.io</a> "Wherefore, be not weary in well-doing, for ye are laying the foundation of a great work. And out of small things proceedeth that which is great." - D&C 64:33