Welcome to the Cox Community
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
Messages
Selected Messages
New Contributor
•
Ongoing problems with Blizzard
For months now, off and on, Cox has an issue with connections to Blizzard servers. The issue was discussed in great detail on Blizzard forums, and is apparently caused by an excessively busy node. Rerouting seems to work temporarily, but the problem keeps coming back, and it keeps happening at peak game time, ie the time when everyone can play.
I still cannot connect to Blizzard servers... when will this get resolved? Asking this question feels like yelling into a wind tunnel, I know.
RoyCq
New Contributor
•
Here is a tracert during the outage time:
Tracing route to 12.129.222.10 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 37 ms 20 ms 35 ms 10.132.184.1
3 15 ms 11 ms 13 ms 68.11.14.138
4 19 ms 17 ms 16 ms 68.11.14.138
5 40 ms 39 ms 55 ms dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
6 20 ms 22 ms 25 ms ae-12.r08.dllstx09.us.bb.gin.ntt.net [129.250.194.173]
7 21 ms 20 ms 21 ms ae-5.r01.dllstx04.us.bb.gin.ntt.net [129.250.3.233]
8 41 ms 75 ms 81 ms ae-0.att.dllstx04.us.bb.gin.ntt.net [129.250.8.238]
9 51 ms 27 ms 92 ms cr2.dlstx.ip.att.net [12.123.16.78]
10 28 ms 22 ms 22 ms 12.123.249.221
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.
0
0
RoyCq
New Contributor
•
I've read that this is due to an over-saturated node, and that it isn't Cox's problem. Maybe you can find a different answer. It certainly feels to me that if Cox New Orleans customers exclusively are not able to access one of the most popular gaming servers on the planet, then that is a Cox problem.
If the node is overloaded at some times, can't Cox route around it? I can use a VPN program to emulate being in a different location, and that works, albeit with a high latency from all the extra hopping around.
If no one has responsibility for this, and Cox just can't do anything about it, does that mean my only option is to switch service? Thanks for your help.
0
0