Anyone else getting bad connection

Technical Support
Anyone else getting bad connection during the last few days? My loading screen taking forever to load and getting a couple laggy games a night now even disconnecting. Def not my internet, or my computer..
Hey, DEVIN! Could you grab a traceroute test to US West (IP: 24.105.30.129 )? When did this problem start? Has it been around a week or so since it started appearing?
Hi Caterpepi,

I have had similar problems, but with a constant high ping reaching upwards of over 200ms. Here is my traceroute test to US West. That is the closest IP to me. This has been an issue for the past two days.

Tracing route to 24.105.30.129 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 7 ms 7 ms 10.182.0.1
3 8 ms 8 ms 7 ms 68.6.14.56
4 23 ms 19 ms 55 ms 100.120.108.24
5 11 ms 9 ms 9 ms 68.1.1.61
6 12 ms 11 ms 10 ms 68.105.30.130
7 28 ms 10 ms 12 ms ae1-br02-eqla1.as57976.net [137.221.68.35]
8 165 ms 164 ms 163 ms be2-pe01-eqla1.as57976.net [137.221.68.71]
9 175 ms 174 ms 174 ms 24.105.30.129

Trace complete.
I have also run the Looking-Glass tool and here are the results.

TRACEROUTE:
traceroute to 68.6.207.40 (68.6.207.40), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.916 ms 1.921 ms 1.925 ms Blizzard(24.105.18.3) 1.965 ms 1.971 ms 1.992 ms
3 137.221.105.12 (137.221.105.12) 1.299 ms 1.440 ms 1.467 ms
4 137.221.66.16 (137.221.66.16) 1.087 ms 1.212 ms 1.248 ms
5 137.221.83.66 (137.221.83.66) 6.481 ms 6.485 ms 6.489 ms
6 137.221.65.68 (137.221.65.68) 6.119 ms 5.621 ms 5.642 ms
7 137.221.68.32 (137.221.68.32) 5.587 ms 5.586 ms 5.444 ms
8 langbbrj02-ae1.301.r2.la.cox.net (68.105.30.129) 5.370 ms 5.614 ms 5.612 ms
9 fed1dsrj01-ae1.0.rd.sd.cox.net (68.1.0.205) 9.511 ms 9.357 ms 9.346 ms
10 ip68-6-207-40.sd.sd.cox.net (68.6.207.40) 16.731 ms 20.314 ms 19.403 ms

10/04/2019 17:24:14 UTC
--------------------

PING:
PING 68.6.207.40 (68.6.207.40) 56(84) bytes of data.
64 bytes from 68.6.207.40: icmp_seq=1 ttl=53 time=16.3 ms
64 bytes from 68.6.207.40: icmp_seq=3 ttl=53 time=14.8 ms
64 bytes from 68.6.207.40: icmp_seq=4 ttl=53 time=16.0 ms

--- 68.6.207.40 ping statistics ---
4 packets transmitted, 3 received, 25% packet loss, time 2998ms
rtt min/avg/max/mdev = 14.891/15.739/16.315/0.620 ms

10/04/2019 17:24:14 UTC
--------------------

PING:
PING 68.6.207.40 (68.6.207.40) 56(84) bytes of data.
64 bytes from 68.6.207.40: icmp_seq=2 ttl=53 time=16.7 ms
64 bytes from 68.6.207.40: icmp_seq=3 ttl=53 time=14.8 ms
64 bytes from 68.6.207.40: icmp_seq=4 ttl=53 time=17.1 ms

--- 68.6.207.40 ping statistics ---
4 packets transmitted, 3 received, 25% packet loss, time 2998ms
rtt min/avg/max/mdev = 14.855/16.258/17.152/1.015 ms

10/04/2019 17:24:14 UTC
--------------------

TRACEROUTE:
traceroute to 68.6.207.40 (68.6.207.40), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.308 ms 0.344 ms 0.354 ms Blizzard(24.105.18.3) 1.419 ms 1.445 ms 1.439 ms
3 137.221.105.12 (137.221.105.12) 0.625 ms 0.834 ms 0.853 ms
4 137.221.66.16 (137.221.66.16) 3.663 ms 3.708 ms 3.718 ms
5 137.221.83.66 (137.221.83.66) 5.981 ms 6.031 ms 6.062 ms
6 137.221.65.68 (137.221.65.68) 5.692 ms 5.798 ms 5.782 ms
7 137.221.68.32 (137.221.68.32) 5.556 ms 5.686 ms 5.712 ms
8 langbbrj02-ae1.301.r2.la.cox.net (68.105.30.129) 5.364 ms 5.585 ms 5.572 ms
9 fed1dsrj01-ae1.0.rd.sd.cox.net (68.1.0.205) 9.258 ms 9.170 ms 9.156 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

10/04/2019 17:24:14 UTC
--------------------

