69 replies to this topic

[Mike Forst]

One thing to note on that map is that all the grey lines are fibre lines that are still under construction. You can click on one and see when it is expected to enter service.

[SirLankyIII]

I see now, Telstra doesn't have a cable that runs right across the pacific, their line stops at Hawaii. So rather than paying Optus to use their Sydney to LA line, or piggy backing off the US-Japan cable from Hawaii, they go via Hong Kong and use one of the cheaper Asia-Pacific lines.

[Breeze]

A little bit of help would be great. I'm not familiar with these types of things at all.

I'm experiencing a huge jump in ping since the move... from an average of 250 to 390-500.

I'm trying to take a screenshot of the tracert, but I'm having some challenges. The tracert disappears the moment it finishes, so I don't even get a chance to screenshot it. Any suggestions on how I get it to stay on-screen?

Just looking at the locations it throws up, it looks like I'm going from Melbourne to Sydney to Tokyo to Singapore to Italy to France... the tracert screen disappears after this last one, on number 21...

I'm currently with iPrimus, which I think also uses Telstra lines. Thanks!

[Symbiodinium]

Breeze, on 14 September 2014 - 03:33 AM, said:

A little bit of help would be great. I'm not familiar with these types of things at all.

I'm experiencing a huge jump in ping since the move... from an average of 250 to 390-500.

I'm trying to take a screenshot of the tracert, but I'm having some challenges. The tracert disappears the moment it finishes, so I don't even get a chance to screenshot it. Any suggestions on how I get it to stay on-screen?

Use the command: tracert mwomercs.com > C:/out.txt

That will create the result as a text file on the C: drive.

[M a y h e m]

Thanks Jon, ping was better before the move but can live with sub 100ms pings.

Jon Cunningham, on 12 September 2014 - 06:49 PM, said:

That's fine - many routers start dropping pings, especially if they are under load, because they're focusing on delivering the other content. If that router dropped "100%" of all packets traveling through it, you wouldn't even be able to reach the subsequent steps of the path, let alone our website!

So long as *your* ping time is fine (it is; 85 ms is slightly better than what we get in the office, which is 87) and your actual packets aren't getting dropped / gameplay isn't being affected, you're good!

[Breeze]

Symbiodinium, on 14 September 2014 - 04:09 AM, said:

Use the command: tracert mwomercs.com > C:/out.txt

That will create the result as a text file on the C: drive.

Thanks very much!

My trace with iPrimus

Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 28 ms 27 ms 29 ms lo0.melbras18.mel.iprimus.net.au [202.138.4.81]
3 30 ms 29 ms 28 ms ae4-vlan11.per01.melbpri.vic.m2core.net.au [203.134.26.193]
4 30 ms 30 ms 27 ms ae10.csr01.melbpri.vic.m2core.net.au [203.134.24.9]
5 39 ms 40 ms 43 ms xe-2-2-0.csr02.masceqx.nsw.m2core.net.au [203.134.2.241]
6 42 ms 41 ms 38 ms ae3.bsr01.masceqx.nsw.m2core.net.au [203.134.2.254]
7 55 ms 39 ms 38 ms ae4.csr01.masceqx.nsw.m2core.net.au [203.134.2.233]
8 161 ms 161 ms 161 ms ge-1-0-0.bsr01.tokyeqx.m2core.net.au [203.134.2.122]
9 250 ms 248 ms 248 ms ge-100-0-0-2.r00.tokyjp03.jp.bb.gin.ntt.net [61.213.160.5]
10 237 ms 237 ms 235 ms ae-0.r22.tokyjp01.jp.bb.gin.ntt.net [129.250.5.28]
11 304 ms 303 ms 302 ms ae-3.r21.sngpsi05.sg.bb.gin.ntt.net [129.250.7.35]
12 295 ms 300 ms 300 ms ae-13.r00.sngpsi02.sg.bb.gin.ntt.net [129.250.4.74]
13 287 ms 378 ms 295 ms ae-13.r00.sngpsi02.sg.bb.gin.ntt.net [129.250.4.74]
14 333 ms 302 ms 337 ms ae-13.r00.sngpsi02.sg.bb.gin.ntt.net [129.250.4.74]
15 400 ms 294 ms 289 ms ae0.singapore2.sin.seabone.net [93.186.133.12]
16 412 ms * * xe-3-0-3.milano51.mil.seabone.net [195.22.205.111]
17 394 ms 390 ms * sbg-g1-a9.fr.eu [91.121.128.80]
18 * * * Request timed out.
19 388 ms * 392 ms 37.187.36.153
20 * * 389 ms 37.187.36.153
21 395 ms * * mwomercs.com [192.99.109.192]
22 * 385 ms 390 ms mwomercs.com [192.99.109.192]

