thinking of purchasing but network routing is messed up to s

[hlds_noob]

Code: Select all

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    0 |  152 |  152 |    0 |    0 |    0 |    0 |
|                            50.161.180.1 -    0 |  152 |  152 |    0 |   13 |  140 |   16 |
|xe-7-0-2-32767-sur02.sacramento.ca.ccal.comcast.net -    0 |  152 |  152 |    0 |   12 |   62 |   16 |
|xe-1-0-0-0-ar04.fresno.ca.fresno.comcast.net -    0 |  152 |  152 |    0 |   22 |  109 |   46 |
|he-1-2-0-0-10-cr01.losangeles.ca.ibone.comcast.net -    1 |  151 |  150 |   15 |   24 |   46 |   31 |
|            xe-0-2-0.lax20.ip4.tinet.net -    1 |  151 |  150 |   15 |   27 |   93 |   31 |
|           xe-11-1-2.sea23.ip4.tinet.net -    1 |  151 |  150 |   46 |   56 |   94 |   62 |
|[color=#BF0040][/color]               internap-gw.ip4.tinet.net -    0 |  151 |  151 |   31 |   44 |   63 |   47 |
|        border8.t8-1-bbnet2.sef.pnap.net -    0 |  151 |  151 |   31 |   52 |  265 |   46 |
|c-66-150-164-26.internap-seattle.nfoservers.com -    1 |  151 |  150 |   31 |   43 |   62 |   47 |
|________________________________________________|______|______|______|______|_____

[Edge100x]

It looks like Comcast is sending you down through LA right now -- is that what you're referring to here?

I'm not sure if there's anything that we can do about that on our end, because trying to influence the choices that ISPs make is a tricky business, but if you contact us directly, I can take a closer look.

[hlds_noob]

Well that 3rd from the last hop "internap-gw.ip4.tinet.net" is sending me from Seattle to NewYork and then back to Seattle again. Hope you had a good thanksgiving John.

[Edge100x]

There's no New York in your trace . It appears to take Sacramento->Fresno->Los Angeles->Seattle, based on the reverse DNS entries, and the latencies correspond to what I would expect for the distances along that path.

[hlds_noob]

There's no New York in your trace . It appears to take Sacramento->Fresno->Los Angeles->Seattle, based on the reverse DNS entries, and the latencies correspond to what I would expect for the distances along that path.

Your not seeing the New York hop in my trace because its just the DNS and not the IP. I assure you that DNS resolves to an IP address in New York, according to domain tools.

http://whois.domaintools.com/216.221.159.198 internap-gw.ip4.tinet.net

[Edge100x]

hlds_noob, GeoIP tools guess at the locations of devices hosting IP addresses by using a variety of sources that do not often apply to networking hardware, most notably what shipping addresses people enter when they order from similar IPs. In this case, we know for a fact that 216.221.159.198 corresponds to an Internap router that is in Seattle, so the tool you are using is guessing wrong.

As I suggested in my previous reply, it's easy to tell when the physical location is wildly incorrect, because the latencies will not correspond. The trip from Seattle to NYC takes about 65ms at minimum, because of the distance involved (signals can only travel so fast). Here, the previous hop reads 46ms, and this hop reads 31ms, for a difference of -15ms. With that delta, it is not possible for the hops to be in cities that far apart.

[hlds_noob]

I completely understand now, thanks for clearing that up.