Does anyone have telus?
Comments
-
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.0.1
2 3 ms 2 ms 1 ms mymodem [192.168.2.1]
3 32 ms 16 ms 15 ms bas1-thornhill40_lo0_SYMP.net.bell.ca [64.230.197.157]
4 17 ms 21 ms 14 ms core1-toronto63_14-0-5_137.net.bell.ca [64.230.138.197]
5 14 ms 15 ms 13 ms core1-toronto63_POS0-0.net.bell.ca [206.108.107.153]
6 16 ms 16 ms 13 ms 64.230.149.215
7 14 ms 12 ms 13 ms 67.69.244.22
8 14 ms 16 ms 14 ms border1-1-dist1-2.tor1.q9.net [69.46.123.206]
9 14 ms 14 ms 13 ms dist1-2-access2-2-100.tor1.q9.net [69.46.121.130]
10 14 ms 12 ms 14 ms ns1-auth.q9.com [216.220.35.20]
Trace complete.
have no clue what all these means xD
and this is wireless -
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\cLappy>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 10.0.0.1
2 7 ms 7 ms 7 ms 73.162.212.1
3 8 ms 8 ms 8 ms te-3-2-ur01.newhaven.ct.hartford.comcast.net [68
.87.159.49]
4 15 ms 14 ms 11 ms be-52-ar01.chartford.ct.hartford.comcast.net [68
.85.162.194]
5 15 ms 15 ms 15 ms pos-1-4-0-0-ar01.needham.ma.boston.comcast.net [
68.85.162.69]
6 25 ms 31 ms 23 ms pos-2-4-0-0-cr01.newyork.ny.ibone.comcast.net [6
8.86.90.61]
7 23 ms 22 ms 25 ms pos-1-3-0-0-pe01.111eighthave.ny.ibone.comcast.n
et [68.86.86.190]
8 20 ms 22 ms 21 ms as577.111eighthave.ny.ibone.comcast.net [173.167
.56.110]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 46 ms 46 ms 48 ms 67.69.244.22
15 57 ms 49 ms 45 ms border1-1-dist1-2.tor1.q9.net [69.46.123.206]
16 48 ms 49 ms 47 ms dist1-2-access2-1-100.tor1.q9.net [69.46.121.134
]
17 53 ms 46 ms 46 ms ns1-auth.q9.com [216.220.35.20]
Trace complete.
C:\Users\cLappy>
Idk what the stars mean, my ping jumps about 20 after the stars. What do they mean? -
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\cLappy>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 10.0.0.1
2 7 ms 7 ms 7 ms 73.162.212.1
3 8 ms 8 ms 8 ms te-3-2-ur01.newhaven.ct.hartford.comcast.net [68
.87.159.49]
4 15 ms 14 ms 11 ms be-52-ar01.chartford.ct.hartford.comcast.net [68
.85.162.194]
5 15 ms 15 ms 15 ms pos-1-4-0-0-ar01.needham.ma.boston.comcast.net [
68.85.162.69]
6 25 ms 31 ms 23 ms pos-2-4-0-0-cr01.newyork.ny.ibone.comcast.net [6
8.86.90.61]
7 23 ms 22 ms 25 ms pos-1-3-0-0-pe01.111eighthave.ny.ibone.comcast.n
et [68.86.86.190]
8 20 ms 22 ms 21 ms as577.111eighthave.ny.ibone.comcast.net [173.167
.56.110]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 46 ms 46 ms 48 ms 67.69.244.22
15 57 ms 49 ms 45 ms border1-1-dist1-2.tor1.q9.net [69.46.123.206]
16 48 ms 49 ms 47 ms dist1-2-access2-1-100.tor1.q9.net [69.46.121.134
]
17 53 ms 46 ms 46 ms ns1-auth.q9.com [216.220.35.20]
Trace complete.
C:\Users\cLappy>
Idk what the stars mean, my ping jumps about 20 after the stars. What do they mean?
As the route goes further, the ping WILL go up.
Looks like you have 46 ping to CrossFire.
The route doesn't look very bad to me, are you spiking or what is the issue? -
As the route goes further, the ping WILL go up.
Looks like you have 46 ping to CrossFire.
The route doesn't look very bad to me, are you spiking or what is the issue?
I do spike a bit, to like 60ish, nothing that bad, I have comcrap.
on a side note, do you know what the stars mean ? -
-
Nah, just a standard wired ethernet connection, no router, could just be normal spikes I guess.
Definitely not an issue with your ISP.
This is a ping test to your ISP router, which handles ALL your internet traffic.
Pinging 73.162.212.1 with 32 bytes of data:
Reply from 73.162.212.1: bytes=32 time=64ms TTL=242
Reply from 73.162.212.1: bytes=32 time=64ms TTL=242
Reply from 73.162.212.1: bytes=32 time=64ms TTL=242
Reply from 73.162.212.1: bytes=32 time=64ms TTL=242
Ping statistics for 73.162.212.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 64ms, Average = 64ms
4 responses all the same, which is PERFECT.
The spikes start here on your route to the server;
Ping statistics for 67.69.244.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 42ms, Average = 39ms
38 min, 42 max, 4 jitter.
FYI, that IP above is in Ontario, CA.. so the issue is with one of the routes.. not you.
-
Definitely not an issue with your ISP.
This is a ping test to your ISP router, which handles ALL your internet traffic.
Pinging 73.162.212.1 with 32 bytes of data:
Reply from 73.162.212.1: bytes=32 time=64ms TTL=242
Reply from 73.162.212.1: bytes=32 time=64ms TTL=242
Reply from 73.162.212.1: bytes=32 time=64ms TTL=242
Reply from 73.162.212.1: bytes=32 time=64ms TTL=242
Ping statistics for 73.162.212.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 64ms, Average = 64ms
4 responses all the same, which is PERFECT.
The spikes start here on your route to the server;
Ping statistics for 67.69.244.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 42ms, Average = 39ms
38 min, 42 max, 4 jitter.
FYI, that IP above is in Ontario, CA.. so the issue is with one of the routes.. not you.
Ah good to know, couldn't I call in to get a different route then if I start to spike again? or is it not that simple ? -
Ah good to know, couldn't I call in to get a different route then if I start to spike again? or is it not that simple ?
You would have to be a millionaire just to ask that of your ISP before they would even think of it as a rational thought. -
Well, I guess I'll just keep spiking then, or change isps if it really bugs me.
Comcast probably has the best route to CrossFire, changing would likely make it worse.
Though, you live about ~500 miles away from Toronto, CA. and get 48-60.. I live 1,800 miles away (3x farther) and get 58 or so... so the routes may be a little messed up at the moment. -
Comcast probably has the best route to CrossFire, changing would likely make it worse.
Though, you live about ~500 miles away from Toronto, CA. and get 48-60.. I live 1,800 miles away (3x farther) and get 58 or so... so the routes may be a little messed up at the moment.
~300 miles (6x further) and my ping has always been 50, are you sure a new isp wouldnt drop it some ? -
Thanks, I'd appreciate it. How about at&t uverse ? or fios, if its in my area yet.
Verizon FiOS in New Jersey > Toronto, Ontario, Canada
Toronto, Canada 74.105.125.249 0.0 22.829 25.285 23.738 23
22 ping lowest, 25 ping max, 24 ping average.
AT&T U-VERSE in New Jersey > Toronto, Ontario, Canada
Toronto, Canada 12.181.128.130 0.0 26.612 35.087 29.559 29
29 ping lowest, 35 ping max, 27 ping avg. -
Verizon FiOS in New Jersey > Toronto, Ontario, Canada
Toronto, Canada 74.105.125.249 0.0 22.829 25.285 23.738 23
22 ping lowest, 25 ping max, 24 ping average.
AT&T U-VERSE in New Jersey > Toronto, Ontario, Canada
Toronto, Canada 12.181.128.130 0.0 26.612 35.087 29.559 29
29 ping lowest, 35 ping max, 27 ping avg.
Thanks, I'd definately look into either of these, effectively half of my ping right now, thanks. -
Thanks, I'd definately look into either of these, effectively half of my ping right now, thanks.
I just tested a Comcast business account to Toronto and got the following:
Toronto, Canada 24.0.105.154 0.0 28.593 29.913 29.17 29
24 ping avg.
Not sure what's with your current routes, Verizon should have a different route aswell as AT&T but you might average the same if they share the same network backbone.. all of them just use different equipment. -
I just tested a Comcast business account to Toronto and got the following:
Toronto, Canada 24.0.105.154 0.0 28.593 29.913 29.17 29
24 ping avg.
Not sure what's with your current routes, Verizon should have a different route aswell as AT&T but you might average the same if they share the same network backbone.. all of them just use different equipment.
Well idk but if you could get it lower it'll be a miracle. If not, I'll switch when as soon as possible. -
Well idk but if you could get it lower it'll be a miracle. If not, I'll switch when as soon as possible.
Click start > then click Run (or do WINKEY + R) and type in CMD
Once at cmd prompt, type in
ping 74.200.6.185
hit enter, once it is done, right click > select all then hit enter to copy and paste it here.
That IP is in the same datacenter as the CrossFire servers, probably less than 5 feet away from it. -
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\cLappy>ping 74.200.6.185
Pinging 74.200.6.185 with 32 bytes of data:
Reply from 74.200.6.185: bytes=32 time=56ms TTL=114
Reply from 74.200.6.185: bytes=32 time=50ms TTL=114
Reply from 74.200.6.185: bytes=32 time=49ms TTL=114
Reply from 74.200.6.185: bytes=32 time=63ms TTL=114
Ping statistics for 74.200.6.185:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 63ms, Average = 55ms
Yea, even worse lol
C:\Users\cLappy> -
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\cLappy>ping 74.200.6.185
Pinging 74.200.6.185 with 32 bytes of data:
Reply from 74.200.6.185: bytes=32 time=56ms TTL=114
Reply from 74.200.6.185: bytes=32 time=50ms TTL=114
Reply from 74.200.6.185: bytes=32 time=49ms TTL=114
Reply from 74.200.6.185: bytes=32 time=63ms TTL=114
Ping statistics for 74.200.6.185:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 63ms, Average = 55ms
Yea, even worse lol
C:\Users\cLappy>
Yup, it's your route.
I get 58 ping every response, that server is under no load whatsoever. -
I live in nj with fios as well ( don't know if Jon was referring to me), my average ping is 38 - 40 in echo. Never have Internet issues or spikes
I have a question though, lately my ping goes down to 28 sometimes. I would join t side of the scrim or ct and then the next side I join my ping would go back to 40 or so. I only get good ping one half (t or ct). Same server with no difference whatsoever -
hammer_bert wrote: »I live in nj with fios as well ( don't know if Jon was referring to me), my average ping is 38 - 40 in echo. Never have Internet issues or spikes
I have a question though, lately my ping goes down to 28 sometimes. I would join t side of the scrim or ct and then the next side I join my ping would go back to 40 or so. I only get good ping one half (t or ct). Same server with no difference whatsoever
No, i was not referring to you.
However, that is rather strange.. I believe it has something to do with the routes.
Years ago, people from NY used to have 11 ping, now they're up to 30's and 40's.
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