High latency - centurylink! Mainthread

Xens-heartseeker · October 22, 2019, 2:32am

Same here 400 ping serer and world… very annoying started about 2 hours ago.

Decayer-anetheron · October 22, 2019, 2:55am

Here’s what I’ve been experiencing for the last 2+ hrs…same 99% loss rate at the ae-1 level.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - %	Sent	Recv	Best	Avrg	Wrst	Last
modem.Home - 0	976	976	0	0	26	0
184-96-48-254 . hlrn . qwest. net - 0	976	976	2	6	34	9
63-225-124-105.hlrn . qwest. net - 0	976	976	1	5	45	3
dvr3-brdr-01 .inet . qwest. net - 0	976	976	2	5	45	8
63-235-41-90. dia. static . qwest . net - 0	976	976	2	4	332	2
ae-1-3508.ear7. Chicago2.Level3. net - 99	197	2	27	27	28	27
BLIZZARD-EN .ear7. Chicago2 .Level3 .net - 1	968	966	74	217	632	218
ae1-br02-eqch2 .as57976.net - 1	972	971	70	216	333	218
be2-pe2-eqch2 .as57976.net - 1	960	956	74	212	251	217
24.105.62.129 - 1	968	966	71	214	250	217
________________________________________________	______	______	______	______	______	______

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Bins-bleeding-hollow · October 22, 2019, 3:30am

Anyone that was experiencing latency tonight still have 200ms+ currently or has it gone down?

Nhí-illidan · October 22, 2019, 3:57am

I finally broke down and purchased ExpressVPN. I’ve found for me Chicago and Denver locations offered the lowest latency - under 100ms (i’m normally 13ms when Level3 is not acting up).

Bins-bleeding-hollow · October 22, 2019, 4:01am

If you dont go through the VPN whats your latency now?

Caterpepi · October 22, 2019, 6:33pm

There’s been some changes made last night. Please let us know if the issue persists tonight!

If the issue continues tonight, could new WinMTR tests be provided? We’d like to check if the Chicago Level 3 continues to experience issues.

Thank you all for your reports!

Bins-bleeding-hollow · October 22, 2019, 8:38pm

Hoping all is good tonight, if not I’ll post some new traceroutes. Appreciate the update!

Zaxxkong-emerald-dream · October 22, 2019, 9:45pm

Problems started around the time the servers came back up this morning and continuing now as well…

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - %	Sent	Recv	Best	Avrg	Wrst	Last
modem.domain - 0	316	316	2	47	1055	4
desm-dsl-gw27.desm.qwest.ne t - 1	312	311	4	47	1467	6
75.160.210.209 - 0	316	316	4	48	1068	5
cer-priv-01.inet.qwest.ne t - 1	308	306	12	46	1412	14
lag-53.ear5.Chicago2.Level3.ne t - 96	66	3	0	457	1316	15
No response from host - 100	63	0	0	0	0	0
BLIZZARD-EN.ear3.LosAngeles1.Level3.ne t - 1	312	311	60	94	1386	77
ae1-br01-eqla1.as57976.ne t - 0	316	316	63	118	1116	121
et-0-0-2-br01-swlv10.as57976.ne t - 1	312	311	62	103	948	66
137.221.65.133 - 0	315	315	63	121	2112	65
be1-pe2-eqch2.as57976.ne t - 0	316	316	63	109	1116	65
chi-eqch2-ia-bons-04.as57976.ne t - 0	316	316	63	109	1115	65
24.105.62.129 - 0	316	316	63	109	1116	65
________________________________________________	______	______	______	______	______	______

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Caterpepi · October 22, 2019, 9:51pm

Thanks, Zaxxkong! The WinMTR test is looking a bit different from the level 3 Chicago issue that we’ve been tracking. I’m more concerned with the home network due to the average latency being 47ms here:

This should generally be under 10ms for a wireless connection, and around 1ms for a wired connection. Could you try powercycling the home network to see if it may help with the latency? If wireless, would you be able to try a wired connection?

