Topic SEA servers are twice as laggy as NA servers
Feynman #569
Feynman
Edited by Feynman on 5/5/11 8:00 PM (PDT)
I'm on Optus cable. These traces were taken at the same time (one immediately after the other) with no other traffic on the network.

SEA: 400-500ms
traceroute to sea.battle.net (202.9.66.38), 64 hops max, 52 byte packets
1 0.0.0.0 (0.0.0.0) 10.590 ms 10.177 ms 11.961 ms
2 riv3-ge5-1-5.gw.optusnet.com.au (198.142.163.33) 8.868 ms 10.755 ms 13.029 ms
3 bla1-ge5-0-0-906.gw.optusnet.com.au (211.29.125.41) 11.597 ms 10.848 ms 18.337 ms
4 bla5-ge5-0.gw.optusnet.com.au (211.29.125.245) 11.946 ms 12.538 ms 10.778 ms
5 203.208.131.57 (203.208.131.57) 171.214 ms 169.942 ms 170.509 ms
6 ge-1-0-0-0.laxow-cr2.ix.singtel.com (203.208.149.118) 170.697 ms
xe-1-1-0-0.laxow-dr3.ix.singtel.com (203.208.149.122) 172.096 ms 169.936 ms
7 pos3-7.sngtp-ar2.ix.singtel.com (203.208.172.17) 283.386 ms
so-4-2-0-0.toknf-cr3.ix.singtel.com (203.208.154.121) 412.037 ms 278.081 ms
8 i-0-0-3-peer.siko02.pr.reach.com (210.57.59.201) 647.566 ms 353.285 ms 351.228 ms
9 i-1-1-0.siko-core01.bi.reach.com (202.84.219.37) 522.211 ms 425.788 ms 482.500 ms
10 i-10-2.hkhh-core01.bx.reach.com (202.84.141.221) 619.114 ms 346.572 ms 567.874 ms
11 i-5-1.6ntp-core02.bx.reach.com (202.84.143.57) 613.713 ms 357.373 ms 564.861 ms
12 i-0-2-0-0.6ntp02.bi.reach.com (202.84.243.86) 358.994 ms 531.636 ms 614.295 ms
13 unknown.net.reach.com (202.126.173.182) 614.326 ms 600.865 ms 372.108 ms
14 202.79.192.182 (202.79.192.182) 549.288 ms 367.071 ms 538.927 ms
15 * * *


NA: 180-200ms
traceroute to us.battle.net (12.129.242.40), 64 hops max, 52 byte packets
1 0.0.0.0 (0.0.0.0) 16.909 ms 12.008 ms 10.030 ms
2 riv4-ge5-1-5.gw.optusnet.com.au (198.142.163.37) 11.452 ms 10.307 ms 13.793 ms
3 sbr5-ge6-1-0-908.gw.optusnet.com.au (211.29.126.25) 11.310 ms 11.707 ms 30.575 ms
4 sbr3-ge14-0.gw.optusnet.com.au (211.29.126.9) 12.574 ms 11.325 ms 14.529 ms
5 203.208.174.129 (203.208.174.129) 168.965 ms 171.088 ms 168.009 ms
6 te-4-2.car2.sanjose1.level3.net (4.79.42.229) 174.727 ms 172.084 ms 169.856 ms
7 ae-4-90.edge2.sanjose3.level3.net (4.69.152.209) 172.890 ms 195.394 ms 169.748 ms
8 192.205.32.205 (192.205.32.205) 171.279 ms 171.718 ms 423.219 ms
9 cr1.sffca.ip.att.net (12.122.86.90) 180.926 ms 180.720 ms 192.072 ms
10 cr1.la2ca.ip.att.net (12.122.3.122) 186.458 ms 181.879 ms 180.118 ms
11 cr83.la2ca.ip.att.net (12.123.30.109) 180.403 ms 183.122 ms 182.297 ms
12 gar5.la2ca.ip.att.net (12.122.128.25) 552.601 ms 210.488 ms 210.179 ms
13 12.122.255.74 (12.122.255.74) 179.661 ms 180.912 ms 182.061 ms
14 mdf001c7613r0003-gig-10-1.lax1.attens.net (12.129.193.242) 193.440 ms 181.892 ms 185.868 ms
15 * * *
Feynman #569
Feynman
This is still an issue, so not transient network latency.
Customer Service
Hi Feynman, we are working with Optus regarding this issue. The reason the latency from Optus to SEA SC2 server is high is because the traffic is being routed to US and back to SEA. Will keep you updated once we hear from Optus.
Feynman #569
Feynman
Crumbs, Optus drops the ball again. Thanks for your reply.
DoomBunnies #341
DoomBunnies
It has now been a full month since the last reply on this, EricL. Have you heard anything from Optus during this time?

Latest traceroutes:

