Ping Issues
Comments
-
Can you run a traceroute to;
ns1-auth.q9.com
Go to start > run (or hit WINKEY + R) and type in CMD, on the cmd line type in;
tracert ns1-auth.q9.com
hit enter, right click > select all (hit enter to copy)
then paste here.
I've also been getting sketchy ping
and if you're lucky enough hopefully you can get Jon to help you -
I dont know if jon will see this but anyways.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\User>tracert ns1-auth.q9.com
Tracing route to ns1-auth.q9.com [216.220.35.20]
over a maximum of 30 hops:
1 12 ms 13 ms 14 ms User-PC [0.0.0.0]
2 12 ms 8 ms 10 ms User-PC [0.0.0.0]
3 11 ms 11 ms 13 ms 24.102.5.65
4 10 ms 12 ms 11 ms core-main.mountaincable.net [24.215.3.185]
5 19 ms 11 ms 11 ms 66.163.78.97
6 15 ms 17 ms 16 ms rc1sh-ge9-0-3.mt.shawcable.net [66.163.66.34]
7 14 ms 17 ms 11 ms rx0sh-q9-networks.mt.bigpipeinc.com [66.244.223.
202]
8 14 ms 12 ms 17 ms border1-2-dist1-2.tor1.q9.net [69.46.123.218]
9 19 ms 13 ms 14 ms dist1-2-access2-1-100.tor1.q9.net [69.46.121.134
]
10 15 ms 14 ms 12 ms ns1-auth.q9.com [216.220.35.20]
Trace complete.
C:\Users\User> -
We need to find what route the issue resides in then contact the network manager for that route.
Both of you (flock and Folsom) run a traceroute by doing the following:
Hit the Windows key + R and type in "CMD" (without quotes)
When you're in the black window, type in;
tracert ns1-auth.q9.com
Hit enter, when it's done (should take 1 min or so) right click > select all then hit enter (enter is to copy, weird yes.. blame it on microsoft)
edit:
lol flock, posted right before i posted mine.. o.0 -
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Donovan>tracet ns1-auth.q9.com
'tracet' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Donovan>tracert ns1-auth.q9.com
Tracing route to ns1-auth.q9.com [216.220.35.20]
over a maximum of 30 hops:
1 * * * Request timed out.
2 * 23 ms 24 ms rc1we-tge0-8-1-0-6.ed.shawcable.net [64.59.189.3
4]
3 44 ms 38 ms 44 ms 66.163.78.66
4 66 ms 68 ms 66 ms rc1sh-pos15-0.mt.shawcable.net [66.163.76.221]
5 * 69 ms 64 ms rc1sh-ge9-0-3.mt.shawcable.net [66.163.66.34]
6 62 ms 64 ms 71 ms rx0sh-q9-networks.mt.bigpipeinc.com [66.244.223.
202]
7 70 ms 68 ms 70 ms border1-2-dist1-1.tor1.q9.net [69.46.123.214]
8 71 ms 66 ms 69 ms dist1-1-access2-2-100.tor1.q9.net [69.46.121.78]
9 65 ms 65 ms 65 ms ns1-auth.q9.com [216.220.35.20]
Trace complete.
C:\Users\Donovan> -
I'm getting some latency issues too,
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\aWpedz>tracert ns1-auth.q9.com
Tracing route to ns1-auth.q9.com [216.220.35.20]
over a maximum of 30 hops:
1 2 ms 3 ms <1 ms 192.168.1.254
2 23 ms 24 ms 22 ms 10.144.16.1
3 27 ms 41 ms 26 ms 208.181.241.134
4 27 ms 31 ms 26 ms 209.121.72.254
5 103 ms 26 ms 27 ms 154.11.22.114
6 73 ms 73 ms 72 ms toroonxndr02.bb.telus.com [154.11.6.19]
7 80 ms 75 ms 75 ms Q9Networks.toroonxngr00.bb.telus.com [154.11.3.7
8]
8 * 73 ms 79 ms border1-2-dist1-1.tor1.q9.net [69.46.123.214]
9 77 ms 76 ms 78 ms dist1-1-access2-1-100.tor1.q9.net [69.46.121.74]
10 77 ms 77 ms 75 ms ns1-auth.q9.com [216.220.35.20]
Trace complete. -
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Donovan>tracert 74.200.6.185
Tracing route to 185.6.200-74.q9.net [74.200.6.185]
over a maximum of 30 hops:
1 * * * Request timed out.
2 23 ms 33 ms 39 ms rc1we-tge0-8-1-0-6.ed.shawcable.net [64.59.189.3
4]
3 * 44 ms 46 ms 66.163.78.138
4 64 ms 60 ms 72 ms rc1sh-pos13-0.mt.shawcable.net [66.163.76.73]
5 67 ms 61 ms 63 ms ra2fs-tge1-3.mt.shawcable.net [66.163.66.138]
6 84 ms 64 ms 76 ms h66-244-255-66.bigpipeinc.com [66.244.255.66]
7 73 ms 70 ms 98 ms 142.46.128.242
8 63 ms 70 ms 72 ms 142.46.2.78
9 * 68 ms 70 ms border1-1-dist1-1.brm1.q9.net [74.200.14.210]
10 71 ms 66 ms 93 ms dist1-1-access1-1-896.brm1.q9.net [74.200.10.66]
11 67 ms 67 ms 70 ms 185.6.200-74.q9.net [74.200.6.185]
Trace complete.
C:\Users\Donovan> -
Same problem on other servers.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\User>tracert 74.200.6.185
Tracing route to 185.6.200-74.q9.net [74.200.6.185]
over a maximum of 30 hops:
1 9 ms 16 ms 10 ms User-PC [0.0.0.0]
2 10 ms 28 ms 8 ms User-PC [0.0.0.0]
3 10 ms 9 ms 9 ms 24.102.5.65
4 8 ms 12 ms 10 ms core-main.mountaincable.net [24.215.3.185]
5 16 ms 14 ms 12 ms 66.163.78.97
6 22 ms 11 ms 10 ms ra2fs-tge1-3.mt.shawcable.net [66.163.66.138]
7 11 ms 11 ms 10 ms h66-244-255-66.bigpipeinc.com [66.244.255.66]
8 13 ms 13 ms 15 ms 142.46.128.242
9 14 ms 12 ms 17 ms 142.46.2.78
10 18 ms 17 ms 18 ms border1-1-dist1-2.brm1.q9.net [74.200.14.206]
11 18 ms 18 ms 15 ms dist1-2-access1-2-896.brm1.q9.net [74.200.10.122
]
12 18 ms 18 ms 15 ms 185.6.200-74.q9.net [74.200.6.185]
Trace complete.
C:\Users\User> -
I just reported the issue to the network managers in Telus/ShawCable, apparently they are experiencing high packet loss and ping issues due to an attack on their network.
They didn't say when it will be fixed but I forwarded them your trace routes.
Good day. -
I just reported the issue to the network managers in Telus/ShawCable, apparently they are experiencing high packet loss and ping issues due to an attack on their network.
They didn't say when it will be fixed but I forwarded them your trace routes.
Good day.
Thanks Jon! -
I just reported the issue to the network managers in Telus/ShawCable, apparently they are experiencing high packet loss and ping issues due to an attack on their network.
They didn't say when it will be fixed but I forwarded them your trace routes.
Good day.
FrostGaming represent. Thank you so much Jon. -
I just reported the issue to the network managers in Telus/ShawCable, apparently they are experiencing high packet loss and ping issues due to an attack on their network.
They didn't say when it will be fixed but I forwarded them your trace routes.
Good day.
You are actually ****ing awesome. -
Folsom I have telus I'm also in Edmonton and I'm getting spikes from 40-700.
I have two houses both with telus and they are both getting these spikes. I'm thinking somethings facked around the whole city because some of my friends are also complaining. -
-
aWptitties wrote: »No one cares, you're trolling on an alt.
(C) Copyright 1985-2001 Microsoft Corp.
\Documents and Settings\IwLyAn>tracert ns1-auth.q9.com
Tracing route to ns1-auth.q9.com [216.220.35.20]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 16 ms 16 ms 15 ms 92.83.128.254
3 23 ms 39 ms 41 ms 10.0.226.125
4 105 ms 109 ms 94 ms 10.0.226.145
5 81 ms 69 ms 83 ms 10.0.226.177
6 94 ms 102 ms 98 ms 10.0.240.213
7 83 ms 78 ms 79 ms 10.0.200.2
8 115 ms 125 ms 121 ms xe-0-3-0.franco31.fra.seabone.net [89.221.34.37]
9 88 ms 76 ms 81 ms ix-3-3-0-0.tcore1.FR0-Frankfurt.as6453.net [195.
219.180.37]
10 180 ms 168 ms 180 ms if-3-2.tcore1.PVU-Paris.as6453.net [80.231.153.5
3]
11 187 ms 197 ms 188 ms if-2-0-0.mcore3.MTT-Montreal.as6453.net [80.231.
153.18]
12 202 ms 219 ms 184 ms if-6-1898.tcore1.MTT-Montreal.as6453.net [64.86.
31.33]
13 220 ms 247 ms 225 ms if-5-0-0.mcore3.TTT-Scarborough.as6453.net [64.8
6.31.22]
14 245 ms 265 ms 240 ms if-1-0-0.core4.TNK-Toronto.as6453.net [63.243.17
2.1]
15 206 ms 211 ms 206 ms 209.58.94.50
16 192 ms 196 ms 188 ms border1-1-dist1-2.tor1.q9.net [69.46.123.206]
17 226 ms 224 ms 243 ms dist1-2-access2-2-100.tor1.q9.net [69.46.121.130
]
18 186 ms 200 ms 187 ms ns1-auth.q9.com [216.220.35.20]
Trace complete.
Categories
- All Categories
- Z8Games
- 1 Z8 Forum Discussion & Suggestions
- 15 Z8Games Announcements
- Rules & Conduct
- 2.6K CrossFire
- 745 CrossFire Announcements
- 742 Previous Announcements
- 2 Previous Patch Notes
- 333 Community
- 12 Modes
- 400 Suggestions
- 16 Clan Discussion and Recruitment
- 89 CF Competitive Forum
- 1 CFCL
- 17 Looking for a Team?
- 536 CrossFire Support
- 9 Suggestion
- 16 CrossFire Guides
- 38 CrossFire Off Topic