Roag-hellscream · October 22, 2019, 11:02pm

Not sure what everyone else is seeing but all I noticed is that they’re now routing traffic through LA instead of the level3 backbone that was originally causing issues.

Tracing route to 24.105.62.129 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  Firewall [192.168.117.1]
  2     4 ms     4 ms     4 ms  blng-dsl-gw16.blng.qwest.net [67.42.227.16]
  3     5 ms     4 ms     4 ms  blng-agw1.inet.qwest.net [65.100.79.121]
  4    16 ms    16 ms    16 ms  dvr3-brdr-01.inet.qwest.net [208.168.152.134]
  5     *        *       16 ms  63-235-41-90.dia.static.qwest.net [63.235.41.90]
  6     *        *        *     Request timed out.
  7    97 ms    46 ms    46 ms  BLIZZARD-EN.ear3.LosAngeles1.Level3.net [4.71.135.106]
  8    65 ms    83 ms    64 ms  ae1-br01-eqla1.as57976.net [137.221.68.33]
  9    64 ms    64 ms    66 ms  et-0-0-2-br01-swlv10.as57976.net [137.221.65.69]
 10   124 ms   116 ms    65 ms  137.221.65.133
 11    65 ms    64 ms    65 ms  be1-pe2-eqch2.as57976.net [137.221.69.69]
 12    67 ms    67 ms    65 ms  24.105.62.129

Trace complete.

If that’s the extent of the changes, I’d say it’s pretty lazy. Maybe just an interim solution until they can perform more diagnostics? I’m about 30ms higher than normal (routing through Chicago) but I guess we’ll see how stable is is later tonight when everything seems to go downhill.

Roag-hellscream · October 23, 2019, 12:17am

Still bad except this time it’s the hop after the level3 backbone in LA.

Tracing route to 24.105.62.129 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  Firewall [192.168.117.1]
  2     4 ms     4 ms     4 ms  blng-dsl-gw16.blng.qwest.net [67.42.227.16]
  3     4 ms     4 ms     4 ms  blng-agw1.inet.qwest.net [65.100.79.121]
  4    16 ms    17 ms    16 ms  dvr3-brdr-01.inet.qwest.net [208.168.152.134]
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7    46 ms    46 ms    95 ms  BLIZZARD-EN.ear3.LosAngeles1.Level3.net [4.71.135.106]
  8   245 ms   268 ms   236 ms  ae1-br01-eqla1.as57976.net [137.221.68.33]
  9   245 ms   234 ms   234 ms  et-0-0-2-br01-swlv10.as57976.net [137.221.65.69]
 10   223 ms   220 ms   230 ms  137.221.65.133
 11   226 ms   226 ms   226 ms  be1-pe2-eqch2.as57976.net [137.221.69.69]
 12   235 ms   240 ms   243 ms  24.105.62.129

Trace complete.

winmtr

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                Firewall -    0 |  101 |  101 |    0 |    0 |    0 |    0 |
|            blng-dsl-gw16.blng.qwest.net -    0 |  101 |  101 |    3 |    4 |   35 |    5 |
|                blng-agw1.inet.qwest.net -    0 |  101 |  101 |    3 |    5 |   38 |    4 |
|             dvr3-brdr-01.inet.qwest.net -    0 |  101 |  101 |   15 |   17 |   50 |   25 |
|       63-235-41-90.dia.static.qwest.net -   95 |   20 |    1 |    0 |   16 |   16 |   16 |
|                   No response from host -  100 |   20 |    0 |    0 |    0 |    0 |    0 |
| BLIZZARD-EN.ear3.LosAngeles1.Level3.net -    0 |  101 |  101 |   45 |   50 |  105 |   45 |
|              ae1-br01-eqla1.as57976.net -    0 |  101 |  101 |  199 |  238 |  338 |  223 |
|        et-0-0-2-br01-swlv10.as57976.net -    0 |  101 |  101 |  198 |  230 |  304 |  223 |
|                          137.221.65.133 -    0 |  101 |  101 |  198 |  232 |  374 |  223 |
|               be1-pe2-eqch2.as57976.net -    0 |  101 |  101 |  198 |  227 |  265 |  223 |
|                           24.105.62.129 -    0 |  101 |  101 |  199 |  228 |  266 |  224 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Hjlmar-thrall · October 23, 2019, 12:38am

