Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
They can track which orders really came in from you and which are caused by the system bug but it will take some time to go through all the executions done last days. TT is a big operator so there will be a lot of executions to check.
It would be nice to know if this a global incident or just related to some brokers only.
Well we don't know is this a hack or a bug but this kind of problems can always escalate quickly into very hazardous events and even kill the companies. Let's hope this is not the case and they are able to solve the situation soon.
EDIT:
These kind of events are very good reminders for us: Use always the full available leverage (not risk) so you can keep as little money as possible under the broker risk. And always trade from the limited liability entities such LLC
Part of the issue was, I saw open positions, when i was not trading while I was at work, and contacted Amp to flatten them......somehow that opened new positions in the opposite direction. Anyway, it is what it is. I feel like the more I plead my case the worse things get. I have taken big losses, but its hard to accept them when you did not make them. Thanks for your input. I was not on TT by the way, but Sierra with their order routing.
Trading: Primarily Energy but also a little Equities, Fixed Income, Metals and Crypto.
Frequency: Many times daily
Duration: Never
Posts: 5,055 since Dec 2013
Thanks Given: 4,397
Thanks Received: 10,220
Sorry to hear of your problems @Fryer. This sounds eerily like the Phillips Capital (and hence Ninja Trader/Edgeclear/and others) problem from last week.
I was a little surprised when I heard how decisively one broker shut down TT users and liquidated positions. If this was a common problem with many of their accounts I can see why they did it. Since I haven't currently heard of similar problems at other FCMs I wonder if that broker have their own TT setup and if something went wrong that specifically effected them.
In your case, since you called them, and told them to flatten you, I hope you should be protected. The problems arise when people saw positions they didn't recognize and flattened them themselves.
I understand the FCMs concerns with this. If you think about it, in some ways that's a free option. If you see a position you don't recognize it, document it and then offset it. If it goes in your favor, then it was a trade you put on, if it goes against you it's their fault because they showed your position incorrectly and you have the documentation to prove it!
From the sierrachart thread that @Scalpguy linked it sounded like there was an issue with the auto-liquidation feature, which I doubt most fcm's have enabled.
looks like it happened to 7 different FCMs and looks to be TT's error.
TT says "issue is impacting a subset of users" so this probably means all the 7 different FCMs on this "subset" TT server environment were affected. Which would explain why it wasn't across all FCMs. Something was wrong with this specific TT server environment.
Trading: Primarily Energy but also a little Equities, Fixed Income, Metals and Crypto.
Frequency: Many times daily
Duration: Never
Posts: 5,055 since Dec 2013
Thanks Given: 4,397
Thanks Received: 10,220
Believe the issue yesterday was a minor connectivity issue which didn't effect routing. Interestingly I monitor my connection to TT using PingPlotter. I had minor connectivity issues at the time TT indicated there was a problem but PingPlotter showed no issues with the connection. Makes me wonder whether the connectivity issue was between their front end (which I believe is cloud based) and their back end (which I believe is exchange colocated).
I reached out to several people at FCMs and all but one said they had heard of the issues but they had not had any issues themselves. Trying to confirm with the one who had issues, exactly what issues they had.