It is probably important to know that those servers are anycasted via the AS112 project (www.as112.net). Perhaps the AS112 operator you are seeing is having issues. You could try to identify which one and let them know.
Thanks,
John 
-----Urspr�ngliche Nachricht-----
John van Oppen wrote:
It is probably important to know that those servers are anycasted via the AS112 project (www.as112.net). Perhaps the AS112 operator you are seeing is having issues. You could try to identify which one and let them know.
Three things:
1) At least one other person reports the same problem.
2) They've been going up and down, so even if you go check and it
works that one time, you may have caught it up.
3) I'd try to ask it which anycast instance it is, but both are
sending ICMP unreachables at the moment. A traceroute says,
traceroute to 192.175.48.42 (192.175.48.42), 64 hops max, 44 byte packets
[snip]
6 p4-3-0.RAR2.SanJose-CA.us.xo.net (65.106.5.161) 34.390 ms 5.774 ms 5.280 ms
7 p1-0.IR1.PaloAlto-CA.us.xo.net (65.106.5.178) 44.123 ms 21.508 ms 5.672 ms
8 207.88.240.70.ptr.us.xo.net (207.88.240.70) 5.473 ms 26.629 ms 14.045 ms
9 ix-4-6.core3.PDI-PaloAlto.Teleglobe.net (207.45.196.66) 6.637 ms 10.697 ms 5.863 ms
10 blackhole-2.iana.org (192.175.48.42) 6.547 ms 6.561 ms 8.935 ms
I don't have a BGP view of the world from XO, our provider on
this link. Anyone know which instance that is? It's "close" to
Palo Alto? From,
http://public.as112.net/node/2
My best guess is ISC? But F-Root seems to be OK from here, FWIW, and
a traceroute to F doesn't jump through that IX.
2) They've been going up and down, so even if you go check and it
works that one time, you may have caught it up.
Something's definitely going on, as the server at ISC seems to be coming and going in operation.
3) I'd try to ask it which anycast instance it is, but both are
sending ICMP unreachables at the moment. A traceroute says,
Always can be gleaned from this:
dig @prisoner.iana.org hostname.as112.net any
Which, from my local ISP's point of view (Sympatico in Canada) seems to yield different answers.
wfms
Looks like it was ISC? And they withdrewn their routes for a bit?
For a while I got (from XO in CA),
$ host -t txt -c chaos hostname.bind 192.175.48.6
Using domain server 192.175.48.6:
hostname.bind CHAOS descriptive text "black-1.sth.netnod.se"
Goin' transatlantic! Traceroutes seemed to verify.
But now I'm back on,
$ host -t txt -c chaos hostname.bind 192.175.48.6
Using domain server 192.175.48.6:
hostname.bind CHAOS descriptive text "hazel.isc.org"
ISC. Got a note from an ISC reader verifying they are/were having
issues with their AS112 server.