yep i am seeing the same thing

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - %	Sent	Recv	Best	Avrg	Wrst	Last
HomeRouter- 0	421	421	0	0	13	0
slc2-edge-06.inet.qwest.net- 0	421	421	10	18	112	14
dvr3-brdr-01.inet.qwest.net- 0	421	421	19	27	140	22
No response from host- 100	84	0	0	0	0	0
No response from host- 100	84	0	0	0	0	0
BLIZZARD-EN.ear3.LosAngeles1.Level3.net- 0	421	421	39	50	158	51
ae1-br01-eqla1.as57976.net- 1	413	411	139	231	389	234
et-0-0-2-br01-swlv10.as57976.net- 0	421	421	139	228	348	233
137.221.65.133- 1	408	405	135	236	1832	242
be1-pe1-eqch2.as57976.net- 1	413	411	138	222	351	232
chi-eqch2-ia-bons-02.as57976.net- 0	421	421	144	226	344	229
24.105.62.129-0	421	421	141	225	343	235
________________________________________________	______	______	______	______	______	______

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Zaarm-malganis · October 23, 2019, 12:39am

Back up again, was averaging 50ms as it was redirected to LA servers.

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    0 |  178 |  178 |    0 |    0 |    3 |    0 |
|            stpl-dsl-gw19.stpl.qwest.net -    0 |  178 |  178 |    2 |    3 |   35 |   14 |
|                stpl-agw1.inet.qwest.net -    0 |  178 |  178 |    2 |    9 |   65 |   39 |
|             216-160-19-2.mpls.qwest.net -    0 |  178 |  178 |    2 |    4 |   18 |    3 |
|                   No response from host -  100 |   35 |    0 |    0 |    0 |    0 |    0 |
| BLIZZARD-EN.ear3.LosAngeles1.Level3.net -    0 |  178 |  178 |   50 |   54 |  108 |   57 |
|              ae1-br01-eqla1.as57976.net -    1 |  174 |  173 |  140 |  223 |  814 |  233 |
|        et-0-0-2-br01-swlv10.as57976.net -    0 |  178 |  178 |  140 |  216 |  288 |  226 |
|                          137.221.65.133 -    0 |  178 |  178 |  140 |  219 |  335 |  227 |
|               be1-pe1-eqch2.as57976.net -    0 |  178 |  178 |  140 |  214 |  252 |  227 |
|        chi-eqch2-ia-bons-02.as57976.net -    0 |  178 |  178 |  141 |  215 |  254 |  228 |
|                           24.105.62.129 -    0 |  178 |  178 |  141 |  215 |  253 |  228 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Zephyy-thunderlord · October 23, 2019, 1:02am

Still seeing this also. Always seems to happen during raid time.

Ardrina-thrall · October 23, 2019, 1:05am

Raid time again and yet another spike in latency for another week. Started when I logged in 3 mins ago.

Xens-heartseeker · October 23, 2019, 1:08am

Man, this is almost unplayable for WPVP…

WinMTR Statistics

WinMTR statistics

