Clearly its a network connectivity issue on your side... don't know whats causing it though. For the record, here is a tracerout. Anything past hop #7 is google infrastructure.
$ traceroute trac.sagemath.org traceroute to trac.sagemath.org (104.197.143.230), 30 hops max, 60 byte packets 1 router (192.168.1.1) 0.273 ms 0.386 ms 0.404 ms 2 * * * 3 83-169-179-182-isp.superkabel.de (83.169.179.182) 15.555 ms 15.715 ms 15.617 ms 4 ip5886c231.static.kabel-deutschland.de (88.134.194.49) 15.155 ms 14.198 ms 15.155 ms 5 * * * 6 * * * 7 * 72.14.212.140 (72.14.212.140) 21.606 ms 25.633 ms 8 108.170.241.194 (108.170.241.194) 26.669 ms 108.170.241.227 (108.170.241.227) 26.375 ms 108.170.241.226 (108.170.241.226) 26.232 ms 9 209.85.240.231 (209.85.240.231) 26.544 ms 209.85.241.31 (209.85.241.31) 30.056 ms 66.249.94.167 (66.249.94.167) 30.378 ms 10 216.239.48.159 (216.239.48.159) 36.351 ms 35.306 ms 216.239.46.115 (216.239.46.115) 36.376 ms 11 108.170.236.33 (108.170.236.33) 109.591 ms 72.14.236.9 (72.14.236.9) 109.098 ms 72.14.235.115 (72.14.235.115) 103.074 ms 12 108.170.237.42 (108.170.237.42) 119.108 ms 122.625 ms 123.293 ms 13 209.85.143.103 (209.85.143.103) 127.391 ms 209.85.247.5 (209.85.247.5) 126.919 ms 72.14.234.9 (72.14.234.9) 134.815 ms 14 72.14.238.41 (72.14.238.41) 132.563 ms 216.239.59.143 (216.239.59.143) 130.232 ms 72.14.239.219 (72.14.239.219) 131.486 ms 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * On Tuesday, December 20, 2016 at 11:23:32 PM UTC+1, Maxie Schmidt wrote: > > I'm still having trouble accessing the trac server by web and over ssh. > Here is the output when I run "ssh -vvv g...@trac.sagemath.org > <javascript:> info": > > OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g 1 Mar 2016 > debug1: Reading configuration data /etc/ssh/ssh_config > debug1: /etc/ssh/ssh_config line 19: Applying options for * > debug2: resolving "trac.sagemath.org" port 22 > debug2: ssh_connect_direct: needpriv 0 > debug1: Connecting to trac.sagemath.org [104.197.143.230] port 22. > debug1: connect to address 104.197.143.230 port 22: Connection timed out > ssh: connect to host trac.sagemath.org port 22: Connection timed out > > Any suggestions about what is going on? Is anyone else still having > problems accessing the trac server? > > > On Sunday, December 18, 2016 at 5:47:04 PM UTC-6, Volker Braun wrote: >> >> works for me, too >> >> On Sunday, December 18, 2016 at 11:55:31 PM UTC+1, William wrote: >>> >>> The trac website is up for me and my uptimerobot monitor hasn't shown >>> any downtime. >>> >>> On Sun, Dec 18, 2016 at 2:17 PM Maxie Schmidt <max...@gmail.com> wrote: >>> >>>> The trac server ssh and website are still down when I check them as >>>> well. >>>> >>>> >>>> On Sunday, December 18, 2016 at 8:06:38 AM UTC-6, Ralf Stephan wrote: >>>>> >>>>> Site unreachable. Maybe that causes the SSH key problem in another >>>>> thread as well. >>>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> >>>> >>>> You received this message because you are subscribed to the Google >>>> Groups "sage-devel" group. >>>> >>>> >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to sage-devel+...@googlegroups.com. >>>> >>>> >>>> To post to this group, send email to sage-...@googlegroups.com. >>>> >>>> >>>> Visit this group at https://groups.google.com/group/sage-devel. >>>> >>>> >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>>> >>>> -- >>> Sent from my massive iPhone 6 plus. >>> >> -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
