Hi. I'm not sure if this post belongs in this forum or the PC Gaming forum, so my apologies if it's misplaced.
I moved into my current house in mid September, at which point my roommates and I got Centurylink service installed. I was sitting at 56 ms on the dot for about a month and a half, bar any server side issues with the game. However, a few weeks ago I started having major issues with latency. Sometimes my ping is fine sitting at 56 ms like it always has, but fairly frequently it will spike to 180-200 ms in the middle of a game and stay there until I reset the router. Resetting the router fixes the problem for about 5 minutes, then it spikes again and stagnates around 200 ms. Tonight was atrocious -- I hovered at 500 ms for an entire game of league of legends, spiking up to 800 ms, obviously making the game 100% unplayable.
I've called Centurylink support 3 times so far, which has been completely useless. They tell me to reset the router, and when I tell them that that only solves the problem temporarily they offer to send a technician to my house for $85. No thanks.
I'm using a wireless connection, as running an ethernet cord from my roommate's room to my room is not feasible. I've heard Centurylink is particularly inefficient in their server routing, and I'm more than ready to switch ISPs if that will fix the problem.
However, I'm certainly no networking guru and I want to do everything I can to fix any issue being caused by myself before blaming the ISP. These are my tracert results for a NA League of Legends server:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Luke>ping battle.net
Pinging battle.net [12.129.242.30] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 12.129.242.30:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Luke>tracert 216.133.234.95
Tracing route to 216.133.234.95 over a maximum of 30 hops
1 1 ms <1 ms <1 ms 192.168.1.1
2 1 ms 2 ms 2 ms 192.168.0.1
3 24 ms 24 ms 23 ms tukw-dsl-gw62-254.tukw.qwest.net [63.231.10.254]
4 23 ms 32 ms 23 ms tukw-agw1.inet.qwest.net [71.217.185.233]
5 119 ms 120 ms 120 ms sea-brdr-02.inet.qwest.net [67.14.41.18]
6 114 ms 117 ms 117 ms 63.146.27.70
7 172 ms 170 ms 174 ms 0.xe-3-0-3.XL3.LAX15.ALTER.NET [152.63.114.66]
8 338 ms 340 ms 338 ms POS6-0-0.GW3.LAX15.ALTER.NET [152.63.112.105]
9 271 ms 278 ms 293 ms internapGIGE-gw.customer.alter.net [157.130.236.
110]
10 434 ms 469 ms 476 ms border1.po1-20g-bbnet1.lax010.pnap.net [216.52.2
55.13]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
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.
Trace complete.
C:\Users\Luke>tracert 216.133.234.95
Tracing route to 216.133.234.95 over a maximum of 30 hops
1 2 ms 3 ms 1 ms 192.168.0.1
2 23 ms 24 ms 23 ms tukw-dsl-gw62-254.tukw.qwest.net [63.231.10.254]
3 23 ms 24 ms 23 ms tukw-agw1.inet.qwest.net [71.217.185.233]
4 110 ms 108 ms 108 ms sea-brdr-02.inet.qwest.net [67.14.41.18]
5 147 ms 100 ms 99 ms 63.146.27.70
6 117 ms 114 ms 114 ms 0.xe-3-0-3.XL3.LAX15.ALTER.NET [152.63.114.66]
7 289 ms 295 ms 281 ms POS6-0-0.GW3.LAX15.ALTER.NET [152.63.112.105]
8 277 ms 438 ms 432 ms internapGIGE-gw.customer.alter.net [157.130.236.
110]
9 232 ms 226 ms 222 ms border1.po1-20g-bbnet1.lax010.pnap.net [216.52.2
55.13]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
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.
Trace complete.
Thanks for any help
I moved into my current house in mid September, at which point my roommates and I got Centurylink service installed. I was sitting at 56 ms on the dot for about a month and a half, bar any server side issues with the game. However, a few weeks ago I started having major issues with latency. Sometimes my ping is fine sitting at 56 ms like it always has, but fairly frequently it will spike to 180-200 ms in the middle of a game and stay there until I reset the router. Resetting the router fixes the problem for about 5 minutes, then it spikes again and stagnates around 200 ms. Tonight was atrocious -- I hovered at 500 ms for an entire game of league of legends, spiking up to 800 ms, obviously making the game 100% unplayable.
I've called Centurylink support 3 times so far, which has been completely useless. They tell me to reset the router, and when I tell them that that only solves the problem temporarily they offer to send a technician to my house for $85. No thanks.
I'm using a wireless connection, as running an ethernet cord from my roommate's room to my room is not feasible. I've heard Centurylink is particularly inefficient in their server routing, and I'm more than ready to switch ISPs if that will fix the problem.
However, I'm certainly no networking guru and I want to do everything I can to fix any issue being caused by myself before blaming the ISP. These are my tracert results for a NA League of Legends server:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Luke>ping battle.net
Pinging battle.net [12.129.242.30] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 12.129.242.30:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Luke>tracert 216.133.234.95
Tracing route to 216.133.234.95 over a maximum of 30 hops
1 1 ms <1 ms <1 ms 192.168.1.1
2 1 ms 2 ms 2 ms 192.168.0.1
3 24 ms 24 ms 23 ms tukw-dsl-gw62-254.tukw.qwest.net [63.231.10.254]
4 23 ms 32 ms 23 ms tukw-agw1.inet.qwest.net [71.217.185.233]
5 119 ms 120 ms 120 ms sea-brdr-02.inet.qwest.net [67.14.41.18]
6 114 ms 117 ms 117 ms 63.146.27.70
7 172 ms 170 ms 174 ms 0.xe-3-0-3.XL3.LAX15.ALTER.NET [152.63.114.66]
8 338 ms 340 ms 338 ms POS6-0-0.GW3.LAX15.ALTER.NET [152.63.112.105]
9 271 ms 278 ms 293 ms internapGIGE-gw.customer.alter.net [157.130.236.
110]
10 434 ms 469 ms 476 ms border1.po1-20g-bbnet1.lax010.pnap.net [216.52.2
55.13]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
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.
Trace complete.
C:\Users\Luke>tracert 216.133.234.95
Tracing route to 216.133.234.95 over a maximum of 30 hops
1 2 ms 3 ms 1 ms 192.168.0.1
2 23 ms 24 ms 23 ms tukw-dsl-gw62-254.tukw.qwest.net [63.231.10.254]
3 23 ms 24 ms 23 ms tukw-agw1.inet.qwest.net [71.217.185.233]
4 110 ms 108 ms 108 ms sea-brdr-02.inet.qwest.net [67.14.41.18]
5 147 ms 100 ms 99 ms 63.146.27.70
6 117 ms 114 ms 114 ms 0.xe-3-0-3.XL3.LAX15.ALTER.NET [152.63.114.66]
7 289 ms 295 ms 281 ms POS6-0-0.GW3.LAX15.ALTER.NET [152.63.112.105]
8 277 ms 438 ms 432 ms internapGIGE-gw.customer.alter.net [157.130.236.
110]
9 232 ms 226 ms 222 ms border1.po1-20g-bbnet1.lax010.pnap.net [216.52.2
55.13]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
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.
Trace complete.
Thanks for any help