MTR:
Start: Wed Apr 10 17:24:14 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.5 0.2 2.2 0.3 Blizzard 0.0% 10 0.5 0.6 0.5 1.1 0.0
3.|-- 137.221.105.12 0.0% 10 0.6 0.7 0.5 1.1 0.0
4.|-- 137.221.66.16 0.0% 10 0.6 0.7 0.5 1.2 0.0
5.|-- 137.221.83.66 0.0% 10 5.6 5.8 5.6 6.1 0.0
6.|-- 137.221.65.68 0.0% 10 5.7 8.2 5.7 29.7 7.6
7.|-- 137.221.68.32 0.0% 10 5.6 6.0 5.5 8.9 0.9
8.|-- langbbrj02-ae1.301.r2.la.cox.net 0.0% 10 5.5 5.6 5.4 6.6 0.3
9.|-- fed1dsrj01-ae1.0.rd.sd.cox.net 0.0% 10 9.3 9.7 9.2 13.3 1.1
10.|-- ip68-6-207-40.sd.sd.cox.net 0.0% 10 16.5 16.3 15.4 17.1 0.0

10/04/2019 17:24:14 UTC
--------------------

MTR:
Start: Wed Apr 10 17:24:14 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 1.2 0.2 9.2 2.8 Blizzard 0.0% 10 0.5 0.6 0.5 0.8 0.0
3.|-- 137.221.105.12 0.0% 10 0.7 0.5 0.5 0.7 0.0
4.|-- 137.221.66.16 0.0% 10 0.6 0.6 0.6 1.0 0.0
5.|-- 137.221.83.66 0.0% 10 5.8 6.3 5.7 9.5 1.1
6.|-- 137.221.65.68 0.0% 10 5.7 9.2 5.7 39.7 10.7
7.|-- 137.221.68.32 0.0% 10 6.2 5.7 5.5 6.2 0.0
8.|-- langbbrj02-ae1.301.r2.la.cox.net 0.0% 10 5.5 7.1 5.4 16.7 3.4
9.|-- fed1dsrj01-ae1.0.rd.sd.cox.net 0.0% 10 9.2 9.7 9.2 12.0 0.7
10.|-- ip68-6-207-40.sd.sd.cox.net 30.0% 10 18.0 16.9 14.9 19.2 1.4

10/04/2019 17:24:14 UTC
--------------------
I also came online to contact blizzard support about my Starcraft 2 connections and ran into this conversation. I am like others here, from the US west, with poor connections when on Starcraft 2. I really hope that this situation can be resolved.

Here are the results for my looking glass as well.

TRACEROUTE:
traceroute to 71.38.145.38 (71.38.145.38), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.317 ms 0.305 ms 0.303 ms
2 24.105.18.131 (24.105.18.131) 0.602 ms 0.631 ms 0.695 ms
3 137.221.105.12 (137.221.105.12) 1.332 ms 1.331 ms 1.344 ms
4 137.221.66.16 (137.221.66.16) 1.327 ms 1.325 ms 1.324 ms
5 137.221.83.66 (137.221.83.66) 2.280 ms 2.327 ms 2.327 ms
6 137.221.65.68 (137.221.65.68) 5.729 ms 10.081 ms 10.065 ms
7 137.221.68.32 (137.221.68.32) 9.979 ms 5.702 ms 5.682 ms
8 xe-9-3-0.edge2.LosAngeles9.Level3.net (4.53.230.237) 5.400 ms 5.567 ms 5.552 ms
9 ae-1-4.bar1.LasVegas1.Level3.net (4.69.133.109) 10.599 ms 10.596 ms 10.664 ms
10 75-163-31-253.lsv2.qwest.net (75.163.31.253) 10.976 ms 11.648 ms 11.636 ms
11 75.160.224.26 (75.160.224.26) 11.124 ms 11.016 ms 10.971 ms
12 71-38-145-38.lsv2.qwest.net (71.38.145.38) 17.447 ms 17.808 ms 17.735 ms

10/04/2019 20:18:33 UTC
--------------------

TRACEROUTE:
traceroute to 71.38.145.38 (71.38.145.38), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.841 ms 0.845 ms 0.860 ms Blizzard(24.105.18.3) 0.922 ms 0.936 ms 1.016 ms
3 137.221.105.16 (137.221.105.16) 0.936 ms 0.987 ms 1.073 ms
4 137.221.66.22 (137.221.66.22) 1.001 ms 1.004 ms 1.005 ms
5 137.221.83.68 (137.221.83.68) 25.542 ms 25.565 ms 25.579 ms
6 137.221.65.68 (137.221.65.68) 6.091 ms 6.815 ms 6.803 ms
7 137.221.68.32 (137.221.68.32) 6.546 ms 6.102 ms 6.097 ms
8 xe-9-3-0.edge2.LosAngeles9.Level3.net (4.53.230.237) 5.996 ms 6.012 ms 5.537 ms
9 ae-1-4.bar1.LasVegas1.Level3.net (4.69.133.109) 10.751 ms 10.769 ms 10.771 ms
10 75-163-31-253.lsv2.qwest.net (75.163.31.253) 12.963 ms 12.963 ms 10.849 ms
11 75.160.224.26 (75.160.224.26) 11.594 ms 11.760 ms 11.263 ms
12 71-38-145-38.lsv2.qwest.net (71.38.145.38) 17.215 ms 17.663 ms 17.673 ms

