Technical Support
This is day 6 of my Disconnect ……Your people blame my Ip and my people blame you. I see in the threads fellow members with the exact same problem heres my trace route……

1 shalu ( 10.678 ms 5.499 ms 9.846 ms
2 ( 29.991 ms 9.113 ms 19.584 ms
3 d207-216-192-254.bchsia.telus.net ( 19.974 ms 29.431 ms 71.326 ms
4 ( 28.721 ms 28.512 ms 30.169 ms
5 ( 39.833 ms 40.009 ms 39.296 ms
6 te7-4.ccr02.sea02.atlas.cogentco.com ( 140.401 ms 211.474 ms 207.996 ms
7 te4-8.ccr02.sea01.atlas.cogentco.com ( 39.933 ms
te9-3.ccr02.sea01.atlas.cogentco.com ( 39.472 ms
te2-7.ccr02.sea01.atlas.cogentco.com ( 39.871 ms
8 te0-7-0-4.ccr21.slc01.atlas.cogentco.com ( 69.085 ms
te0-7-0-10.ccr21.slc01.atlas.cogentco.com ( 57.307 ms 61.701 ms
9 te7-2.ccr01.den01.atlas.cogentco.com ( 200.317 ms
te8-2.ccr02.den01.atlas.cogentco.com ( 119.611 ms
te9-1.ccr02.den01.atlas.cogentco.com ( 161.206 ms
10 te0-2-0-7.ccr21.mci01.atlas.cogentco.com ( 93.370 ms
te0-3-0-7.ccr21.mci01.atlas.cogentco.com ( 95.567 ms
te0-4-0-3.ccr21.mci01.atlas.cogentco.com ( 108.565 ms
11 te0-3-0-7.ccr22.ord01.atlas.cogentco.com ( 99.798 ms
te0-4-0-3.ccr21.ord01.atlas.cogentco.com ( 98.401 ms
te0-2-0-3.ccr21.ord01.atlas.cogentco.com ( 98.854 ms
12 te0-1-0-3.ccr22.ord03.atlas.cogentco.com ( 98.777 ms
te0-1-0-1.ccr22.ord03.atlas.cogentco.com ( 99.624 ms
te0-6-0-7.ccr22.ord03.atlas.cogentco.com ( 98.798 ms
13 ( 109.638 ms
att.ord03.atlas.cogentco.com ( 106.304 ms ( 101.050 ms
14 cr2.cgcil.ip.att.net ( 110.071 ms
cr1.cgcil.ip.att.net ( 109.440 ms 129.380 ms
15 gar3.cgcil.ip.att.net ( 109.930 ms
gar2.clboh.ip.att.net ( 182.027 ms 203.698 ms
16 ( 133.775 ms 139.298 ms ( 136.380 ms
17 ( 101.883 ms 110.845 ms 109.955 ms
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
As you can see clearly the time out at the 17th hop at YOUR Ip (…..I demand that blizzard take responsibility of this issue and stop !@#$ing around their dedicated patrons!

Just a heads up, its normal to have timeouts at that 63.240.... thats your destination.
Then how come i disconnect……6 days and no one still won't take responsibility……I'm getting sooooo down…..
01/13/2013 08:15 PMPosted by Apikapak
Just a heads up, its normal to have timeouts at that 63.240.... thats your destination.

Not exactly. But it is Blizzard's firewall, and only specific traffic can make it past there - pings are not part of that specific traffic. As such, no ping or trace to a Blizzard server will ever return anything past here.

te0-6-0-7.ccr22.ord03.atlas.cogentco.com ( 98.798 ms
13 ( 109.638 ms

This is why you're disconnecting, even though the results are perfectly normal in this report. It's not something specific to your ISP, but it's also not anything within Blizzard's network. It's a point in between them - specifically at the link between Cogentco and AT&T.

What is particularly interesting about your report, however, is that it seems the link is inconsistent - the three checks for what should be that link shows three different servers, one of which is actually back within Cogentco's network. I could understand being connected to three different servers on the subnet, but bouncing back a network is just plain odd.

Vulgar language and random demands won't change the fact that Blizzard has no authority over the network link where the issue is occurring, nor the networks on either side of it. Given the number of recent reports on the issue the chances of Blizzard doing nothing about it are slim, but they're acting as a 3rd party rather than a customer since it is not their network and they may not have the clout you want them to.
Ahhhh thats just how I need to express how feel on this subject nobody has or can't do anything on this matter so what the hell am i suppose to do ….scratch myself and stare at the disconnect icon for another 6 days….gawd i might just puke! thank you very much for your info though….thanks… what now, good grief I'm grieving
I've had limited success using a trial for ReduceTheLag (30 days, no charge - they just want an e-mail address). Though these are always of questionable value for their latency reduction services, and even a potential breeching point, they do at least alter the routing in some way which has turned an unplayable connection into a fairly stable one (albeit with the occasional "blank" period where I get about 20 seconds of nothing, followed by a quick catch-up).

YMMV, but it's free - worth a shot.
01/13/2013 08:07 PMPosted by Heavyreams
1 shalu ( 10.678 ms 5.499 ms 9.846 ms

This first hop is a little concerning as well. That is your computer to router/modem hop. If you are hardwired it should be showing <1ms (less than a ms). If you are on wireless 1 or 2 ms would be okay. You should look into that - if signal starts out bad it just gets compounded down the line.

You could try a power cycle and see if it improves.

Here's how to power cycle:

1. Turn off all computers on the network
2. Unplug the power from the modem and the router (if applicable)
3. Wait about 1-2 minutes
4. Plug in the modem first and wait for it to completely boot up
5. If there was a router, plug the power back in and wait for it to completely boot up
6. Turn on the computer and try the game out

If that doesn't work try flushing the DNS:

Its cogentco throttling your connection.I have the same problem.I am from saskatchewan Canada.Nobody can do !@#$ all.My ISP is fine right until it hits cogentco and blizzard's end is fine.Its those %^-*heads at cogentco crimping the line.Welcome to the new world of the internet.File your complaint http://www.ccts-cprst.ca/

Join the Conversation

Return to Forum