Right, pinging 23.253.225.173 or 23.253.241.126 times out for me. Here's tracepath:
chris@retina:~$ tracepath new-www.haskell.org 1: retina.local 0.130ms pmtu 1500 1: AirPort-Express-di-MYEGO.local 2.633ms 1: AirPort-Express-di-MYEGO.local 1.481ms 2: 10.233.128.1 29.365ms asymm 3 3: 10.6.105.26 255.868ms 4: 10.251.245.201 202.527ms 5: 10.251.240.22 95.021ms 6: 10.251.241.1 332.744ms asymm 4 7: 10.247.125.241 56.229ms asymm 5 8: 10.251.245.194 38.307ms asymm 6 9: 10.6.4.17 195.425ms asymm 7 10: 10.254.11.245 156.151ms asymm 15 On 8 September 2014 18:15, Herbert Valerio Riedel <[email protected]> wrote: > On 2014-09-08 at 15:37:08 +0200, Christopher Done wrote: >> As a random data point, I'm on Telecom Italia in Italy and I've never >> been able to resolve new-www.haskell.org. traceroute gives up. I'm not >> sure how much of Italy can't access that domain. It's the same for >> darcs.haskell.org. Hopefully this issue won't transfer to the main >> haskell.org domain. > > that's totally weird... are you saying you can DNS resolve some > *.haskell.org names, but not others? Or that you can't reach the IP > darcs.haskell.org points to? > > for the record, here's the IPs those entries ought to resolve to > currently: > > new-www.haskell.org. IN A 23.253.241.126 > new-www.haskell.org. IN AAAA > 2001:4800:7817:104:be76:4eff:fe05:a27e > > darcs.haskell.org. IN A 23.253.225.173 > > > Also, can you currently reach https://ghc.haskell.org/trac/ghc/ ? > _______________________________________________ haskell-infrastructure mailing list [email protected] http://community.galois.com/mailman/listinfo/haskell-infrastructure