10/04/2019 20:18:34 UTC
--------------------

PING:
PING 71.38.145.38 (71.38.145.38) 56(84) bytes of data.
64 bytes from 71.38.145.38: icmp_seq=1 ttl=53 time=17.4 ms
64 bytes from 71.38.145.38: icmp_seq=2 ttl=53 time=17.2 ms
64 bytes from 71.38.145.38: icmp_seq=3 ttl=53 time=17.4 ms
64 bytes from 71.38.145.38: icmp_seq=4 ttl=53 time=17.8 ms

--- 71.38.145.38 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 17.255/17.488/17.833/0.249 ms

10/04/2019 20:18:34 UTC
--------------------

PING:
PING 71.38.145.38 (71.38.145.38) 56(84) bytes of data.
64 bytes from 71.38.145.38: icmp_seq=1 ttl=53 time=17.8 ms
64 bytes from 71.38.145.38: icmp_seq=2 ttl=53 time=17.7 ms
64 bytes from 71.38.145.38: icmp_seq=3 ttl=53 time=17.6 ms
64 bytes from 71.38.145.38: icmp_seq=4 ttl=53 time=17.6 ms

--- 71.38.145.38 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 17.601/17.704/17.860/0.165 ms

10/04/2019 20:18:33 UTC
--------------------

MTR:
Start: Wed Apr 10 20:18:33 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 24.105.18.131 0.0% 10 0.7 0.6 0.5 0.7 0.0
3.|-- 137.221.105.12 0.0% 10 0.7 0.7 0.5 1.1 0.0
4.|-- 137.221.66.16 0.0% 10 0.8 0.7 0.5 0.8 0.0
5.|-- 137.221.83.66 0.0% 10 3.2 6.1 2.2 11.8 3.2
6.|-- 137.221.65.68 0.0% 10 8.0 8.7 5.7 33.8 8.8
7.|-- 137.221.68.32 0.0% 10 5.7 5.6 5.5 5.9 0.0
8.|-- xe-9-3-0.edge2.LosAngeles9.Level3.net 0.0% 10 5.5 5.8 5.3 7.3 0.5
9.|-- ae-1-4.bar1.LasVegas1.Level3.net 0.0% 10 10.7 10.6 10.5 10.7 0.0
10.|-- 75-163-31-253.lsv2.qwest.net 0.0% 10 11.0 11.3 10.8 12.3 0.3
11.|-- 75.160.224.26 40.0% 10 11.4 12.0 11.0 15.6 1.7
12.|-- 71-38-145-38.lsv2.qwest.net 0.0% 10 17.6 17.6 17.2 18.0 0.0

10/04/2019 20:18:33 UTC
--------------------

MTR:
Start: Wed Apr 10 20:18:34 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0 Blizzard 0.0% 10 0.6 2.1 0.5 8.5 3.2
3.|-- 137.221.105.16 0.0% 10 0.6 0.8 0.5 2.6 0.6
4.|-- 137.221.66.22 0.0% 10 0.7 0.6 0.5 0.8 0.0
5.|-- 137.221.83.68 0.0% 10 11.7 5.4 1.0 11.7 3.8
6.|-- 137.221.65.68 0.0% 10 5.8 9.0 5.6 38.0 10.2
7.|-- 137.221.68.32 0.0% 10 5.6 6.9 5.5 14.5 2.8
8.|-- xe-9-3-0.edge2.LosAngeles9.Level3.net 0.0% 10 5.3 5.4 5.3 5.5 0.0
9.|-- ae-1-4.bar1.LasVegas1.Level3.net 0.0% 10 10.6 10.8 10.5 12.7 0.5
10.|-- 75-163-31-253.lsv2.qwest.net 0.0% 10 10.9 11.1 10.8 12.5 0.3
11.|-- 75.160.224.26 50.0% 10 11.1 11.4 11.1 12.3 0.0
12.|-- 71-38-145-38.lsv2.qwest.net 0.0% 10 17.5 17.6 17.4 18.0 0.0

10/04/2019 20:18:34 UTC
--------------------
I have also very laggy games since yesterday. Im from Europe. First i thought ist the new graphics driver but another one did not solve the problem either.

