Get the Desktop App for Battle.net Now
- All your games in 1 place
- Log in once
- Automatic game updates
Same issue, seemigly random lag spikes and "waiting for server" dialogue boxes with the orange flashing boxes in bottom left saying disconnected/reconnected etc. Pausing the game seems to help.
1. Sky Broadband
2. Liverpool UK
3. FIbre Optic 40mbs!!!!!!!!
4. Traceroute to EU 126.96.36.199
1 192.168.0.1 (192.168.0.1) 1.442 ms 4.347 ms 0.950 ms
2 97e70003.skybroadband.com (188.8.131.52) 16.543 ms 17.813 ms 9.992 ms
3 0278098c.bb.sky.com (184.108.40.206) 21.418 ms 17.114 ms 22.329 ms
4 ip-84-38-37-94.easynet.co.uk (220.127.116.11) 19.589 ms 19.658 ms 17.207 ms
5 * * *
6 18.104.22.168 (22.214.171.124) 18.242 ms 17.763 ms 15.504 ms
7 ae-1-51.edge5.london1.level3.net (126.96.36.199) 15.481 ms
ae-2-52.edge5.london1.level3.net (188.8.131.52) 14.846 ms 14.596 ms
8 ldn-b5-link.telia.net (184.108.40.206) 13.875 ms
ldn-b5-link.telia.net (220.127.116.11) 83.295 ms 14.725 ms
9 ldn-bb1-link.telia.net (18.104.22.168) 15.052 ms
ldn-bb1-link.telia.net (22.214.171.124) 14.660 ms
ldn-bb1-link.telia.net (126.96.36.199) 17.023 ms
10 prs-bb2-link.telia.net (188.8.131.52) 22.299 ms
prs-bb1-link.telia.net (184.108.40.206) 22.404 ms
prs-bb1-link.telia.net (220.127.116.11) 28.159 ms
11 ffm-bb2-link.telia.net (18.104.22.168) 28.110 ms
ffm-bb1-link.telia.net (22.214.171.124) 28.121 ms
ffm-bb2-link.telia.net (126.96.36.199) 27.427 ms
12 ffm-b10-link.telia.net (188.8.131.52) 31.065 ms
ffm-b10-link.telia.net (184.108.40.206) 28.578 ms
ffm-b10-link.telia.net (220.127.116.11) 29.851 ms
Traceroute to 18.104.22.168:
1 * 192.168.0.1 (192.168.0.1) 1.783 ms 1.117 ms
2 97e70003.skybroadband.com (22.214.171.124) 2782.606 ms 278.743 ms 39.025 ms
3 0278098c.bb.sky.com (126.96.36.199) 22.733 ms 22.376 ms 16.090 ms
4 te0-1-0-7.er10.thlon.ov.easynet.net (188.8.131.52) 20.877 ms 15.180 ms 21.002 ms
5 * * *
6 184.108.40.206 (220.127.116.11) 39.578 ms *
18.104.22.168 (22.214.171.124) 15.241 ms
7 * * *
8 ldn-b5-link.telia.net (126.96.36.199) 15.056 ms
ldn-b5-link.telia.net (188.8.131.52) 16.418 ms
telia (184.108.40.206) 41.753 ms
9 ldn-bb2-link.telia.net (220.127.116.11) 40.396 ms
ldn-bb1-link.telia.net (18.104.22.168) 24.162 ms *
10 prs-bb2-link.telia.net (22.214.171.124) 22.380 ms
prs-bb2-link.telia.net (126.96.36.199) 22.588 ms
prs-bb1-link.telia.net (188.8.131.52) 22.861 ms
11 prs-b8-link.telia.net (184.108.40.206) 22.516 ms
prs-b8-link.telia.net (220.127.116.11) 22.608 ms
prs-b8-link.telia.net (18.104.22.168) 24.636 ms
Macbook Pro 13 inch late 2011 Processor 2.8 GHz Intel Core i7 Memory 4 GB 1333 MHz DDR3 Graphics Intel HD Graphics 3000 384 MB.
I don't know who is still following this, but I came here thinking ppl would discuss a hack :). Anyhow I had problems lagging out and my fsb would drop to 0 at times, unplayable so must be the graphics that Blizzard had set it to :) right? Blizzard had set everything to Ultra because my rig is pretty powerfull, so anyhow I notch them back doesn't really help much. A few days ago I installed something called Nvidia Experience and among other things it automatically sets optimal settings for SC2. So when I compared the two the biggest changes were Shaders and Shadows they went from Ultra to Low. So when I play in those setts I get hardly any lag or any Waiting to Surender screens, I can't explain why that is but maybe it's harder to communicate those bites? All I know is that it somehow helps me, as far as large games with my friends that's not even possible in Nvidia's recommended settings, after a while the game just lags so bad that you can't control anything anymore, there was another thread about fsb and they recommend to set the CPU priority for the SC2 process from normal to high, so I do that every game as well, and end the update process that always runs in the background.
So that's my story hope it might make someone go KLICK :)
as always gl hf all
Same issue on my end. Ever since the Hots release came out. I stopped playing for a few months. Came back. Did a CLEAN reformat on my computer, and totally wiped EVERY file. Installed Windows 7 fresh, all updates fresh. Installed my NVidia graphics drivers to most up to date and its doing the exact same. On very RARE days ill be able to play an entire game without the "waiting for server" screen. Then the next game it happens, usually every couple of minutes (give or take). One game I did note when it lagged and the "waiting for server" screen appeared. The entire game froze, but my music off of youtube did not skip a single beat one bit and had absolutely no pause or lag as if nothing happened to the internet connection, but a battle.net issue. Im running windows 7, GT 440 Graphics with 1gig of ddr5 ram, a dual core phantom II AMD and 4 gigs of ram. With the factory network card which is using Nvidia driver software. This is becoming troublesome and is very frustrating considering I cannot play a single game basically without lag. It's miserable and makes me not want to play starcraft ever again, because it feels like this wont be resolved. I use Charter Communications Cable internet with 30mbps of download and 4mbps upload, located in Massachusetts. Here is a tracer route.
Tracing route to 22.214.171.124 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 11 ms 19 ms 9 ms crr02wrcsma-tge-0-2-0-5.wrcs.ma.charter.com [126.96.36.199]
4 13 ms 10 ms 10 ms crr03oxfrma-tge-0-3-0-6.oxfr.ma.charter.com [188.8.131.52]
5 14 ms 14 ms 15 ms bbr01oxfrma-bue-1.oxfr.ma.charter.com [184.108.40.206]
6 10 ms 9 ms 9 ms bst-edge-05.inet.qwest.net [220.127.116.11]
7 15 ms 23 ms 15 ms jfk-brdr-04.inet.qwest.net [18.104.22.168]
8 16 ms 16 ms 25 ms 22.214.171.124
9 92 ms 104 ms 88 ms cr1.n54ny.ip.att.net [126.96.36.199]
10 100 ms 99 ms 84 ms cr2.cgcil.ip.att.net [188.8.131.52]
11 95 ms 88 ms 86 ms cr1.cgcil.ip.att.net [184.108.40.206]
12 87 ms 98 ms 91 ms cr2.dvmco.ip.att.net [220.127.116.11]
13 87 ms 84 ms 102 ms cr1.slkut.ip.att.net [18.104.22.168]
14 87 ms 86 ms 87 ms cr2.la2ca.ip.att.net [22.214.171.124]
15 84 ms 91 ms 83 ms gar20.la2ca.ip.att.net [126.96.36.199]
16 88 ms 113 ms 84 ms 188.8.131.52
17 87 ms 94 ms 84 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [184.108.40.206]
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.
Well it looks like I am the only one who actually knows what is going on here ;), at least I hope I do. If you are using wifi instead of being plugged in directly to the internet that is why you are getting the waiting for server screen.
One of the issues being reported all over the place is that the new macpro's seem to drop the connection to wifi rather frequently. As of yet I cannot find a solution to this problem and the only workaround that I have found is to turn your wifi off and then back on. When this happens to me during starcraft I simply do that and then I am able to go right back into the game.
A related issue that some of you guys might be having are games where your game seems to stutter. This can be caused by your wifi disconnecting during a match, but then reconnecting on its own before the surrender screen comes up. The fix for this is the same as the other which is to turn your wifi off then back on.
I have searched all over the place for a fix for the wifi dropping and as of yet I haven't found a single solution that works. I dont know what apple did with the new OS but this issue is yet to be fixed. Hopefully this will help you all out a bit, or at the very least show you where to aim your frustrations. If you are connected directly to your internet and having this issue I have no idea what the problem is.
Definitely not a mac issue...
Running win7, core i5, 16gb RAM and most importantly.... ETHERNET.
I'm from UK and play EU server.
I thought this problem was related to the 4v4 bug, but seems not. Between this connection issue and the other bug, 4v4 is unplayable!
I moved house in June, wondering whether it's an ISP problem. Will submit a trace when i get a few mins.
This is still happening. August 1st, 2013.
The "waiting for server" legend, comes up at the very end of the game. Even if you win, the message shows up, and then you are taken out, and it registers the match as a loss. It happens 5 in 10, but is frustating.
This was originated since the first patch introducing the new interface of HOTS. Programmers messed that up. It's clearly demonstrated. Go along all the comments and you will see it.
What I have found is that, when you win, don't click on the button of the points and results, wait like 5 secs, and then press it. Because if you do it immedeately it is guaranteed it will say the aforementioned legend and it will register the match as a loss.
Why has this not been fixed yet guys! You are Blizzard!
Check this out!
Edited by bernext on 8/1/2013 11:26 AM PDT
1 day ago no problem, the game running nicely since the beginning of time. since today i am getting "Waiting for server" screen in about 80% games at random times. Happens in Arcade, 1v1 AI, 4v4, etc.. My network is solid and superfast, the problem occurs at work location and at home also. Both PCs connected with cable, no wifi used.
Edited by Jerryno on 8/7/2013 5:24 PM PDT
Same has been happening to me. Consistently. No problems when I play on my PC...no problems doing anything else. No one else in the house experiences lag of any sort. I never lose FPS...it just stutters briefly and then the server error comes up.
This has been going on for awhile: http://us.battle.net/sc2/en/forum/topic/8197761877
I've done everything suggested on here and elsewhere...since June.
It is even worse playing 2v2. Because of this (anywhere from 3min to 25min into the game) I will drop.
1v1 it is about 1 in 5 games.
2v2 it is about 4 in 5 games.
Something else is going on and it has nothing to do with my connection.
Edited by sleep on 8/15/2013 12:07 AM PDT
Threats of violence. We take these seriously and will alert the proper authorities.
Harassing or discriminatory language. This will not be tolerated.