367 ms to SEA.
traceroute to sea.battle.net (202.9.66.38), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 0.462 ms 0.356 ms 0.282 ms
2 10.60.0.1 (10.60.0.1) 11.285 ms 9.807 ms 10.989 ms
3 meb4-ge2-1-6.gw.optusnet.com.au (198.142.160.137) 9.935 ms 10.006 ms 8.257 ms
4 mas2-ge10-1-0-902.gw.optusnet.com.au (211.29.125.102) 26.338 ms 22.949 ms 23.584 ms
5 mas3-ge11-0.gw.optusnet.com.au (211.29.125.241) 23.171 ms 37.764 ms 25.134 ms
6 203.208.148.97 (203.208.148.97) 186.220 ms 175.277 ms 175.267 ms
7 ge-0-0-0-0.laxow-dr1.ix.singtel.com (203.208.171.65) 171.779 ms
xe-0-0-0-0.laxow-dr3.ix.singtel.com (203.208.149.106) 176.103 ms
ge-0-0-0-0.laxow-dr1.ix.singtel.com (203.208.171.65) 173.413 ms
8 so-4-2-0-0.toknf-cr3.ix.singtel.com (203.208.154.121) 282.561 ms 273.083 ms
so-2-0-2-0.toknf-cr3.ix.singtel.com (203.208.151.58) 287.521 ms
9 i-0-0-3-peer.siko02.pr.reach.com (210.57.59.201) 227.537 ms 206.675 ms 207.697 ms
10 i-1-1-0.siko-core01.bi.reach.com (202.84.219.37) 213.126 ms 215.141 ms 210.943 ms
11 i-4-1.hkhh-core01.bx.reach.com (202.84.141.217) 346.616 ms 356.690 ms 343.494 ms
12 i-5-1.6ntp-core02.bx.reach.com (202.84.143.57) 379.967 ms 378.685 ms 380.481 ms
13 i-3-2.6ntp01.bi.reach.com (202.84.180.150) 387.908 ms 376.477 ms 387.534 ms
14 unknown.net.reach.com (202.126.173.182) 381.013 ms 372.467 ms 367.493 ms
15 27.111.222.65 (27.111.222.65) 363.386 ms 371.536 ms 367.532 ms
16 27.111.222.82 (27.111.222.82) 366.421 ms 366.907 ms 362.560 ms
17 * * *


193 ms to NA
traceroute to us.battle.net (12.129.242.40), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 0.479 ms 0.240 ms 0.232 ms
2 10.60.0.1 (10.60.0.1) 9.869 ms 8.762 ms 10.254 ms
3 meb3-ge2-1-6.gw.optusnet.com.au (198.142.160.133) 7.880 ms 9.237 ms 9.108 ms
4 sbr4-ge6-1-0-904.gw.optusnet.com.au (211.29.125.114) 21.822 ms 22.659 ms 21.541 ms
5 sbr2-ge5-0.gw.optusnet.com.au (211.29.125.253) 22.833 ms 23.391 ms 24.390 ms
6 203.208.190.125 (203.208.190.125) 182.301 ms 175.672 ms 201.769 ms
7 te-4-2.car2.sanjose1.level3.net (4.79.42.229) 182.534 ms 173.567 ms 177.905 ms
8 ae-2-70.edge2.sanjose3.level3.net (4.69.152.81) 186.741 ms 187.493 ms 179.663 ms
9 192.205.32.205 (192.205.32.205) 194.023 ms 175.670 ms 176.589 ms
10 cr1.sffca.ip.att.net (12.122.86.90) 189.323 ms 180.086 ms 193.742 ms
11 cr1.la2ca.ip.att.net (12.122.3.122) 178.860 ms 186.603 ms 182.482 ms
12 cr83.la2ca.ip.att.net (12.123.30.109) 177.366 ms 179.238 ms 190.331 ms
13 gar5.la2ca.ip.att.net (12.122.128.25) 192.391 ms 211.335 ms 202.436 ms
14 12.122.255.74 (12.122.255.74) 177.399 ms 177.808 ms 183.994 ms
15 mdf001c7613r0003-gig-10-1.lax1.attens.net (12.129.193.242) 178.652 ms 178.703 ms 192.820 ms
16 * * *


Playing on SEA becomes completely impossible for me after about 6pm, as the whole battle.net interface suddenly loads very slowly, often leaving me at completely blank screens, and with achievement service popping in and out almost at random.

NA continues to work normally.

Am now seriously considering giving up on the SEA server and starting fresh over on NA, instead. Would miss my friends on the SEA server, though.
cozeh #138
cozeh
Yeah I've been experiencing these issues for a few months now, its a really woeful issue.

This compounds with the fact that us Aussies don't have any servers that can deliver < 30 ping like the US/Europe/Korea/Russia and pretty much anyone that plays SC2 (which is terrible for this day and age sadly).

Any kind of updates on this issue would be great as I love blizzard games but am always having to put up with average pings.

