Trunkmonky's profile

New Contributor

 • 

1 Message

Closed

tracert timed out to Blizzard servers

Ran a tracert after being disconnected from Blizzard servers and not being able to connect on their website either. Other people still connected to these servers so it's not on their end.

Results from server tracert:

Tracing route to 12.129.254.184 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 7 ms 7 ms 10.33.224.1
3 7 ms 7 ms 7 ms COX-68-12-9-80-static.coxinet.net [68.12.9.80]
4 9 ms 8 ms 8 ms COX-68-12-19-152-static.coxinet.net [68.12.19.15
2]
5 55 ms 55 ms 56 ms langbbrj01-ae2.rd.la.cox.net [68.1.1.14]
6 54 ms 58 ms 54 ms ae-7.r00.lsanca19.us.bb.gin.ntt.net [129.250.194
.165]
7 50 ms 51 ms 50 ms ae-17.r05.lsanca03.us.bb.gin.ntt.net [129.250.6.
180]
8 53 ms 52 ms 53 ms ae-0.att.lsanca03.us.bb.gin.ntt.net [129.250.9.6
]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 *... runs all the way to 30 with results timed out

Results from website tracert:

Tracing route to 12.129.254.184 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 7 ms 7 ms 10.33.224.1
3 7 ms 7 ms 7 ms COX-68-12-9-80-static.coxinet.net [68.12.9.80]
4 9 ms 8 ms 8 ms COX-68-12-19-152-static.coxinet.net [68.12.19.15
2]
5 55 ms 55 ms 56 ms langbbrj01-ae2.rd.la.cox.net [68.1.1.14]
6 54 ms 58 ms 54 ms ae-7.r00.lsanca19.us.bb.gin.ntt.net [129.250.194
.165]
7 50 ms 51 ms 50 ms ae-17.r05.lsanca03.us.bb.gin.ntt.net [129.250.6.
180]
8 53 ms 52 ms 53 ms ae-0.att.lsanca03.us.bb.gin.ntt.net [129.250.9.6
]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 *

New Contributor

 • 

2 Messages

I've been having some issues randomly DCing from Blizzard servers as well lately. I can't give any numbers at the moment since it's currently working, but every night it's been DCing for a couple of minutes.

Valued Contributor III

 • 

4.2K Messages

That tracert is normal. The request time outs happen after hitting ntt.net, which is where you hit Blizzard's firewall. What is odd is when I do a tracert I get something different. My tracert is different then I normally see it. I have no problems getting to blizzard (don't play any blizzard games right now). Try changing DNS to 8.8.8.8 and 8.8.4.4 and see if any difference. If you need instructions how, just reply with your OS.

Tracing route to 12.129.254.184 over a maximum of 30 hops

1 1 ms 1 ms 1 ms router.asus.com [192.168.1.1]
2 8 ms 9 ms 9 ms 10.2.x.x
3 8 ms 9 ms 8 ms ip98-190-160-114.ri.ri.cox.net [98.190.160.114]

4 30 ms 10 ms 12 ms ip98-190-33-123.ri.ri.cox.net [98.190.33.123] (Rhode Island Cox)
5 197 ms 92 ms 93 ms langbbrj01-ae2.rd.la.cox.net [68.1.1.14] (Calofornia Cox)
6 126 ms 92 ms 95 ms ae-7.r00.lsanca19.us.bb.gin.ntt.net [129.250.194
.165]
7 93 ms 96 ms 100 ms ae-17.r05.lsanca03.us.bb.gin.ntt.net [129.250.6.
180]
8 91 ms 89 ms 90 ms ae-0.att.lsanca03.us.bb.gin.ntt.net [129.250.9.6
]
9 93 ms 93 ms 93 ms cr2.la2ca.ip.att.net [12.122.129.234]
10 185 ms 93 ms 120 ms gar29.la2ca.ip.att.net [12.122.129.241]
11 235 ms 107 ms 90 ms 12.122.251.190
12 191 ms 211 ms 211 ms 206.16.68.46
13 * * * Request timed out.
14 * * * Request timed out.
15 ^C

"Because of the safeguards that protect our Battle.net servers, you may notice later hops in your trace route failing with an error message such as 'Request Timed Out' or 'Destination Net Unreachable'. You may also see inflated latency numbers. You can ignore any error messages you receive after contacting our servers as they do not indicate a problem with your internet connection. To identify our servers, look for the following suffixes: attens.netatt.netalter.net, telia.net."

https://us.battle.net/support/en/article/performing-a-traceroute

Recent Discussions

View More

Loading...