[Joseph Mallan]

Ultimatum X, on 12 September 2014 - 09:06 PM, said:

This thread is not only amazing, watching these folks work out this issue - but also informative on a subject of which I have zero knowledge.


5/5.

MW:O has been sorely missing this kind of communication and assistance. Thank You gentlemen.

[N0MAD]

SirLankyIII, on 12 September 2014 - 10:29 PM, said:

I see now, Telstra doesn't have a cable that runs right across the pacific, their line stops at Hawaii. So rather than paying Optus to use their Sydney to LA line, or piggy backing off the US-Japan cable from Hawaii, they go via Hong Kong and use one of the cheaper Asia-Pacific lines.

Err im a telstra customer, im not being routed to EU how does that work?. and ummm Optus uses Telstra hardware and lines.
So its optus paying telstra not the other way around..

[Mavairo]

repete, on 11 September 2014 - 08:29 PM, said:

Thanks for the update. 250ms ping from NZ, both before and after the move. I'd hate to see what it looked like if Telstra and Comcast had a baby.

I think the child would be dial up...

[Breeze]

Is there any update on the network path issues for players in Australia? My path is still going through Europe...

[MarineTech]

Mike....

As a sysadmin myself with 16 years of experience in IT Systems & Operations, I am feel I am required to speak up here.

You are seriously pressing up against BOFH regulations against giving "Forbidden Information" to your user base.

It's not what we do FOR our users, it's what we do TO our users.

Edited by MarineTech, 17 September 2014 - 08:01 AM.

[Killercage]

from Japan

tracert 192.99.40.106

Tracing route to ns7000227.ip-192-99-40.net [192.99.40.106]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 14 ms 16 ms 18 ms 122.1.247.101
3 20 ms 19 ms * 122.1.247.97
4 14 ms 14 ms 16 ms 118.23.12.13
5 7 ms 9 ms 8 ms 61.207.25.49
6 20 ms 19 ms 16 ms 125.170.97.49
7 25 ms 26 ms 27 ms 60.37.27.153
8 * 21 ms 23 ms ae-5.r21.tokyjp05.jp.bb.gin.ntt.net [129.250.11.53]
9 18 ms 18 ms 19 ms ae-0.r24.tokyjp05.jp.bb.gin.ntt.net [129.250.6.96]
10 23 ms 23 ms 29 ms ae-6.r23.tokyjp01.jp.bb.gin.ntt.net [129.250.3.158]
11 103 ms 83 ms 90 ms as-1.r20.sngpsi02.sg.bb.gin.ntt.net [129.250.6.121]
12 83 ms 82 ms 82 ms ae-0.r20.sngpsi05.sg.bb.gin.ntt.net [129.250.3.145]
13 82 ms 84 ms 82 ms ae-2.r21.sngpsi05.sg.bb.gin.ntt.net [129.250.7.23]
14 89 ms 90 ms 89 ms ae-13.r00.sngpsi02.sg.bb.gin.ntt.net [129.250.4.74]
15 82 ms 94 ms 85 ms ae0.singapore2.sin.seabone.net [93.186.133.12]
16 290 ms 291 ms * xe-2-2-0.milano51.mil.seabone.net [195.22.192.101]
17 * 295 ms * mil-1-6k.it.eu [213.186.32.213]
18 294 ms * * mil-5-6k.it.eu [94.23.122.251]
19 * * * Request timed out.
20 300 ms 302 ms 289 ms rbx-g2-a9.fr.eu [94.23.122.117]
21 * * * Request timed out.
22 * * * Request timed out.
23 831 ms 812 ms 807 ms bhs-g2-6k.qc.ca [198.27.73.207]
24 321 ms 319 ms 322 ms bhs-s3-6k.qc.ca [198.27.73.142]
25 335 ms 317 ms 317 ms ns7000227.ip-192-99-40.net [192.99.40.106]

[Clit Beastwood]

