Hi, I'm located in Miami and just out of curiosity I ran traceroute to see where the IQFeed server (that I'm connected to) is located. Seems like Denver. IQFeed was never marketed as a low latency feed, though I'm still surprised that it's not cheaper (and faster!) to have a server farm in each large geographic area closer to the end clients. Any comments? ;)

...
4: xe-5-0-0.edge2.Miami1.Level3.net 11.068ms asymm 9
5: ae-31-51.ebr1.Miami1.Level3.net 21.953ms asymm 8
6: ae-2-2.ebr1.Dallas1.Level3.net 40.906ms asymm 13
7: ae-81-81.csw3.Dallas1.Level3.net 41.991ms asymm 12
8: ae-72-72.ebr2.Dallas1.Level3.net 45.846ms asymm 13
9: ae-2-2.ebr1.Denver1.Level3.net 56.002ms asymm 14
10: ae-12-51.car2.Denver1.Level3.net 55.967ms asymm 15
11: DTN.car2.Denver1.Level3.net 66.972ms asymm 16
12: 66.112.152.58 66.975ms asymm 18
13: 66.112.156.112 67.103ms !H

---

"I hear and I forget. I see and I remember. I do and I understand."
-- Confucius

Given that stock exchange data has to get to Denver from New York before it gets to me, this puts the total latency at ~ 120 ms...

---

"I hear and I forget. I see and I remember. I do and I understand."
-- Confucius

Our servers are located in Omaha and Bellevue Nebraska.

Using a centralized location (most traffic will run through either Chicago, Denver, or Dallas) in the US allows us good speeds to most users while maintaining low costs.

The latency from us to the exchange is minimal. We have dedicated lines to most exchanges/data providers. This means that the latency from us to your machine (via the general internet) is the significant portion of the connection in terms of latency.