** Official ** Cryptsy funds are safe and secure

[XRcode]

Hmmmmmmmmmm....

[1713947032]

1713947032

[1713947032]

1713947032

[1713947032]

1713947032

[1713947032]

1713947032

[1713947032]

1713947032

[amytheplanarshift]

Hmmmmmmmmmm....

Mine is still pointing to secure.4rx.com over here. Interesting that you are getting something different.

[smitemesmith]

Thank you for the update

[DigitalDoom]

Hmmmmmmmmmm....

Mine is still pointing to secure.4rx.com over here. Interesting that you are getting something different.

Really? Do you really find that interesting?

Personally, it's not something I find at all interesting.

LOL...JK

[peonminer]

Provider is now officially calling it a DDOS again all funds are fine exchange is actually running just fine internally of course noone can get to it which is obviously an issue

For those of us with auto payout from pools sending directly to cryptsy deposit addresses, will those funds still transfer safely or at all? Should we stop the auto transfers until the site is back up?

[nhminer]

John, can you please post the real IP address for cryptsy.com

I believe it is 166.78.0.180 but just want to confirm it.

~nh

[weav]

Hmmmmmmmmmm....

Now that's weird

Code:

www.luggagepros.com resolves to 66.40.35.112 Peer 1 Dedicated Hosting, Georgia

Seemingly unrelated to Incapsula..

but this:

I can confirm invalid SSL certificate. I'm getting SSL cert for *.professionalperformanceonline.nl -- definitely not going to log in.

resolves to 149.126.74.128, again Incapsula

Hopefully just some Incapsula issue

[r3wt]

Provider is now officially calling it a DDOS again all funds are fine exchange is actually running just fine internally of course noone can get to it which is obviously an issue

For those of us with auto payout from pools sending directly to cryptsy deposit addresses, will those funds still transfer safely or at all? Should we stop the auto transfers until the site is back up?

i cant speak for the cryptsy team, but i would atleast as a precautionary metric.

[nhminer]

I'm not logging in yet, but at least now I see data ...

https://166.78.0.180/markets/view/43

~nhminer

[kevindeangelis]

Thanks for keeping everyone posted on the status of things!

[Lauda]

Provider is now officially calling it a DDOS again all funds are fine exchange is actually running just fine internally of course noone can get to it which is obviously an issue

For those of us with auto payout from pools sending directly to cryptsy deposit addresses, will those funds still transfer safely or at all? Should we stop the auto transfers until the site is back up?

You're sending it to their wallet not their website.. jeesh

[saber]

Thanks for the update John!

[donjonson]

Bad for letting the attack to happen.

Good for the constant communication and update, this is what's needed when this type of things happen.

[ohiwastedmylif]

waiting for bigsausagepizza.com to be the new re-route

[snowcrashed]

I'm not logging in yet, but at least now I see data ...

https://166.78.0.180/markets/view/43

~nhminer

I would highly advise against anyone using that link to attempt to login.  Especially since the SSL is not functioning.

Bad for letting the attack to happen.

Good for the constant communication and update, this is what's needed when this type of things happen.

I wouldn't necessarily blame the website operators for "letting" the attack happen, after all they are not the service provider.  I would assume they picked a provider who has some form of DDoS protection.

[BitJohn]

Yes our provider has DDOS protection however nothing is DDOS proof. We are implementing even more protections with this downtime and will be up VERY soon.

[nhminer]

I'm not logging in yet, but at least now I see data ...

https://166.78.0.180/markets/view/43

~nhminer

I would highly advise against anyone using that link to attempt to login.  Especially since the SSL is not functioning.

Agreed -- not for logging in, just to get data -- SSL certificate on this site will identify itself as cryptsy.com, which is correct -- the SSL match will fail b/c the link uses the IP address

~nh

[LosingAlpha]

Provider is now officially calling it a DDOS again all funds are fine exchange is actually running just fine internally of course noone can get to it which is obviously an issue

For those of us with auto payout from pools sending directly to cryptsy deposit addresses, will those funds still transfer safely or at all? Should we stop the auto transfers until the site is back up?

You're sending it to their wallet not their website.. jeesh

Well, yeah from the weird SSL certs it kinda looks like the domain has been hijacked - possibly not, but without an official steer we're certainly in 'do not log in under any circumstances' territory.

If it *is* the case that the domain that got boosted but the real server hasn't been compromised (which if it has, is probably the case - there are far more elegant ways of doing this if you get control of the server) then your wallets are safe -  unless you log in, in which case the attacker would just scoop up your login details, use them to log into the real site, and drain your funds.

[peonminer]

Provider is now officially calling it a DDOS again all funds are fine exchange is actually running just fine internally of course noone can get to it which is obviously an issue

For those of us with auto payout from pools sending directly to cryptsy deposit addresses, will those funds still transfer safely or at all? Should we stop the auto transfers until the site is back up?

You're sending it to their wallet not their website.. jeesh

Didn't know if they had l33t online wallets or not. Good they didn't!!!

[frobley]

A record is: qrq4x.x.incapdns.net -> [ 149.126.77.157  ]
http://www.intodns.com/cryptsy.com