Thanks Pat. I was hoping you would weigh in on this. I'm trading through FIX API, which (as you appropriately qualified) will be a bit different than the above scenario. I've actually progressed quite a bit from when I posted this question...I've recently gone live with one of your competitors but have had a very poor experience (no, a terrible experience). But at least no transatlantic latency (well...once I asked for the nth time for them to base my 'accout' in London - which came after asking for correct ip/host for the London server, which even then was provided wrong a couple more times. I can't make this stuff up - and its all much worse than I'm describing). All that being said...your timing is actually perfect. Just the other day, I posed a few questions regarding latency and such to he TT rep I've been in contact with, but thus far have have not received answers. Perhaps you could help? When using the TT FIX Adapter, what’s the latency from LD4 to Eurex? (From when the trade is sent by TT) Is the above figure, the (average) amount of time from when the trade is sent from LD4 to reach Eurex’s Matching Engine or when they’re distributed? What’s the average latency incurred by TT’s infrastructure (risk checks, etc.)? What’s the latency of the MD that TT receives from Eurex to LD4? (and what’s the latency (if any) before TT passes that on to the client)? As I said to him, I imagine these are all stats you guys probably keep a pretty close eye on. The not hearing back has me a bit concerned though. Granted this has more to do with my experience with your competitor than with TT thus far, but I'm beginning to think that going with a smaller shop may very well be the best (only painless) option. Just for the laugh of it...when I emailed the rep after not hearing back, he responded (quite quickly, to be fair) letting me know he's reaching out to xyz dept for some answers. Here's the good part...in the email back to me...he got my name wrong. For all those that may not know, this TT FIX adapter is $1,000/month + a fee/fill). I mean, I'm paying about that in car payments for my Audi and wife's Acura and they seemed to get my name right at the dealership?! And they didn't even have the benefit of having the email I had just sent them, with my name on it, in front of them.
Thank you for the information @oversea. If you could PM me details about your rep here, I'd appreciate it. I am tracking down information for you regarding times. This is a tricky subject as there are many, many variables involved. It will help if you PM me with your clearer and where your network is hosted. For example are you going through TT NET or through an environment hosted by an FCM or bank. It makes a big difference. Also, have you entered any tickets with our DTS support team? I'd like to review those. https://developer.tradingtechnologies.com/dts-development-environment
I just spoke to Patrick for my API requirements in Europe and he was most helpful. Very knowledgeable guy. Thank you Patrick.
No. Trader13 did not make a "very good point". Saying "servers being down in their datacenters or a network outage in their area" is grossly over-simplifying a complex technical topic, its the equivalent of saying "GBPUSD crashed because Obama farted". Its far too complex to even begin covering here, but in essence unless you are doing a "flash boys" and connecting your own private fibre, you really do not need to concern yourself with datacentre location or outage of a specific network. No offense, but what Trader13 said is the equivalent of waving a rubber chicken over your computer to try to figure out why your broker's platform isn't working. The above applies to any internet-facing business, be it Amazon, IB or anyone else. You would need far more information (the sort of internal information only available to a company's IT department) in order to be able to make an accurate statement.