[www.]ripple.com is unreachable

[alexkravets]

I guess nothing says "success" as being victimized by DDOS ? :-)

clafferty-lt:~ alex$ traceroute www.ripple.com
traceroute to www.ripple.com (216.180.249.121), 64 hops max, 52 byte packets
 1  juniperfw (10.1.0.1)  1.052 ms  0.971 ms  0.915 ms
 2  rrcs-173-196-196-177.west.biz.rr.com (173.196.196.177)  1.229 ms  1.461 ms  1.586 ms
 3  rrcs-24-43-182-130.west.biz.rr.com (24.43.182.130)  5.310 ms  5.188 ms  5.562 ms
 4  agg11.lsaicaev-ccr02.socal.rr.com (72.129.18.194)  10.657 ms  9.243 ms  8.285 ms
 5  agg26.tustcaft-ccr01.socal.rr.com (72.129.17.2)  10.687 ms  11.551 ms  8.040 ms
 6  ae-5-0.cr0.lax30.tbone.rr.com (66.109.6.64)  7.368 ms  9.038 ms  7.956 ms
 7  ae-1-0.pr0.lax10.tbone.rr.com (66.109.6.131)  5.762 ms
    66.109.9.26 (66.109.9.26)  5.976 ms  5.947 ms
 8  xe-2-0-4.ar1.lax1.us.nlayer.net (69.31.127.73)  7.142 ms  7.397 ms  7.838 ms
 9  ae0-100g.cr1.lax1.us.nlayer.net (69.31.127.137)  4.194 ms  12.697 ms  9.961 ms
10  xe-1-0-0.cr1.iah1.us.nlayer.net (69.22.142.121)  41.366 ms
    xe-2-0-1.cr1.dfw1.us.nlayer.net (69.22.142.22)  71.525 ms  39.587 ms
11  xe-4-2-1.cr1.atl1.us.nlayer.net (69.22.142.118)  54.979 ms  54.996 ms  55.351 ms
12  * ae1-40g.ar1.atl1.us.nlayer.net (69.31.135.130)  62.833 ms  57.028 ms
13  as3595.xe-2-0-5-103.ar1.atl1.us.nlayer.net (69.31.135.54)  60.308 ms  56.196 ms  70.749 ms
14  atl-core-int-ga.gnax.net (209.51.137.218)  58.144 ms  54.525 ms  54.335 ms
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *

[Spekulatius]

Hmm, who..

War of the X-coins!

[markm]

SImply run the client yourself on your own local machine. It does not actually need to be on someone else's webserver at all, you can browse it locally as a file:/// type of URL

-MarkM-

[JoelKatz]

The internal validator network was intact and functioning as was the public-facing payment network systems. The web site was down due to some problem at the provider. I don't know yet whether it was a denial of service attack or a technical problem, but last I heard they suspected it was a technical problem.

We're currently keeping the number of site running servers and providing the client small so that we can easily fix bugs and make improvements that require coordinated changes to both the client and the server. I'm hopeful that will die down soon and we can move on to making the network more distributed.