Host	%	Sent	Recv	Best	Avrg	Wrst	Last
modem.Home	0	196	196	0	0	3	0
phn4-dsl-gw03.phn4.qwest.net	0	196	196	14	20	78	18
phn4-agw1.inet.qwest.net	0	196	196	15	22	93	18
209.181.128.2	2	185	182	15	60	934	18
No response from host	100	39	0	0	0	0	0
BLIZZARD-EN.ear3.LosAngeles1.Level3.net	0	196	196	25	33	183	25
ae1-br01-eqla1.as57976.net	2	188	186	213	259	477	240
et-0-0-2-br01-swlv10.as57976.net	2	188	186	205	252	310	246
137.221.65.133	0	196	196	222	273	1103	251
be1-pe2-eqch2.as57976.net	0	196	196	226	251	296	250
24.105.62.129	0	196	196	227	251	297	251

and a few minutes later, it gets worse…

WinMTR Statistics

WinMTR statistics

Host	%	Sent	Recv	Best	Avrg	Wrst	Last
modem.Home	0	423	423	0	0	5	2
phn4-dsl-gw03.phn4.qwest.net	0	423	423	14	19	78	15
phn4-agw1.inet.qwest.net	0	423	423	14	21	93	31
209.181.128.2	5	352	335	15	49	934	19
No response from host	100	84	0	0	0	0	0
BLIZZARD-EN.ear3.LosAngeles1.Level3.net	0	423	423	25	32	183	31
ae1-br01-eqla1.as57976.net	1	415	413	200	256	724	369
et-0-0-2-br01-swlv10.as57976.net	1	415	413	198	246	315	239
137.221.65.133	1	417	416	203	285	2251	247
be1-pe2-eqch2.as57976.net	0	423	423	201	245	296	261
24.105.62.129	0	423	423	200	246	297	258

Threvik-deathwing · October 23, 2019, 1:11am

Same deal again, only change was a dip for about 15-20 minutes at about 7:45. Bad hop did change to the Hop after Level3 with the change from Chicago to LA

| WinMTR statistics |

|------------------------------------------------|------|------|------|------|------|------|

| Local - 0 | 3061 | 3061 | 0 | 0 | 9 | 0 |

| rb4-bras.wnvl.centurytel .net - 1 | 3023 | 3013 | 1 | 8 | 215 | 4 |

| clma-agw1.inet.qwest .net - 1 | 3027 | 3018 | 2 | 10 | 178 | 9 |

| dvr3-brdr-01.inet.qwest .net - 1 | 3023 | 3013 | 15 | 24 | 227 | 19 |

| No response from host - 100 | 612 | 0 | 0 | 0 | 0 | 0 |

| BLIZZARD-EN.ear3.LosAngeles1.Level3 .net - 1 | 3031 | 3023 | 45 | 56 | 329 | 51 |

| ae1-br01-eqla1.as57976 .net - 1 | 2949 | 2921 | 90 | 237 | 1529 | 226 |

| et-0-0-2-br01-swlv10.as57976 .net - 2 | 2928 | 2894 | 88 | 230 | 1180 | 233 |

| 137.221.65.133 - 1 | 2979 | 2960 | 89 | 250 | 2498 | 241 |

| be1-pe2-eqch2.as57976 .net - 2 | 2939 | 2908 | 88 | 225 | 464 | 227 |

| 24.105.62.129 - 2 | 2919 | 2883 | 89 | 227 | 529 | 232 |

Arittamordio-stormrage · October 23, 2019, 1:11am

Same issue still occurring but it appears the route was slightly changed

5 21 ms 21 ms 21 ms 63-235-41-90.dia.static.qwest. net
6 * * * Request timed out.
7 50 ms 50 ms 50 ms BLIZZARD-EN.ear3.LosAngeles1.Level3. net [4.71.135.106]
8 271 ms 301 ms 234 ms ae1-br01-eqla1.as57976. net [137.221.68.33]
9 236 ms 237 ms 239 ms et-0-0-2-br01-swlv10.as57976. net [137.221.65.69]
10 233 ms 233 ms 248 ms 137.221.65.133
11 237 ms 219 ms 215 ms be1-pe2-eqch2.as57976. net [137.221.69.69]
12 220 ms 231 ms 224 ms chi-eqch2-ia-bons-04.as57976. net [137.221.66.15]
13 224 ms 229 ms 237 ms 24.105.62.129

