Using the same ISP from the same location, when pinging gw*.ibllc.com or cm*.esignal.com, at some days I get an average of 170ms and on some days an average of 600ms. I tried an alternative ISP I have and it's more or less the same. This is no more controllable than the weather. Not much can be done about this imho.
just for shits and giggles i started pings from a datacenter with mci bandwidth - on a friday night going out over T3 plus connection, with trace routes showing i am staying on the same network as IB (mci) from the DC to IB but response times where in the 96ms range. back at the house on a SBC dsl line 1.5/128kb i was getting 109ms i expected a lot better from the data center - the first real delay is in NYC - go from 6ms (LAX) to 88ms(NYC) in one hop
If you actually trade using the data center connectivity, you should call them and ask them to change your routing. Already being on the east coast, it is silly, unless they have no choice, to route you to LA first to get to Boston. If I read it correctly, this is on an MCI backbone? If so, zero chance they have no choice. nitro
Trace Route For what it's worth, I just did a trace route today ( Saturday at 2:00PM ) from the San Francisco Bay Area to ESignal.Com I got a total of 14 hops. Hop 11 timed out, but the majority were between 11ms and 14ms, and one that went up as high as 28ms. Hop 13 was ESignal via sfj.pnap.net and it was 24ms, 26ms, and 68ms. Hop 14 was DBC.com and it was 23ms, 23ms, and 25ms. Ping Test Minimum: 23ms Maximum: 52ms Avg: 32ms
Yes, I am aware that I am very close to their headquarters in Hayward, but I am told that their servers might not necessarily be at their headquarters there. Hang on. I will run another ping test, this time to ETG in Texas.
True, but woudln't they want to serve their west coast customers from a local center, it would especially make sense when they already have a facility over there. TM Trader
Trace route to ETG: 15 Hops total. Hops 4-10 are between 10ms and 26ms. Hops 7-9 are att.net hops. Hops 10-13 are verio.net These hops show Hop 10 between 22 and 26ms. Hops 11-13 are between 80ms and 86ms, with one at 102ms. Hop 14 in the low 80's. Hop 15 to ETGtrader.com at 84ms, 83ms, and 84ms. Ping Test to ETG: Minimum: 82ms Maximum: 86ms Avg: 83ms
I have yet to use the brand new ETG-TRADER Platform that just rolled-out last week, but from what I understand the servers are in Chicago and Dallas, and run on an OC192 backbone that is 6100 times as fast as a T-1 line.