Hey guys, I've recently started having huge ping spikes during game, with pings rising from 50-90 up to 800-3500! I've tried tracert & ping mwomercs.com in CMD, both showing long ping times. Then the problem disappears a minute later, which is too late to survive!
Where should I start?
2
Random Ping Spikes
Started by Chiron, Feb 02 2015 11:07 AM
6 replies to this topic
#1
Posted 02 February 2015 - 11:07 AM
#2
Posted 02 February 2015 - 11:31 AM
chiron, on 02 February 2015 - 11:07 AM, said:
Hey guys, I've recently started having huge ping spikes during game, with pings rising from 50-90 up to 800-3500! I've tried tracert & ping mwomercs.com in CMD, both showing long ping times. Then the problem disappears a minute later, which is too late to survive!
Where should I start?
Where should I start?
When acting up wherr does the trace take you.
Which hop is the problem area
These things can be tricky to get an ISP to do somthing about
#3
Posted 02 February 2015 - 04:55 PM
chiron, on 02 February 2015 - 11:07 AM, said:
Hey guys, I've recently started having huge ping spikes during game, with pings rising from 50-90 up to 800-3500! I've tried tracert & ping mwomercs.com in CMD, both showing long ping times. Then the problem disappears a minute later, which is too late to survive!
Where should I start?
Where should I start?
BEST place to start is to update your Network Drivers. Go to iObit website (or other web sites that mirror it's programs) and download a free program called "Driver Booster". Install and run it, update your drivers, and viola.. hopefully that would help you. If not, it's most likely your ISP to blame, power-lines moving back and forth with ice on them and wind blowing or something.. ready to snap and leave you without a connection at all.. happy thoughts 2u.
Added: ...oh, and you might want to look into trying a new modem/router/cable modem, etc. as a troubleshooting effort, including checking your lan cables, if you are on wired lan.
Edited by Jesus DIED for me, 02 February 2015 - 04:57 PM.
#4
Posted 03 February 2015 - 04:19 AM
from charlottesville, VA
1 8 ms 3 ms 5 ms dlinkrouter.PK5001Z [192.168.5.1]
2 7 ms 1 ms 1 ms PK5001Z.PK5001Z [192.168.0.1]
3 20 ms 31 ms 20 ms va-184-5-152-1.dhcp.embarqhsd.net [184.5.152.1]
4 26 ms 21 ms 20 ms va-71-2-174-45.sta.embarqhsd.net [71.2.174.45]
5 36 ms 34 ms 35 ms 208-110-248-237.centurylink.net [208.110.248.237
]
6 315 ms 330 ms 325 ms dcx2-edge-01.inet.qwest.net [65.113.64.197]
7 189 ms 340 ms 334 ms dcp-brdr-03.inet.qwest.net [205.171.251.6]
8 341 ms 342 ms 368 ms ae5.edge1.Washington4.Level3.net [4.68.63.81]
9 362 ms 232 ms 358 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
10 38 ms 39 ms 43 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
11 78 ms * 421 ms level3.as3356.nj.us [178.32.135.18]
12 402 ms 408 ms 265 ms bhs-g1-6k.qc.ca [198.27.73.205]
13 66 ms 63 ms 62 ms 198.27.73.231
14 416 ms 373 ms 421 ms mwomercs.com [192.99.109.192]
Trace complete.
C:\Users\karl>ping mwomercs.com
Pinging mwomercs.com [192.99.109.192] with 32 bytes of data:
Reply from 192.99.109.192: bytes=32 time=471ms TTL=52
Reply from 192.99.109.192: bytes=32 time=60ms TTL=52
Reply from 192.99.109.192: bytes=32 time=477ms TTL=52
Reply from 192.99.109.192: bytes=32 time=467ms TTL=52
Ping statistics for 192.99.109.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 60ms, Maximum = 477ms, Average = 368ms
1 8 ms 3 ms 5 ms dlinkrouter.PK5001Z [192.168.5.1]
2 7 ms 1 ms 1 ms PK5001Z.PK5001Z [192.168.0.1]
3 20 ms 31 ms 20 ms va-184-5-152-1.dhcp.embarqhsd.net [184.5.152.1]
4 26 ms 21 ms 20 ms va-71-2-174-45.sta.embarqhsd.net [71.2.174.45]
5 36 ms 34 ms 35 ms 208-110-248-237.centurylink.net [208.110.248.237
]
6 315 ms 330 ms 325 ms dcx2-edge-01.inet.qwest.net [65.113.64.197]
7 189 ms 340 ms 334 ms dcp-brdr-03.inet.qwest.net [205.171.251.6]
8 341 ms 342 ms 368 ms ae5.edge1.Washington4.Level3.net [4.68.63.81]
9 362 ms 232 ms 358 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
10 38 ms 39 ms 43 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
11 78 ms * 421 ms level3.as3356.nj.us [178.32.135.18]
12 402 ms 408 ms 265 ms bhs-g1-6k.qc.ca [198.27.73.205]
13 66 ms 63 ms 62 ms 198.27.73.231
14 416 ms 373 ms 421 ms mwomercs.com [192.99.109.192]
Trace complete.
C:\Users\karl>ping mwomercs.com
Pinging mwomercs.com [192.99.109.192] with 32 bytes of data:
Reply from 192.99.109.192: bytes=32 time=471ms TTL=52
Reply from 192.99.109.192: bytes=32 time=60ms TTL=52
Reply from 192.99.109.192: bytes=32 time=477ms TTL=52
Reply from 192.99.109.192: bytes=32 time=467ms TTL=52
Ping statistics for 192.99.109.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 60ms, Maximum = 477ms, Average = 368ms
#5
Posted 03 February 2015 - 04:24 PM
chiron, on 03 February 2015 - 04:19 AM, said:
from charlottesville, VA
1 8 ms 3 ms 5 ms dlinkrouter.PK5001Z [192.168.5.1]
2 7 ms 1 ms 1 ms PK5001Z.PK5001Z [192.168.0.1]
3 20 ms 31 ms 20 ms va-184-5-152-1.dhcp.embarqhsd.net [184.5.152.1]
4 26 ms 21 ms 20 ms va-71-2-174-45.sta.embarqhsd.net [71.2.174.45]
5 36 ms 34 ms 35 ms 208-110-248-237.centurylink.net [208.110.248.237
]
6 315 ms 330 ms 325 ms dcx2-edge-01.inet.qwest.net [65.113.64.197]
7 189 ms 340 ms 334 ms dcp-brdr-03.inet.qwest.net [205.171.251.6]
8 341 ms 342 ms 368 ms ae5.edge1.Washington4.Level3.net [4.68.63.81]
9 362 ms 232 ms 358 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
10 38 ms 39 ms 43 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
11 78 ms * 421 ms level3.as3356.nj.us [178.32.135.18]
12 402 ms 408 ms 265 ms bhs-g1-6k.qc.ca [198.27.73.205]
13 66 ms 63 ms 62 ms 198.27.73.231
14 416 ms 373 ms 421 ms mwomercs.com [192.99.109.192]
Trace complete.
C:\Users\karl>ping mwomercs.com
Pinging mwomercs.com [192.99.109.192] with 32 bytes of data:
Reply from 192.99.109.192: bytes=32 time=471ms TTL=52
Reply from 192.99.109.192: bytes=32 time=60ms TTL=52
Reply from 192.99.109.192: bytes=32 time=477ms TTL=52
Reply from 192.99.109.192: bytes=32 time=467ms TTL=52
Ping statistics for 192.99.109.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 60ms, Maximum = 477ms, Average = 368ms
1 8 ms 3 ms 5 ms dlinkrouter.PK5001Z [192.168.5.1]
2 7 ms 1 ms 1 ms PK5001Z.PK5001Z [192.168.0.1]
3 20 ms 31 ms 20 ms va-184-5-152-1.dhcp.embarqhsd.net [184.5.152.1]
4 26 ms 21 ms 20 ms va-71-2-174-45.sta.embarqhsd.net [71.2.174.45]
5 36 ms 34 ms 35 ms 208-110-248-237.centurylink.net [208.110.248.237
]
6 315 ms 330 ms 325 ms dcx2-edge-01.inet.qwest.net [65.113.64.197]
7 189 ms 340 ms 334 ms dcp-brdr-03.inet.qwest.net [205.171.251.6]
8 341 ms 342 ms 368 ms ae5.edge1.Washington4.Level3.net [4.68.63.81]
9 362 ms 232 ms 358 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
10 38 ms 39 ms 43 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
11 78 ms * 421 ms level3.as3356.nj.us [178.32.135.18]
12 402 ms 408 ms 265 ms bhs-g1-6k.qc.ca [198.27.73.205]
13 66 ms 63 ms 62 ms 198.27.73.231
14 416 ms 373 ms 421 ms mwomercs.com [192.99.109.192]
Trace complete.
C:\Users\karl>ping mwomercs.com
Pinging mwomercs.com [192.99.109.192] with 32 bytes of data:
Reply from 192.99.109.192: bytes=32 time=471ms TTL=52
Reply from 192.99.109.192: bytes=32 time=60ms TTL=52
Reply from 192.99.109.192: bytes=32 time=477ms TTL=52
Reply from 192.99.109.192: bytes=32 time=467ms TTL=52
Ping statistics for 192.99.109.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 60ms, Maximum = 477ms, Average = 368ms
Looks like qwest servers is where the problem starts for you.
Try this if you are brave enough..
https://developers.g...-dns/docs/using
#6
Posted 03 February 2015 - 05:31 PM
O.o. You change switch your DNS? without incurring issues from your ISP?
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users