Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Users\Jeff>ping 184.107.107.176

Pinging 184.107.107.176 with 32 bytes of data:
Reply from 184.107.107.176: bytes=32 time=30ms TTL=52
Reply from 184.107.107.176: bytes=32 time=33ms TTL=52
Reply from 184.107.107.176: bytes=32 time=30ms TTL=52
Reply from 184.107.107.176: bytes=32 time=32ms TTL=52

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

C:\Users\Jeff>pathping 184.107.107.176

Tracing route to 184.107.107.176 over a maximum of 30 hops

0 JeffsBeast [192.168.0.3]
1 142.254.152.145
2 gig2-5.lkgnwilkgn.wi.rr.com [24.160.229.158]
3 tge1-7-0-9.milzwift-ccr01.midwest.rr.com [65.29.45.102]
4 ae-6-0.cr0.chi30.tbone.rr.com [66.109.6.206]
5 ae-2-0.a0.buf00.tbone.rr.com [66.109.1.42]
6 if-17-0.tcore1.CT8-Chicago.as6453.net [63.243.129.21]
7 if-22-2.tcore2.CT8-Chicago.as6453.net [64.86.79.1]
8 if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
9 66.198.96.58
10 te7-4.dr9.mtl.iweb.com [184.107.1.110]
11 72.55.128.44
12 184.107.107.176

Computing statistics for 300 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 JeffsBeast [192.168.0.3]
0/ 100 = 0% |
1 8ms 0/ 100 = 0% 0/ 100 = 0% 142.254.152.145
0/ 100 = 0% |
2 8ms 0/ 100 = 0% 0/ 100 = 0% gig2-5.lkgnwilkgn.wi.rr.com [24.16
0.229.158]
0/ 100 = 0% |
3 13ms 0/ 100 = 0% 0/ 100 = 0% tge1-7-0-9.milzwift-ccr01.midwest.
rr.com [65.29.45.102]
0/ 100 = 0% |
4 15ms 0/ 100 = 0% 0/ 100 = 0% ae-6-0.cr0.chi30.tbone.rr.com [66.
109.6.206]
0/ 100 = 0% |
5 14ms 0/ 100 = 0% 0/ 100 = 0% ae-2-0.a0.buf00.tbone.rr.com [66.1
09.1.42]
0/ 100 = 0% |
6 15ms 0/ 100 = 0% 0/ 100 = 0% if-17-0.tcore1.CT8-Chicago.as6453.
net [63.243.129.21]
0/ 100 = 0% |
7 14ms 0/ 100 = 0% 0/ 100 = 0% if-22-2.tcore2.CT8-Chicago.as6453.
net [64.86.79.1]
0/ 100 = 0% |
8 32ms 0/ 100 = 0% 0/ 100 = 0% if-3-2.tcore1.W6C-Montreal.as6453.
net [66.198.96.45]
0/ 100 = 0% |
9 33ms 99/ 100 = 99% 99/ 100 = 99% 66.198.96.58
0/ 100 = 0% |
10 --- 100/ 100 =100% 100/ 100 =100% te7-4.dr9.mtl.iweb.com [184.107.1.
110]
0/ 100 = 0% |
11 --- 100/ 100 =100% 100/ 100 =100% 72.55.128.44
0/ 100 = 0% |
12 30ms 0/ 100 = 0% 0/ 100 = 0% 184.107.107.176

Trace complete.

this right here is proof that it is not SE's fault, and im sick and tired of hearing people complain about the .3 positional update. Its clear that it is directly related to the clients ISP/location where they live. Ive said it a hundred times, i dont have problems dodging anything EVER, and its not SE's fault for any of the problems people claim to be having. It also seems like a lot of the people who claim to have these problems are located in the same states, which again, proves its not SE's fault