(edited by Insanelogic.3250)
Showing Posts For Insanelogic.3250:
This issue only started for my when this patch hit, was playing last night with no issues.
Tracing route to 64.25.38.245 over a maximum of 30 hops
1 13 ms 7 ms 9 ms 192.168.0.1
2 18 ms 29 ms 19 ms 7.11.163.25
3 26 ms 29 ms 21 ms 209.148.245.157
4 25 ms 29 ms 41 ms 69.63.248.173
5 29 ms 27 ms 29 ms 69.63.248.181
6 * * * Request timed out.
7 86 ms 83 ms 90 ms xe-0-1-0.er2.iad10.us.above.net [64.124.196.213]
8 48 ms 54 ms 46 ms above-uu.iad10.us.above.net [64.125.13.174]
9 * * * Request timed out.
10 65 ms 71 ms 68 ms GigabitEthernet7-0-0.GW12.DFW9.ALTER.NET [152.63
.97.98]
11 70 ms 69 ms 69 ms 65.205.119.210
12 * 119 ms 137 ms 64.25.32.9
13 * 122 ms * 64.25.32.26
14 * 129 ms * 64.25.32.82
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
I have also been having this issue with latency around the 300ms mark. ISP is also Rogers so I don’t know what to think….