Bitcoincharts.com down?

[BitCrawler]

Ey guys, what happened to bitcoincharts.com??

At first I got a 404 error when I wanted to view the charts. So I went to the homepage and got some German website?
http://bitcoincharts.com/media/e-l-g_vcard011.png

What happened?

[1714194696]

1714194696

[1714194696]

1714194696

[FoxMURDER]

kind of seems bitcoincharts.com got dns hijacked. looked like the BitcoinCharts Pro advertised there was used for phishing.

[TheButterZone]

Downtime

Nov. 10, 2013, 2:45 p.m.

Our provider (Hetzner) messed up it's routing and telephone support can not be reached. It looks like it's working again but I have no idea whether problems will return or not.

[elm]

I cant open bitcoincharts.com

how about you guys?

thanks

[deepceleron]

Down. But

This time it's different. The bitcoincharts.com DNS record has been changed, and there is no "A record" IP addresses, and the last known IP address is unresponsive.

Registrar URL: http://www.1api.net
Updated Date: 2013-11-27T18:34:45Z
Creation Date: 2010-11-08T02:11:21Z
Registrar Registration Expiration Date: 2014-11-08T02:11:21Z
Registrar: 1api GmbH

However, there is a ipv6 AAAA DNS record that appears to be working, I was able to to access the page once through a barely-responsive overloaded proxy, as my layers of firewall block native ipv6:

;; ANSWER SECTION:
bitcoincharts.com.      140     IN      AAAA    2400:cb00:2048:1::6ca2:c7b7
bitcoincharts.com.      140     IN      AAAA    2400:cb00:2048:1::6ca2:c6b7

traceroute to bitcoincharts.com (2400:cb00:2048:1::6ca2:c7b7), 30 hops max, 40 byte packets
 1  2a02:348:82::1 (2a02:348:82::1)  8.580 ms  8.528 ms  8.439 ms
 2  xl-internetservices.nl.ip6.jointtransit.nl (2a02:10:0:1::e:3)  11.417 ms  3.475 ms  11.262 ms
 3  ge-0.ams-ix.amstnl02.nl.bb.gin.ntt.net (2001:7f8:1::a500:2914:1)  2.668 ms  2.603 ms  2.699 ms
 4  * ae-5.r03.amstnl02.nl.bb.gin.ntt.net (2001:728:0:2000::11a)  3.403 ms  3.449 ms
 5  2001:590:2:2e::1 (2001:590:2:2e::1)  4.144 ms  4.062 ms  3.981 ms
 6  as13335.xe-3-0-2.ar1.ams3.nl.nlayer.net (2001:590::3f8d:df1e)  1.206 ms  1.337 ms  1.553 ms
 7  2400:cb00:20:1024::8d65:4b32 (2400:cb00:20:1024::8d65:4b32)  2.214 ms  1.520 ms  2.348 ms

IPv6 Ping Output:

PING 2400:cb00:2048:1::6ca2:c7b7(2400:cb00:2048:1::6ca2:c7b7) 32 data bytes
40 bytes from 2400:cb00:2048:1::6ca2:c7b7: icmp_seq=0 ttl=60 time=1.66 ms
40 bytes from 2400:cb00:2048:1::6ca2:c7b7: icmp_seq=1 ttl=60 time=1.50 ms
40 bytes from 2400:cb00:2048:1::6ca2:c7b7: icmp_seq=2 ttl=60 time=1.65 ms
40 bytes from 2400:cb00:2048:1::6ca2:c7b7: icmp_seq=3 ttl=60 time=1.62 ms

--- 2400:cb00:2048:1::6ca2:c7b7 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3012ms
rtt min/avg/max/mdev = 1.509/1.613/1.668/0.074 ms, pipe 2

I know that the admin was thinking of changing hosting, since they messed up his routing twice in the last year.

[elm]

thanks, now I could connect again. lets see for how long