I spent 4 hours on the phone with my ISP- showed screenshots, graphs demonstrating packet loss, etc. - their only solution was "we can send a technician out to your home". It's really hard to explain routing issues to "level 3 tech support" whom does not understand basic routing. It's not the latency, it's the huge drop in registered hits. I rarely even drop with a serious group anymore because I look like an a-hole putting down under 300 damage drop after drop. Still getting kills on targets I work, but it's like I'm not getting credit for the damage I do. Gauss works ok, missiles are iffy, and lasers are a total waste of time. I called every ISP i could find that might offer service here. 768k DSL or the time warner connection I already have are the only options. Move the servers back
(Not really, I'm glad ping got better for a lot of you guys!)

Edited by Fierostetz, 18 September 2014 - 06:35 AM.

[Clit Beastwood]

Fwiw, ping zapper has helped a bit. Can't get wtfast to work with mwo (disconnects when dropping) but it's metrics show an improvement in link quality while doing stuff in the mechlab. Ping zapper has a free limited trial.

Edited by Fierostetz, 18 September 2014 - 06:41 AM.

[PASHA]

My tracert:

[DreadBlade81]

Hi

From the philippines.

Got a decent 250ms before moving the servers. Now its a worst 600 to 1000ms ping.

Below is my tracert

Tracing route to 192.99.109.129 over a maximum of 30 hops

1 7 ms 5 ms 5 ms firewall.secuban.local [192.168.3.1]
2 15 ms 17 ms 16 ms dsl.49.146.128.1.pldt.net [49.146.128.1]
3 37 ms 15 ms 15 ms 122.2.159.29.static.pldt.net [122.2.159.29]
4 18 ms 14 ms 19 ms 210.213.131.66.static.pldt.net [210.213.131.66]
5 15 ms 13 ms 13 ms 210.213.133.49.static.pldt.net [210.213.133.49]
6 189 ms 188 ms 188 ms if-5-0.mcore5.LAA-Los-Angeles.as6453.net [209.58.33.77]
7 192 ms 190 ms 201 ms if-9-3-1-14.tcore2.LVW-Los-Angeles.as6453.net [209.58.33.142]
8 193 ms 192 ms 192 ms if-3-2.tcore1.SQN-San-Jose.as6453.net [63.243.205.13]
9 189 ms 193 ms 189 ms if-1-2.tcore2.SQN-San-Jose.as6453.net [63.243.205.2]
10 * * * Request timed out.
11 363 ms 210 ms 192 ms 198.27.73.249
12 * * * Request timed out.
13 * * * Request timed out.
14 258 ms 256 ms 257 ms bhs-g1-6k.qc.ca [198.27.73.5]
15 258 ms 257 ms 261 ms 198.27.73.231
16 258 ms 259 ms 258 ms 192.99.109.129

Trace complete.

Thanks. Kudos for the team for their hard work

[KharnZor]

Past, on 11 September 2014 - 08:28 PM, said:

Telstra being called out as crap by people from all the way from Canada amuses me greatly. Good luck getting them to do anything if there's no profit in it for them.

If any Aussies looking to jump ship i can tell you my ping with Internode wasn't affected by the move.

I'm one of the few on Telstra that has had no change to pings at all.
So yea, damn you mostly bad Telastra

[D0hle]

Just to keep this thread afloat, and because I'm not getting answers to my support ticket anymore, here is my trace route as well:

1 7 ms 6 ms 5 ms 1252026-JIMMS [0.0.0.0]
2 6 ms 6 ms 6 ms hel5-sr3.dnaip.fi [62.78.106.166]
3 7 ms 5 ms 9 ms hel5-tr3.dnaip.fi [62.78.107.116]
4 19 ms 15 ms 16 ms rai1-tr1.dnaip.fi [62.78.107.13]
5 15 ms 15 ms 23 ms tuk2-sr1.dnaip.fi [62.78.107.174]
6 16 ms 17 ms 16 ms te0-7-0-2.ccr21.sto01.atlas.cogentco.com [149.6.168.129]
7 63 ms 66 ms 66 ms level3.sto01.atlas.cogentco.com [130.117.14.6]
8 * * * Request timed out.
9 * * * Request timed out.
10 42 ms 39 ms 39 ms ae-46-46.ebr3.Frankfurt1.Level3.net [4.69.143.170]
11 * * * Request timed out.
12 39 ms 39 ms 40 ms ae-2-70.edge5.Frankfurt1.Level3.net [4.69.154.73]
13 * 50 ms * fra-5-6k.fr.eu [91.121.131.5]
14 56 ms 56 ms 54 ms sbg-g2-a9.fr.eu [91.121.128.125]
15 52 ms 54 ms 53 ms 37.187.36.155
16 * * * Request timed out.
17 * * * Request timed out.
18 147 ms 147 ms 145 ms mwomercs.com [192.99.109.192]

Curiously enough, I reside in Finland and my ping actually increased after the data center switch even though the data center moved physically closer to me. My ping used to be between 125 and 130, now it's between 145 and 150, sometimes jumping all the way up to 180 or even 220.

[General Solo]

Ping before the move was 245ms, with ok hit detection

Since the move 300ms plus

Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:
1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 28 ms 29 ms 29 ms TenGigE0-5-0-15.chw-edge901.sydney.telstra.net [139.130.111.73]
5 27 ms 32 ms 26 ms bundle-ether13.chw-core10.sydney.telstra.net [203.50.11.98]
6 28 ms 27 ms 32 ms Bundle-ether17.oxf-gw2.sydney.telstra.net [203.50.13.70]
7 35 ms 24 ms 31 ms bundle-ether1.sydo-core01.sydney.reach.com [203.50.13.38]
8 36 ms 27 ms 31 ms i-0-3-2-0.sydo-core02.bi.telstraglobal.net [202.84.220.189]
9 215 ms 189 ms 179 ms i-0-2-0-0.1wlt-core01.bx.telstraglobal.net [202.84.141.146]
10 454 ms 238 ms 329 ms i-0-4-0-2.eqla01.bi.telstraglobal.net [202.40.149.242]
11 171 ms 471 ms 177 ms tisparkle-peer.eqla01.pr.telstraglobal.net [134.159.61.26]
12 173 ms 399 ms 319 ms xe-5-1-0.paloalto2.pao.seabone.net [89.221.35.147]
13 * 189 ms 204 ms pal-5-6k.ca.us [178.32.135.206]
14 241 ms * * 198.27.73.188
15 * 245 ms 257 ms 198.27.73.175
16 249 ms 256 ms 319 ms bhs-g1-6k.qc.ca [198.27.73.1]
17 280 ms 319 ms 319 ms 198.27.73.231
18 542 ms 319 ms 319 ms mwomercs.com [192.99.109.192]
Trace complete.

[Reverendk]

Coming straight out of Texas, ping used to average between 70-90. Today mwo, and only mwo is giving me pings of 190-220, which makes maintaining the high elo life style to which I have become accustomed to difficult. Nothing in this traceroute appears particularly egregious, but I'm an expert in trigger pulling, not fiber opticing.




Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms ---.---.-.-
2 19 ms 17 ms 18 ms cpe-70-121-192-1.satx.res.rr.com [70.121.192.1]

3 12 ms 11 ms 14 ms tge1-0-0.snantx2000-10k1.satx.rr.com [24.28.133.
33]
4 14 ms 6 ms 12 ms tge0-10-0-3.snaptx1901r.texas.rr.com [24.175.33.
74]
5 16 ms 15 ms 13 ms agg22.snavtxuu02r.texas.rr.com [24.175.32.160]
6 30 ms 19 ms 23 ms agg23.hstqtxl301r.texas.rr.com [24.175.32.156]
7 15 ms 23 ms 15 ms 107.14.19.94
8 19 ms 18 ms 24 ms ae-0-0.cr0.dfw10.tbone.rr.com [66.109.6.39]
9 24 ms 25 ms 21 ms ae0.pr1.dfw10.tbone.rr.com [107.14.17.232]
10 22 ms 22 ms 23 ms ix-23-0.tcore2.DT8-Dallas.as6453.net [66.110.57.
97]
11 96 ms 94 ms * if-2-2.tcore1.DT8-Dallas.as6453.net [66.110.56.5
]
12 * * 93 ms if-10-3.tcore1.AEQ-Ashburn.as6453.net [66.198.15
4.117]
13 74 ms 70 ms 73 ms if-2-2.tcore2.AEQ-Ashburn.as6453.net [216.6.87.1
]
14 91 ms 90 ms 87 ms if-3-2.tcore2.NJY-Newark.as6453.net [216.6.87.10
]
15 * 103 ms * if-2-2.tcore1.NJY-Newark.as6453.net [66.198.70.1
]
16 * * * Request timed out.
17 106 ms 114 ms 109 ms bhs-g2-6k.qc.ca [198.27.73.207]
18 * * * Request timed out.
19 107 ms * * mwomercs.com [192.99.109.192]
20 111 ms 113 ms 105 ms mwomercs.com [192.99.109.192]

Edited by Reverendk, 30 September 2014 - 05:36 PM.