Bitcoin Forum

Other => Meta => Topic started by: pekv2 on July 17, 2012, 05:47:54 AM



Title: What happened to bitcointalk when the btc prices rampaged?
Post by: pekv2 on July 17, 2012, 05:47:54 AM
What happened to bitcointalk when the btc prices rampaged?


Title: Re: What happened to bitcointalk when the btc prices rampaged?
Post by: phantitox on July 17, 2012, 05:48:36 AM
million dollar question  :-\


Title: Re: What happened to bitcointalk when the btc prices rampaged?
Post by: myrkul on July 17, 2012, 05:51:01 AM
Well, maybe not million dollar, but probably worth at least a few hundred BTC.


Title: Re: What happened to bitcointalk when the btc prices rampaged?
Post by: pekv2 on July 17, 2012, 05:51:11 AM
million dollar question  :-\

I wanted to see how many active users that were on.

I heard a few other places went down as well.


Title: Re: What happened to bitcointalk when the btc prices rampaged?
Post by: theymos on July 17, 2012, 05:55:00 AM
I don't know. sshing into the server always timed out, so I couldn't investigate. My guess is that it was caused by a lot of traffic.


Title: Re: What happened to bitcointalk when the btc prices rampaged?
Post by: pekv2 on July 17, 2012, 05:57:20 AM
I bet man, sent it soaring through the roof.

You think the the pw encryption had anything to do with it as such a large amount hit the server at once? Since it is technically new to the software? Or atleast to us? Or new to your hardware?

Gosh, to bad the user count got wiped or didn't have a chance to be used today. Would have been exciting to see.


Title: Re: What happened to bitcointalk when the btc prices rampaged?
Post by: yogi on July 17, 2012, 05:59:56 AM
There was a news story recently where a bunch of traders were ddos'ing news sites to stop the flow of information and give them an advantage in the market.

Could that be what happen here?


Title: Re: What happened to bitcointalk when the btc prices rampaged?
Post by: Bitcoin Oz on July 17, 2012, 06:09:07 AM
Someone trying to calm speculation is my bet.


Title: Re: What happened to bitcointalk when the btc prices rampaged?
Post by: theymos on July 17, 2012, 06:10:33 AM
I bet man, sent it soaring through the roof.

You think the the pw encryption had anything to do with it as such a large amount hit the server at once? Since it is technically new to the software? Or atleast to us? Or new to your hardware?

I doubt it. Hashing one password takes only one-twentieth of a second, and it only happens when someone logs in.

Quote from: pekv2
Gosh, to bad the user count got wiped or didn't have a chance to be used today. Would have been exciting to see.

https://bitcointalk.org/index.php?action=stats


Title: Re: What happened to bitcointalk when the btc prices rampaged?
Post by: Serge on July 17, 2012, 06:14:37 AM
shortly after bitcointalk was down, mtgox went out too, strangely mtgoxlive was responding although feeds were frozen for a significant period of time

btw MTGOX, if you're reading this, when are you going to fix live part of mtgoxlive site?


Title: Re: What happened to bitcointalk when the btc prices rampaged?
Post by: pekv2 on July 17, 2012, 06:16:42 AM
oic, cool. Was hoping for little bit under the record of 3809 (June 19, 2011, 02:56:13 PM)

Uh well, maybe next time.


Title: Re: What happened to bitcointalk when the btc prices rampaged?
Post by: notme on July 17, 2012, 06:26:29 AM
I bet man, sent it soaring through the roof.

You think the the pw encryption had anything to do with it as such a large amount hit the server at once? Since it is technically new to the software? Or atleast to us? Or new to your hardware?

I doubt it. Hashing one password takes only one-twentieth of a second, and it only happens when someone logs in.

Quote from: pekv2
Gosh, to bad the user count got wiped or didn't have a chance to be used today. Would have been exciting to see.

https://bitcointalk.org/index.php?action=stats

So 20 simultaneous login attempts per second with random credentials is all it takes to lock up a core?  Hopefully you at least limit login attempts per ip so they have to use a botnet or a bunch of proxies.


Title: Re: What happened to bitcointalk when the btc prices rampaged?
Post by: BadBear on July 17, 2012, 06:27:44 AM
I bet man, sent it soaring through the roof.

You think the the pw encryption had anything to do with it as such a large amount hit the server at once? Since it is technically new to the software? Or atleast to us? Or new to your hardware?

I doubt it. Hashing one password takes only one-twentieth of a second, and it only happens when someone logs in.

Quote from: pekv2
Gosh, to bad the user count got wiped or didn't have a chance to be used today. Would have been exciting to see.

https://bitcointalk.org/index.php?action=stats

So 20 simultaneous login attempts per second with random credentials is all it takes to lock up a core?  Hopefully you at least limit login attempts per ip so they have to use a botnet or a bunch of proxies.

I think it's more likely a problem with MtGox, they've always had issues with heavy volume. God forbid anyone actually use their exchange.


Title: Re: What happened to bitcointalk when the btc prices rampaged?
Post by: sadpandatech on July 17, 2012, 07:04:44 AM
I bet man, sent it soaring through the roof.

You think the the pw encryption had anything to do with it as such a large amount hit the server at once? Since it is technically new to the software? Or atleast to us? Or new to your hardware?

I doubt it. Hashing one password takes only one-twentieth of a second, and it only happens when someone logs in.

Quote from: pekv2
Gosh, to bad the user count got wiped or didn't have a chance to be used today. Would have been exciting to see.

https://bitcointalk.org/index.php?action=stats

So 20 simultaneous login attempts per second with random credentials is all it takes to lock up a core?  Hopefully you at least limit login attempts per ip so they have to use a botnet or a bunch of proxies.

I think it's more likely a problem with MtGox, they've always had issues with heavy volume. God forbid anyone actually use their exchange.

+1 The outage just happened to be right as the order book took on MASSIVE shuffling.