Cheers
onsRabbiT #787
onsRabbiT
I am with Optus and it still seems to be lagging in SEA server, the latency is ridiculous at times, often with 5 seconds delay between a key stroke and the action taking place.
InternetHero #494
InternetHero
Edited by InternetHero on 7/31/11 2:19 AM (PDT)
I am also with Optus in Brisbane with the same problem. ~400ms to sea.battle.net and about 200ms to us.battle.net.

Tracing route to sea.battle.net [202.9.66.38]
over a maximum of 30 hops:

1 <1 ms 9 ms 1 ms 192.168.1.1
2 26 ms 9 ms 15 ms 10.66.0.1
3 15 ms 11 ms 9 ms rdl1-ge5-1-3.gw.optusnet.com.au [198.142.163.233
]
4 22 ms 31 ms 21 ms mas1-ge13-0-0-904.gw.optusnet.com.au [211.29.125
.134]
5 56 ms 57 ms 71 ms mas3-ge2-0.gw.optusnet.com.au [211.29.125.237]
6 210 ms 215 ms 212 ms 203.208.148.97
7 186 ms 187 ms 193 ms ge-0-0-0-0.laxow-dr1.ix.singtel.com [203.208.171
.65]
8 313 ms 314 ms 318 ms POS3-7.sngtp-ar2.ix.singtel.com [203.208.172.17]

9 217 ms 213 ms 217 ms i-0-0-3-peer.siko02.pr.reach.com [210.57.59.201]

10 212 ms 211 ms 255 ms i-1-1-0.siko-core01.bi.reach.com [202.84.219.37]

11 373 ms 367 ms 386 ms i-3-2-0.hkhh-core01.bx.reach.com [202.84.144.161
]
12 * 404 ms 420 ms i-3-1-2.istt-core01.bx.reach.com [202.84.143.57]

13 373 ms 379 ms 373 ms i-0-0-7-0.6ntp-core02.bx.reach.com [202.84.243.6
]
14 393 ms 386 ms 379 ms unknown.net.reach.com [202.126.173.182]
15 387 ms 401 ms 389 ms 27.111.222.65
16 418 ms 420 ms 426 ms 27.111.222.82
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 * * ^C


Tracing route to us.battle.net [12.129.242.40]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 11 ms 10 ms 23 ms 10.66.0.1
3 8 ms 23 ms 9 ms rdl2-ge5-1-3.gw.optusnet.com.au [198.142.192.141
]
4 26 ms 37 ms 25 ms bla2-ge5-0-0-905.gw.optusnet.com.au [211.29.125.
146]
5 35 ms 24 ms 28 ms bla5-ge13-0.gw.optusnet.com.au [211.29.125.249]

6 181 ms 186 ms 184 ms 203.208.191.153
7 219 ms 224 ms 218 ms xe-10-0-0.edge5.LosAngeles1.Level3.net [4.59.48.
57]
8 182 ms 184 ms 197 ms ae-3-80.edge2.LosAngeles9.Level3.net [4.69.144.1
43]
9 209 ms 224 ms 222 ms 192.205.37.145
10 184 ms 196 ms 189 ms cr1.la2ca.ip.att.net [12.122.84.202]
11 197 ms 185 ms 183 ms gar10.la2ca.ip.att.net [12.122.104.45]
12 189 ms 183 ms 184 ms 12-122-254-226.attens.net [12.122.254.226]
13 199 ms 194 ms 197 ms 12.129.193.242
14 * 12.129.199.254 reports: Destination net unreachable.


I think everybody would love to have an update with this issue, doesn't matter whether there is progress or not, it shows there is somebody working on the problem.

cheers
PeteOZ #126
PeteOZ
I'm with optus in Melbourne and have been having the same lag issues as well. It is REALLY disappointing that this is making the game completely unplayable
ToRPezz #138
ToRPezz
PLEASE resolve this issue! I DESPERATELY want to play games on SEA but simply CANNOT because of absurd delay.

I beg you :(
Highlander #869
Highlander
There isn't progress and there isn't ever going to be progress until Optus make a major investment in their Australia to Asia/Europe infrastructure.

Blizzard can't resolve this. It has absolutely nothing to do with them.

Optus, unlike everyone else in Australia, reroutes via Los Angeles to get everywhere that isn't Australia. That means for all sites and servers in Europe or Asia will be significantly worse (Asia being the most noticable of course).

Telstra have a line that runs straight from Perth into South East Asia and most providers rent access to that cable. But not Optus.

You can see this visually here: http://www.cablemap.info/

The two main cable sets are the Southern Cross network from Sydney to North America which everyone uses, and the SEA-ME-WE lines from Perth to Singapore (where the SEA server is based) and beyond. Optus does not have access to the latter.

Harass Optus or change providers and tell them why.

I recommend iiNet, not only are they great, but they support uncapped downloads of the Day9 daily on their free downloads site. :D

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Click here to view the Forums Code of Conduct.

Report Post # written by
Reason
Explain (256 characters max)

Reported!

[Close]