packet loss at 206.16.68.54 in trace route to us.battle.net

when other providers open today you can bet I'm calling them.

goodby Cox

Can you provide any details? You only gave the forum 12 hours to respond. Moderators generally try to wait for other members to post before they step in. Maybe start by providing the tracert? 9/10, with Blizzard, it's the peer Cox uses and how they connect to Blizzard's ISP. However, local ISP issues and network issues can play a role too. I play SC2 and HoTS, so your among friends. 

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 1036 | 1036 | 0 | 0 | 1 | 0 |
| 10.11.96.1 - 0 | 1045 | 1045 | 5 | 7 | 27 | 7 |
| 100.127.40.34 - 0 | 1045 | 1045 | 6 | 8 | 29 | 7 |
| 172.22.51.64 - 0 | 1045 | 1045 | 5 | 7 | 17 | 8 |
|port-channel201.car1.Richmond1.Level3.net - 0 | 1045 | 1045 | 8 | 36 | 240 | 142 |
| ae-106-3506.bar2.Tustin1.Level3.net - 1 | 1042 | 1041 | 71 | 73 | 126 | 73 |
| 192.205.37.145 - 0 | 1042 | 1042 | 74 | 78 | 98 | 79 |
| cr2.la2ca.ip.att.net - 0 | 1044 | 1044 | 73 | 76 | 97 | 76 |
| 12.123.249.73 - 0 | 1046 | 1046 | 74 | 76 | 104 | 81 |
| No response from host - 100 | 209 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 209 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 209 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 209 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 209 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 209 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 209 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 209 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 209 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 209 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 209 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 209 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 209 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 209 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 209 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 209 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 209 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 209 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 209 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 209 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 209 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

spending all morning trying to figure this out...

did trace routes to several battle.net ip addys

I'm waiting for some tech guy to say 

"jules, i got this...the calvery is on it's way"

jimbo812 said:
"jules, i got this...the calvery is on it's way"

This is a public forum. Its for users to help other users. A moderator may be able to give advice or even contact you to go further, but it is not direct support. No magic buttons here.

I don't see any super obvious signs of a issue. I also don't see any packet loss. What makes you think there is? Also, can you describe your symptoms? 

Digging around, I did see news of a major fiber cut that effected WA and CA starting 1-2 weeks ago. I also see 1 packet loss inside Level3 network. It's less then 1% packet loss, but if the data shows your issue, my guess would be there. More info would help.