Topic: Bitcoin-24.com Down? (Read 865 times)

Now I was in:

Slow Server - The 10*10G between Beauharnois and Montréal are down.
Repair operations are in progress. The impacted links should come back up after 6pm Montreal localtime.

From spain i get a 504 gw timeout

ping bitcoin-24.com
PING bitcoin-24.com (198.27.65.125): 56 data bytes
64 bytes from 198.27.65.125: icmp_seq=0 ttl=48 time=123.434 ms
64 bytes from 198.27.65.125: icmp_seq=1 ttl=47 time=122.317 ms
64 bytes from 198.27.65.125: icmp_seq=2 ttl=47 time=124.690 ms
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
64 bytes from 198.27.65.125: icmp_seq=5 ttl=47 time=146.227 ms
64 bytes from 198.27.65.125: icmp_seq=6 ttl=48 time=118.710 ms
Request timeout for icmp_seq 7
64 bytes from 198.27.65.125: icmp_seq=8 ttl=48 time=119.242 ms
Request timeout for icmp_seq 9
64 bytes from 198.27.65.125: icmp_seq=10 ttl=47 time=134.691 ms
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
64 bytes from 198.27.65.125: icmp_seq=13 ttl=47 time=120.881 ms
64 bytes from 198.27.65.125: icmp_seq=14 ttl=48 time=127.564 ms
64 bytes from 198.27.65.125: icmp_seq=15 ttl=47 time=126.126 ms
64 bytes from 198.27.65.125: icmp_seq=16 ttl=47 time=133.408 ms
64 bytes from 198.27.65.125: icmp_seq=17 ttl=47 time=127.295 ms
^C
--- bitcoin-24.com ping statistics ---
19 packets transmitted, 12 packets received, 36.8% packet loss
round-trip min/avg/max/stddev = 118.710/127.049/146.227/7.513 ms

Weird.

traceroute to bitcoin-24.com (198.27.65.125), 64 hops max, 52 byte packets
 1  home (192.x.x.x)  3.402 ms  3.173 ms  1.517 ms
 2  10.xx.xx.xx (10.xx.xx.xx)  18.717 ms  32.934 ms  35.215 ms
 3  10.x.x.x (10.x.x.x)  12.740 ms  7.365 ms  9.681 ms
 4  ae-8-8.ebr1.frankfurt1.level3.net (4.69.141.58)  47.751 ms
    213.242.114.5 (213.242.114.5)  43.141 ms  40.934 ms
 5  ae-61-61.csw1.frankfurt1.level3.net (4.69.140.2)  38.534 ms
    ae-8-8.ebr1.frankfurt1.level3.net (4.69.141.58)  46.698 ms
    ae-71-71.csw2.frankfurt1.level3.net (4.69.140.6)  40.168 ms
 6  ae-61-61.csw1.frankfurt1.level3.net (4.69.140.2)  41.238 ms
    ae-81-81.csw3.frankfurt1.level3.net (4.69.140.10)  37.710 ms
    ae-91-91.csw4.frankfurt1.level3.net (4.69.140.14)  40.417 ms
 7  * ae-1-60.edge5.frankfurt1.level3.net (4.69.154.9)  48.740 ms *
 8  rbx-g2-a9.fr.eu (91.121.131.130)  43.088 ms  39.911 ms  42.201 ms
 9  rbx-s6-6k.fr.eu (178.33.100.66)  60.542 ms
    rbx-g2-a9.fr.eu (91.121.131.130)  43.945 ms
    ldn-5-6k.uk.eu (91.121.131.242)  78.394 ms
10  * * *
11  * mtl-2-6k.qc.ca (178.32.135.47)  239.754 ms *
12  * * mtl-2-6k.qc.ca (178.32.135.47)  131.414 ms
13  * * *
14  * * *
15  bhs-2-6k.qc.ca (198.27.73.16)  152.824 ms
    bitcoin-24.com (198.27.65.125)  121.689 ms
    bhs-2-6k.qc.ca (198.27.73.16)  122.991 ms

Ah, OK, NVM, seems it's some kind of faulty link between Europe and Canada.

Is Bitcoin-24.com giving everyone "Internal Server Error" replies or just me?

This is so not cool.