Jayvzy-emerald-dream · October 23, 2019, 1:12am

Was doing fine earlier, but started going up like an hour ago.

|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|                         PK5001Z.PK5001Z -    0 |  228 |  228 |    1 |   14 |   97 |    7 |

|            stpl-dsl-gw12.stpl.qwest.net -    1 |  224 |  223 |   19 |   38 |  112 |   69 |

|                stpl-agw1.inet.qwest.net -    1 |  224 |  223 |   19 |   42 |  101 |   52 |

|             216-160-19-2.mpls.qwest.net -    1 |  224 |  223 |   20 |   39 |  114 |   50 |

|                   No response from host -  100 |   46 |    0 |    0 |    0 |    0 |    0 |

| BLIZZARD-EN.ear3.LosAngeles1.Level3.net -    0 |  228 |  228 |   68 |   94 |  273 |   94 |

|              ae1-br01-eqla1.as57976.net -    0 |  228 |  228 |  215 |  274 |  461 |  295 |

|        et-0-0-2-br01-swlv10.as57976.net -    1 |  220 |  218 |  216 |  265 |  343 |  310 |

|                          137.221.65.133 -    1 |  224 |  223 |  214 |  288 | 1092 |  270 |

|               be1-pe1-eqch2.as57976.net -    0 |  228 |  228 |  212 |  268 |  377 |  277 |

|        chi-eqch2-ia-bons-02.as57976.net -    1 |  224 |  223 |  221 |  268 |  334 |  323 |

|                           24.105.62.129 -    1 |  221 |  219 |  219 |  270 |  352 |  266 |

|________________________________________________|______|______|______|______|______|______|

   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Bins-bleeding-hollow · October 23, 2019, 1:25am

I waited until tonight to post this as I wanted to be sure it would improve or remedy the latency. Also wanted a baseline with the new network changes (Rerouting through LA vice Chicago):

TLDR: Enabling and using IPv6 improves latency.

My Latencies:
Normal: 13ms
Evening (IPv4): 220ms
Evening (IPv6): 60ms

This is a 4 step process, every step must be complete before you will see results. If any step is not performed you will continue to connect using IPv4 and not see any change. Remove spaces in below referenced URLS.

NOTE: If you are not comfortable making these changes please contact CenturyLink support. I’m not responsible for you breaking your internet connection.

Enable IPv6 on your CenturyLink router:

URL: https:// www.centurylink .com/home/help/internet/modems-and-routers/zyxel-c3000z/enable-ipv6.html

Note: By default IPv6 is Disabled on your router however, CenturyLink’s network does support IPv6 in some but not all areas. If you have a different model modem, please search for the appropriate steps to enable IPv6 on your specific model.
Note: Your router will reboot after changes are made and you will loose internet connectivity briefly.
Enable IPv6 on your Gaming Machine’s Network Configuration:

MAC: https:// support.apple .com/guide/mac-help/use-ipv6-on-mac-mchlp2499/mac
Windows: https:// support.microsoft .com/en-us/help/929852/guidance-for-configuring-ipv6-in-windows-for-advanced-users

Note: I used “Configure IPv6” set to “Automatically” on my iMac.
Turn Off and Turn On your Gaming Machine’s Network Interface:

Note: This will allow the Network Interface Card (NIC) to reset and grab an IPv6 address. If you dont know how to do this step in Settings you may simply reboot your Gaming Machine.
Test to ensure your Router and Gaming Machine are configured correctly for IPv6:

URL: https:// ipv6-test .com/

Note: You should see an IPv4 & IPv6 address listed and a green “Supported” box. If no IPv6 address is shown, either an above step was not performed or your CenturyLink Modem or CenturyLink Service Area do not support IPv6.
Enable IPV6 on WoW Network Settings:

In the WoW client goto: System >> Network >> Enable IPv6 when available.

Hope this helps until the underlying issue is resolved. Cheers!