Server rentals :: NFOservers.com

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\dusty>ping 208.146.44.38

Pinging 208.146.44.38 with 32 bytes of data:
Reply from 208.146.44.38: bytes=32 time=65ms TTL=54
Reply from 208.146.44.38: bytes=32 time=65ms TTL=54
Reply from 208.146.44.38: bytes=32 time=64ms TTL=54
Reply from 208.146.44.38: bytes=32 time=64ms TTL=54

Ping statistics for 208.146.44.38:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 65ms, Average = 64ms

C:\Users\dusty>tracert 208.146.44.38

Tracing route to 208.146.44.38 over a maximum of 30 hops

1 1 ms 2 ms 1 ms . [192.168.1.254]
2 12 ms 13 ms 10 ms 10.197.144.1
3 10 ms 10 ms 10 ms 209.115.156.129
4 17 ms 14 ms 24 ms 209.115.156.121
5 17 ms 15 ms 15 ms 173.182.206.124
6 57 ms 73 ms 60 ms chcgildtgr00.bb.telus.com [154.11.11.30]
7 55 ms 56 ms 56 ms 206.111.2.57.ptr.us.xo.net [206.111.2.57]
8 57 ms 56 ms 57 ms te0-12-1-0.rar3.chicago-il.us.xo.net [207.88.12.
141]
9 83 ms 66 ms 63 ms te-4-1-0.rar3.denver-co.us.xo.net [207.88.12.22]

10 64 ms 65 ms 71 ms te-3-0-0.rar3.seattle-wa.us.xo.net [207.88.12.81
]
11 63 ms 65 ms 63 ms ae0d1.cir1.seattle7-wa.us.xo.net [207.88.13.145]

12 63 ms 63 ms 63 ms 216.156.100.66.ptr.us.xo.net [216.156.100.66]
13 64 ms 64 ms 66 ms border9.t8-1-bbnet2.sef.pnap.net [63.251.160.83]

14 80 ms 63 ms 63 ms 63.251.175.142
15 77 ms 63 ms 64 ms 208.146.44.38

Trace complete.

C:\Users\dusty>

Get great routes to Chicago, but Seattle has just gone to crap. Not sure if anyone else is on Telus and in Canada. The routes really aren't that good at all.

_________________

It looks like your ISP is funneling you through Chicago right now, possibly even for all destinations in the US. If you live near Chicago, that's not a terrible choice. If you don't, then it may be worth asking them if they are working to improve this.

I'm extremely far from Chicago. I'm in central Alberta, which is more west coast. Getting an ISP to fix routing issues? I just giggled like a little girl .

_________________

Sometimes they do, you'd be surprised -- mainly the small ones, though.

Also, the squeaky wheel, and all that. If they don't get complaints about something, there's very little chance that they'll even consider fixing it.

I never got Shaw to do it, I doubt Telus will either. Last time I had routing issues related to NFO, I believe Internap managed to fix the route so I got the proper ping times. Is this even possible again or no?

_________________

If a problem exists on the outbound from InterNAP to you, they may be able to adjust it. That doesn't appear to be the case here, but I can take a closer look if you submit a support request providing your client IP address.