mtgox 0.02 a few seconds ago ^124.77
Along with 15 minutes of lag. Cutting edge systems!!!1 
Topic: Wall Observer BTC/USD - Bitcoin price movement tracking & discussion - page 34072. (Read 26630516 times)
April 21, 2013, 02:06:06 PM
April 21, 2013, 02:06:03 PM
Mtgox trading engine lag: 16m 6s
April 21, 2013, 02:05:35 PM
On the one hand they claim this is a layer7 attack then they show this prolexic report, which is about layer 3-4. If they have an attack vector for an application layer attack why spend the resources for a expensive network layer attack?
It still smells fishy to me.
If nothing else they are shutting down their service when under attack to prevent "lag"
Which is the only responsible thing to do. A ddos attacked market racking up lag isn't a normal market. Thus the only responsible way to fight back is to turn off the market for the time being till the attack passes. At which point allow people to trade normally once again.It still smells fishy to me.
If nothing else they are shutting down their service when under attack to prevent "lag"
If this really is a layer7 attack it might be able to be sustained indefinitely. And what then?
Lol, you people need to stop trolling with Gox going down "indefinitely." This has happened like 20 times before, and its already back up. This is like, completely and utterly boring and normal.
That's why it's called back to normal in the bubble autonomy chart.
April 21, 2013, 02:04:48 PM
mtgox 0.02 a few seconds ago ^124.77
April 21, 2013, 02:04:24 PM
On the one hand they claim this is a layer7 attack then they show this prolexic report, which is about layer 3-4. If they have an attack vector for an application layer attack why spend the resources for a expensive network layer attack?
It still smells fishy to me.
If nothing else they are shutting down their service when under attack to prevent "lag"
Which is the only responsible thing to do. A ddos attacked market racking up lag isn't a normal market. Thus the only responsible way to fight back is to turn off the market for the time being till the attack passes. At which point allow people to trade normally once again.It still smells fishy to me.
If nothing else they are shutting down their service when under attack to prevent "lag"
If this really is a layer7 attack it might be able to be sustained indefinitely. And what then?
Lol, you people need to stop trolling with Gox going down "indefinitely." This has happened like 20 times before, and its already back up. This is like, completely and utterly boring and normal.
That's why it's called back to normal in the bubble autonomy chart.
April 21, 2013, 02:02:40 PM
On the one hand they claim this is a layer7 attack then they show this prolexic report, which is about layer 3-4. If they have an attack vector for an application layer attack why spend the resources for a expensive network layer attack?
It still smells fishy to me.
If nothing else they are shutting down their service when under attack to prevent "lag"
Which is the only responsible thing to do. A ddos attacked market racking up lag isn't a normal market. Thus the only responsible way to fight back is to turn off the market for the time being till the attack passes. At which point allow people to trade normally once again.It still smells fishy to me.
If nothing else they are shutting down their service when under attack to prevent "lag"
If this really is a layer7 attack it might be able to be sustained indefinitely. And what then?
Lol, you people need to stop trolling with Gox going down "indefinitely." This has happened like 20 times before, and its already back up. This is like, completely and utterly boring and normal.
April 21, 2013, 02:01:10 PM
Clear your cache to see wonderful numbers [...]
You're right, thanks for the tip.
April 21, 2013, 01:59:19 PM
On the one hand they claim this is a layer7 attack then they show this prolexic report, which is about layer 3-4. If they have an attack vector for an application layer attack why spend the resources for a expensive network layer attack?
It still smells fishy to me.
If nothing else they are shutting down their service when under attack to prevent "lag"
Which is the only responsible thing to do. A ddos attacked market racking up lag isn't a normal market. Thus the only responsible way to fight back is to turn off the market for the time being till the attack passes. At which point allow people to trade normally once again.It still smells fishy to me.
If nothing else they are shutting down their service when under attack to prevent "lag"
If this really is a layer7 attack it might be able to be sustained indefinitely. And what then?
April 21, 2013, 01:58:26 PM
Interface is up for me. bitcoinity see gox and show 8 minutes lag without trading. Again.
April 21, 2013, 01:57:12 PM
GOX TRADING ENGINE BACK. YEEHAW!
It is still "502 Bad Gateway" to me...
Last price:$124.90000
High:$132.00000
Low:$117.86000
Volume:88053 BTC
Weighted Avg:$125.67729
Last Updated: 6 Minutes Ago
April 21, 2013, 01:56:00 PM
GOX TRADING ENGINE BACK. YEEHAW!
It is still "502 Bad Gateway" to me...
April 21, 2013, 01:51:26 PM
GOX TRADING ENGINE BACK. YEEHAW!
April 21, 2013, 01:49:33 PM
Something happening at gox? Moody is outputting random stuff.
April 21, 2013, 01:48:13 PM
MtGox website: Database access error, please retry later
wtf?!
wtf?!
April 21, 2013, 01:47:55 PM
On the one hand they claim this is a layer7 attack then they show this prolexic report, which is about layer 3-4. If they have an attack vector for an application layer attack why spend the resources for a expensive network layer attack?
It still smells fishy to me.
If nothing else they are shutting down their service when under attack to prevent "lag"
Which is the only responsible thing to do. A ddos attacked market racking up lag isn't a normal market. Thus the only responsible way to fight back is to turn off the market for the time being till the attack passes. At which point allow people to trade normally once again. It still smells fishy to me.
If nothing else they are shutting down their service when under attack to prevent "lag"
April 21, 2013, 01:46:05 PM
On the one hand they claim this is a layer7 attack then they show this prolexic report, which is about layer 3-4.
It still smells fishy to me.
It still smells fishy to me.
Well, I doubt they are claiming today is April 11th.
Oh, in that case, pretty solid arguing folks!
April 21, 2013, 01:42:11 PM
On the one hand they claim this is a layer7 attack then they show this prolexic report, which is about layer 3-4. If they have an attack vector for an application layer attack why spend the resources for a expensive network layer attack?
It still smells fishy to me.
If nothing else they are shutting down their service when under attack to prevent "lag"
It still smells fishy to me.
If nothing else they are shutting down their service when under attack to prevent "lag"
April 21, 2013, 01:35:13 PM
Nah this is totally a shoop. CONSPIRACY!!!
I have an idea! Why doesn't Gox publish the destination IPs on twitter, so we can all point LOIC at it? (disclaimer I'm a complete DDoS newb and i'm sure there's some reason that 'firing back' doesn't work.)
(Forum etiquette - quote pruning pro-tip - prune large images in quoted replies by throwing in a height= width= into the [img] tag, make people's scroll fingers happy
) 
April 21, 2013, 01:33:25 PM
should we get worried, this looks more serious than ddos
April 21, 2013, 01:32:11 PM
Nah this is totally a shoop. CONSPIRACY!!! Prolexic isn't even a real company, Gox just made them up.
(In seriousness: They're learning a thing or two about transparency. They should release this third-party event report (along with a way to verify it via the third party) after each and every single claimed DDoS event.)
I have an idea! Why doesn't Gox publish the source IPs on twitter, so we can all point LOIC at them? (disclaimer I'm a complete DDoS newb and i'm sure there's some reason that 'firing back' doesn't work, so this is probably a stupid idea
.) (Forum etiquette - quote pruning pro-tip - prune large images in quoted replies by throwing in a height= width= into the [img] tag, make people's scroll fingers happy
) Jump to: