I live in Minneapolis, but I have ~250 ms latency to Chicago servers. Many of my friends who also live in Minneapolis but have different ISPs have recently had the same issues. Some spike to high latency, anywhere from 180-400. I am currently sitting at 250 ms with very little fluctuation and no packet loss so I ran WinMTR to the Chicago server (24.105.62.129):
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
same issue here. 300-400 ping on my end. just started today. here is tracert
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms <1 ms <1 ms 192.168.0.1
3 18 ms 20 ms 65 ms cdrr-dsl-gw18.cdrr.qwest. net [209.181.206.18]
4 23 ms 18 ms 21 ms cdrr-agw1.inet.qwest. net [209.181.211.137]
5 61 ms 61 ms 61 ms los-edge-07.inet.qwest. net [67.14.102.142]
6 67 ms 68 ms 68 ms 65.153.81.102
7 68 ms 67 ms 68 ms i-93.1wlt-core02.telstraglobal. net [202.84.253.85]
8 260 ms 260 ms 262 ms i-15006.sgpl-core02.telstraglobal. net [202.84.140.233]
9 260 ms 299 ms 259 ms i-92.sgpl01.telstraglobal. net [202.84.224.194]
10 241 ms 241 ms 241 ms unknown.telstraglobal. net [210.176.138.174]
11 241 ms 256 ms 241 ms 203.118.15.10
12 241 ms 246 ms 241 ms 203.118.6.97
13 253 ms 264 ms 253 ms 203.117.163.174
14 261 ms 250 ms 268 ms et-0-0-48-br01-eqsg3.as57976. net [137.221.87.33]
15 250 ms 250 ms 250 ms ge-0-0-4-br01-eqty2.as57976. net [137.221.65.126]
16 250 ms 249 ms 249 ms xe-0-0-0-1-br01-eqla1.as57976. net [137.221.65.56]
17 250 ms 249 ms 249 ms et-0-0-2-br01-swlv10.as57976. net [137.221.65.69]
18 251 ms 254 ms 249 ms 137.221.65.133
19 250 ms 250 ms 249 ms be1-pe01-eqch2.as57976. net [137.221.69.67]
20 251 ms 251 ms 251 ms 24.105.62.129
Hi, I’m on PS4, so I can’t run your guys’ test, but I live in the inland northwest (about six hours east of Seattle. ) I normally range 85 ping. Today, I’ve been getting 180-200 ping, and it feels unplayable. I main off tank, so this affects hooks, it affects what I see when trying to place projected barriers at the right time to save people, eating ults with matrix as they’re cast at the right time… you get the idea. I don’t know if I’m connecting to Chicago or something, but this 120+ ping jump is ruining the game for me. The game was running at 85 ping for me yesterday (9/29).
I’ve done all the things people say to do, like resetting the router (allowed it to be unplugged 10 mins), using ethernet cable, turning off all devices that might be connected to the router (laptop, phone, etc), turning off the console, and everything else. My connection speeds on tests have not changed, and I’m not really sure if there’s anything else I can do.
It’s helpful seeing other people with unnecessarily high ping, maybe it’s their issue, I don’t know, but I thought I’d add my voice to the “getting weirdly higher ping than what I usually get in NA” topic.
I usually get 35-40 ms in a regular game (NA East) and now I’m getting 140-260 ms. Not sure what happened but in my last game, it took 22 mins in support queue and i had all spanish speaking players, which I’ve never had happen before.
Hey, Im from inland WA state and im also noticing a huge ping jump. I did a similar tracert to the blizzard servers and im getting snagged on 202.84.144.193 which is telstraglobal. My best guess is that blizzard had a switch go down or something and we are being automatically redirected I hope they are aware of the issue and are working on getting it back up and running shortly! I gotta get my fix you know what i mean.
I am having a similar issue. My ping is normally 30 here and I was just in a comp match where people were speaking Portuguese and they said it was the south American server. I looked at my ping and noticed it was 150. I’m in the northern part of the US so I definitely should not be on that server.
Glad I’m not alone. This is likely an issue on their end thankfully.
Tracing route to 24.105.30.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms modem.Home [192.168.0.1]
2 3 ms 2 ms 3 ms tukw-dsl-gw70.tukw.qwest.net [63.231.10.70]
3 3 ms 8 ms 5 ms 63-226-198-41.tukw.qwest.net [63.226.198.41]
4 20 ms 20 ms 19 ms snj-edge-06.inet.qwest.net [67.14.34.202]
5 20 ms 21 ms 21 ms 65.123.13.174
6 23 ms 21 ms 21 ms https://pastebin.com/kxYbphRn [202.84.247.18]
7 222 ms 225 ms 224 ms i-25008.sgpl-core02.telstraglobal.net [202.84.144.193]
8 222 ms 222 ms 224 ms i-92.sgpl01.telstraglobal.net [202.84.224.194]
9 208 ms 209 ms 216 ms unknown.telstraglobal.net [210.176.138.174]
10 211 ms 208 ms 209 ms 203.118.15.133
11 222 ms 221 ms 221 ms 203.118.6.101
12 211 ms 224 ms 207 ms 203.117.163.174
13 222 ms 225 ms 217 ms et-0-0-48-br01-eqsg3.as57976.net [137.221.87.33]
14 215 ms 215 ms 215 ms ge-0-0-4-br01-eqty2.as57976.net [137.221.65.126]
15 266 ms 232 ms 244 ms xe-0-0-0-1-br01-eqla1.as57976.net [137.221.65.56]
16 217 ms 216 ms 215 ms be1-pe01-eqla1.as57976.net [137.221.68.67]
17 215 ms 216 ms 216 ms lax-eqla1-ia-bons-02.as57976.net [137.221.66.3]
18 215 ms 215 ms 216 ms 24.105.30.129
Trace complete.
> ~$ traceroute battle.net
traceroute to battle.net (137.221.106.104), 30 hops max, 38 byte packets
1 rb-bras-sea.centurytel.net (63.231.10.151) 35.285 ms 37.009 ms 32.837 ms
2 63-226-199-1.tukw.qwest.net (63.226.199.1) 38.607 ms 42.887 ms 42.809 ms
3 snj-edge-06.inet.qwest.net (67.14.34.202) 48.963 ms 57.025 ms *
4 65.123.13.174 (65.123.13.174) 44.569 ms 65.131 ms 54.255 ms
5 i-92.eqnx-core02.telstraglobal.net (202.84.247.18) 63.280 ms 59.852 ms 43.149 ms
6 i-25008.sgpl-core02.telstraglobal.net (202.84.144.193) 256.690 ms 260.716 ms 252.649 ms
7 i-92.sgpl01.telstraglobal.net (202.84.224.194) 252.242 ms * 255.550 ms
8 unknown.telstraglobal.net (210.176.138.174) 243.622 ms 239.330 ms 247.791 ms
9 203.118.15.10 (203.118.15.10) 246.801 ms 203.118.15.133 (203.118.15.133) 234.534 ms 235.423 ms
10 203.118.6.97 (203.118.6.97) 245.582 ms 242.722 ms 246.340 ms
11 203.117.163.174 (203.117.163.174) 254.935 ms 236.409 ms 254.732 ms
12 et-0-0-48-br01-eqsg3.as57976.net (137.221.87.33) 244.452 ms 251.385 ms 252.095 ms
13 ge-0-0-4-br01-eqty2.as57976.net (137.221.65.126) 238.676 ms 259.582 ms 259.019 ms
14 xe-0-0-0-1-br01-eqla1.as57976.net (137.221.65.56) 259.927 ms 259.498 ms 237.608 ms
15 et-0-0-2-br01-swlv10.as57976.net (137.221.65.69) 260.376 ms 243.203 ms 246.474 ms
16 et-0-0-31-pe01-swlv10.as57976.net (137.221.83.67) 259.094 ms 236.476 ms 259.884 ms
17 * las-swlv10-ia-bons-01.as57976.net (137.221.66.17) 243.332 ms !A *
18 * * *
19 * * *
20 * las-swlv10-ia-bons-01.as57976.net (137.221.66.17) 259.953 ms !A *
21 * * *
22 * * *
23 * * *
24 las-swlv10-ia-bons-01.as57976.net (137.221.66.17) 239.521 ms !A * *
25 las-swlv10-ia-bons-02.as57976.net (137.221.66.19) 243.639 ms !A * *
26 * * *
27 * * *
28 * * *
29 * * las-swlv10-ia-bons-02.as57976.net (137.221.66.19) 259.333 ms !A
30 * las-swlv10-ia-bons-02.as57976.net (137.221.66.19) 245.958 ms !A *
$ whois 65.123.13.174
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2019, American Registry for Internet Numbers, Ltd.
#
# start
NetRange: 65.112.0.0 - 65.127.255.255
CIDR: 65.112.0.0/12
NetName: CENTURYLINK-LEGACY-QWEST-65-112-0
NetHandle: NET-65-112-0-0-1
Parent: NET65 (NET-65-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: CenturyLink Communications, LLC (CCL-534)
RegDate: 2001-01-04
Updated: 2018-02-21
Ref: https://rdap.arin.net/registry/ip/65.112.0.0
OrgName: CenturyLink Communications, LLC
OrgId: CCL-534
Address: 100 CENTURYLINK DR
City: Monroe
StateProv: LA
PostalCode: 71201
Country: US
RegDate: 2018-07-12
Updated: 2018-08-15
Comment: ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE
Comment:
Comment: For abuse issues, please email abuse@centurylinkservices.net
Comment: All abuse reports MUST include:
Comment: * src IP
Comment: * dest IP (your IP)
Comment: * dest port
Comment: * Accurate date/timestamp and timezone of activity
Comment: * Intensity/frequency (short log extracts)
Comment: * Your contact details (phone and email)
Comment: Without these we will be unable to identify the correct owner of the IP address at that point in time.
Comment:
Comment: For subpoena or court order please fax 844.254.5800 or refer to our Law Enforcement Support page http://www.centurylink.com/static/Pages/AboutUs/Legal/LawEnforcement/
Ref: https://rdap.arin.net/registry/entity/CCL-534
OrgAbuseHandle: CAD54-ARIN
OrgAbuseName: Centurylink Abuse Desk
OrgAbusePhone: +1-877-886-6515
OrgAbuseEmail: abuse@centurylinkservices.net
OrgAbuseRef: https://rdap.arin.net/registry/entity/CAD54-ARIN
OrgTechHandle: QIA-ARIN
OrgTechName: Centurylink IP Admin
OrgTechPhone: +1-877-886-6515
OrgTechEmail: ipadmin@centurylink.com
OrgTechRef: https://rdap.arin.net/registry/entity/QIA-ARIN
# end
# start
NetRange: 65.123.13.0 - 65.123.13.255
CIDR: 65.123.13.0/24
NetName: SNFC01-WAN-65-123-13
NetHandle: NET-65-123-13-0-1
Parent: CENTURYLINK-LEGACY-QWEST-65-112-0 (NET-65-112-0-0-1)
NetType: Reassigned
OriginAS:
Organization: Qwest Communications (QWST)
RegDate: 2005-09-28
Updated: 2005-09-28
Ref: https://rdap.arin.net/registry/ip/65.123.13.0
OrgName: Qwest Communications
OrgId: QWST
Address: 950 17th Street
Address: Suite 1900
City: Denver
StateProv: CO
PostalCode: 80202
Country: US
RegDate: 1998-09-07
Updated: 2002-08-29
Ref: https://rdap.arin.net/registry/entity/QWST
OrgTechHandle: QIA-ARIN
OrgTechName: Centurylink IP Admin
OrgTechPhone: +1-877-886-6515
OrgTechEmail: ipadmin@centurylink.com
OrgTechRef: https://rdap.arin.net/registry/entity/QIA-ARIN
OrgAbuseHandle: QIA2-ARIN
OrgAbuseName: Qwest Abuse
OrgAbusePhone: +1-877-886-6515
OrgAbuseEmail: abuse@qwest.net
OrgAbuseRef: https://rdap.arin.net/registry/entity/QIA2-ARIN
OrgNOCHandle: QIN-ARIN
OrgNOCName: Qwest IP NOC
OrgNOCPhone: +1-877-886-6515
OrgNOCEmail: support@qwestip.net
OrgNOCRef: https://rdap.arin.net/registry/entity/QIN-ARIN
# end
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2019, American Registry for Internet Numbers, Ltd.
#
i didn’t restart anything. i was in the middle of a laggy match and my screen went black and it came back at 50ms. I did do the DNS flush earlier, but still had issues.
Do you have CenturyLink? A lot of people I know, myself included, are having this issue and are being connected to sae1 instead of lax1, and the only people being affected appear to be CenturyLink users.
I live in Pennsylvania and only seem to be having latency issues when connected to Blizzard’s servers. I did all the steps recommended, ran some screen shots, and still have 150ms+ ping and heavy rubberbanding issues in game. As a result I just can’t play the game, and certainly can’t play competitive like this.
Role queue is the best thing to ever happen to this game, but aside from lack of tank players these connection issues have been horrendous lately. They started happening for me around the same time. Is it possible the two are related?
Edit: I do not have CenturyLink (I don’t think it’s available around here).
It looks like the ISP is routing your signal through Tokyo! They should not be doing that. Please contact the ISP and let them know of the error.
I do also notice a few other user’s posting tests who also route through “Telstra” or “qwest” backbone so it’s likely a peering issue not actually related to the ISP themselves. They will need to reach out to their peer networks to resolve the problem.
You may need to request a Tier 2 or Tier 3 agent who understands what routing is. Providing them the MTR test showing the obscure routing should help escalate the issue.