Routenverfolgung zu 185.60.112.157 ber maximal 30 Hops

1 2 ms 2 ms 1 ms 10.0.0.138
2 9 ms 8 ms 7 ms 91-114-247-254.adsl.highway.telekom.at [91.114.247.254]
3 10 ms 10 ms 10 ms 195.3.74.81
4 21 ms 21 ms 21 ms lg2-1171.as8447.a1.net [195.3.64.6]
5 22 ms 21 ms 22 ms pr01.eqfr5.blizzardonline.net [80.81.195.26]
6 28 ms 28 ms 28 ms ae1-br01-eqfr5.as57976.net [137.221.80.33]
7 29 ms 28 ms 27 ms et-0-0-2-br01-eqam1.as57976.net [137.221.65.29]
8 28 ms 28 ms 28 ms et-0-0-31-pe01-eqam1.as57976.net [137.221.78.67]
9 27 ms 28 ms 27 ms 137.221.66.43
10 27 ms 28 ms 28 ms 185.60.112.157

Ablaufverfolgung beendet.

-----------------------------------------------

Routenverfolgung zu 185.60.112.158 ber maximal 30 Hops

1 1 ms 1 ms <1 ms 10.0.0.138
2 8 ms 8 ms 8 ms 91-114-247-254.adsl.highway.telekom.at [91.114.247.254]
3 11 ms 11 ms 11 ms 195.3.74.81
4 21 ms 21 ms 21 ms lg2-1171.as8447.a1.net [195.3.64.6]
5 21 ms 21 ms 21 ms pr01.eqfr5.blizzardonline.net [80.81.195.26]
6 28 ms 29 ms 28 ms ae1-br01-eqfr5.as57976.net [137.221.80.33]
7 284 ms 439 ms 399 ms et-0-0-2-br01-eqam1.as57976.net [137.221.65.29]
8 27 ms 28 ms 27 ms et-0-0-31-pe02-eqam1.as57976.net [137.221.78.69]
9 28 ms 29 ms 28 ms 137.221.66.45
10 29 ms 30 ms 28 ms 185.60.112.158

Ablaufverfolgung beendet.

-------------------------------------------------------------

Routenverfolgung zu 185.60.114.159 ber maximal 30 Hops

1 1 ms 1 ms 2 ms 10.0.0.138
2 9 ms 8 ms 8 ms 91-114-247-254.adsl.highway.telekom.at [91.114.247.254]
3 10 ms 10 ms 10 ms 195.3.74.81
4 22 ms 20 ms 22 ms lg2-1171.as8447.a1.net [195.3.64.6]
5 22 ms 21 ms 23 ms pr01.eqfr5.blizzardonline.net [80.81.195.26]
6 35 ms 34 ms 34 ms ae1-br01-eqfr5.as57976.net [137.221.80.33]
7 38 ms 38 ms 38 ms et-0-0-2-br01-eqpa4.as57976.net [137.221.65.26]
8 34 ms 38 ms 34 ms be1-pe01-eqpa4.as57976.net [137.221.77.67]
9 * * * Zeitberschreitung der Anforderung.
10 * * * Zeitberschreitung der Anforderung.
11 * * * Zeitberschreitung der Anforderung.
12 * * * Zeitberschreitung der Anforderung.
13 * * * Zeitberschreitung der Anforderung.
14 * * * Zeitberschreitung der Anforderung.
15 * * * Zeitberschreitung der Anforderung.
16 * * * Zeitberschreitung der Anforderung.
17 * * * Zeitberschreitung der Anforderung.
18 * * * Zeitberschreitung der Anforderung.
19 * * * Zeitberschreitung der Anforderung.
20 * * * Zeitberschreitung der Anforderung.
21 * * * Zeitberschreitung der Anforderung.
22 * * * Zeitberschreitung der Anforderung.
23 * * * Zeitberschreitung der Anforderung.
24 * * * Zeitberschreitung der Anforderung.
25 * * * Zeitberschreitung der Anforderung.
26 * * * Zeitberschreitung der Anforderung.
27 * * * Zeitberschreitung der Anforderung.
28 * * * Zeitberschreitung der Anforderung.
29 * * * Zeitberschreitung der Anforderung.
30 * * * Zeitberschreitung der Anforderung.

Ablaufverfolgung beendet.
04/09/2019 01:53 PMPosted by Caterpepi
Hey, DEVIN! Could you grab a [url="https://battle.net/support/article/7870?utm_source=internal-TechForum&utm_medium=posting&utm_campaign=BlizzardCS&utm_content=solution"]traceroute test[/url] to US West (IP: 24.105.30.129 )? When did this problem start? Has it been around a week or so since it started appearing?
Yeah about a week now. It says access is denied when I'm trying to run tracert and I am the administrator + firewall off.

Join the Conversation

Return to Forum