24 replies to this topic

[eli]

Recently, pings for most Australians on the NA server have jumped from ~275 to around ~525, which is basically unplayable. Any idea why?

Edited by eli, 21 January 2016 - 10:44 PM.

[Bonger Bob]

likely telco problems causing your data traffic to go through a bad route.

run a ping test, call your telco and complain.

[Carl Vickers]

A while ago I had a similar issue and it turned out my ISP had put some backup routes in and they somehow got turned to default routes.

This meant that instead of the signal going from Perth to SA to VIC to NSW then across the big blue sea to US, it instead went to Hong Kong then Japan then across the big blue sea to USA.

Do a tracert mwomercs.com. this will tell you the route and if it seem wrong speak to your ISP.

Disclaimer - the tech support of your ISP may be useless like mine was and said they had nothing to do with the routes which I proved wrong but I had an internal contact help get it sorted.

[tangles 253]

yeah ive got the same issue as of this week.

so you recon just ring em up and ask and ask and pester?

Im with telstra in melbourne btw

[eli]

Tracert:

1 1 ms 1 ms 2 ms dsldevice.gateway [10.0.0.138]
2 3 ms 2 ms 2 ms 58.162.26.193
3 3 ms 3 ms 6 ms 144.130.210.209
4 20 ms 14 ms 17 ms bundle-ether10.exi-core10.melbourne.telstra.net [203.50.11.109]
5 21 ms 20 ms 24 ms bundle-ether12.chw-core10.sydney.telstra.net [203.50.11.124]
6 20 ms 21 ms 20 ms bundle-ether1.oxf-gw11.sydney.telstra.net [203.50.6.93]
7 * 22 ms 18 ms bundle-ether1.sydo-core03.sydney.reach.com [203.50.13.98]
8 200 ms 199 ms 203 ms i-0-2-0-2.tlot-core01.bx.telstraglobal.net [202.84.140.225]
9 268 ms 267 ms 267 ms i-0-4-0-6.tnrt-core01.bi.telstraglobal.net [202.40.149.145]
10 340 ms 346 ms 347 ms i-0-3-0-2.ulhc-core01.bx.telstraglobal.net [202.84.143.230]
11 377 ms 374 ms 373 ms i-0-0-0-5.ulco01.bi.telstraglobal.net [202.84.178.10]
12 * * * Request timed out.
13 530 ms 530 ms 530 ms sbg-g2-a9.fr.eu [37.187.232.94]
14 530 ms 530 ms 533 ms sbg-g5-a9.fr.eu [37.187.36.155]
15 * * * Request timed out.
16 534 ms 526 ms 525 ms mwomercs.com [192.99.109.192]

Looks like it's routing through Europe? =O

Edited by eli, 21 January 2016 - 11:04 PM.

[tangles 253]

exactly the same as mine

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

1 <1 ms <1 ms <1 ms dsldevice.gateway [10.0.0.138]
2 * * * Request timed out.
3 19 ms 20 ms 18 ms 144.130.211.210
4 19 ms 20 ms 20 ms bundle-ether12.win-core10.melbourne.telstra.net [203.50.11.111]
5 31 ms 31 ms 33 ms bundle-ether12.ken-core10.sydney.telstra.net [203.50.11.122]
6 31 ms 33 ms 31 ms bundle-ether1.pad-gw11.sydney.telstra.net [203.50.6.61]
7 31 ms 31 ms 31 ms bundle-ether1.sydp-core04.sydney.reach.com [203.50.13.90]
8 175 ms 174 ms 175 ms i-0-3-0-5.paix-core01.bx.telstraglobal.net [202.84.144.157]
9 173 ms 173 ms 174 ms i-0-5-0-4.paix02.bi.telstraglobal.net [202.40.149.122]
10 203 ms 173 ms 173 ms xe-5-3-0.paloalto2.pao.seabone.net [195.22.206.129]
11 250 ms 258 ms 258 ms et-10-1-0.miami15.mia.seabone.net [89.221.41.175]
12 251 ms 257 ms 251 ms et-4-3-0.miami15.mia.seabone.net [195.22.199.177]
13 * 436 ms * mia-1-6k.fl.us [178.32.135.208]
14 445 ms 445 ms 446 ms nwk-5-a9.nj.us [198.27.73.201]
15 444 ms 442 ms 444 ms bhs-g2-a9.qc.ca [192.99.146.101]
16 444 ms 443 ms 443 ms bhs-g5-a9.qc.ca [198.27.73.233]
17 441 ms 442 ms 442 ms mwomercs.com [192.99.109.192]

Trace complete.

It goes

Melb
*somewhere in mid south Aus*
Hong kong
Paris France
then Montreal canada

seems like the long way round ay

[tangles 253]

just got off the phone with the almighty 'T'

no one could help me because it was beyond their knowledge and qualifications. they did take a fair bit of talking too to be brought up to speed (haha, punny) on what the problem was and what was going on. the 'manager' at the time was on the same page a lot fatser, but couldn't do anything. unless i engaged the services of a personal technician at the one off rate of 120 per issue, or an extra 12 a month for 24 months. i opted for a no but thanks.

The short salty story is no one knows why its happening however, i can PAY to have one of their technicians fix their routing problem.

anywho, any ideas?

[Carl Vickers]

You should be able to log a ticket to get passed to their network team, supply the details and they pass it up the chain, no site engineer needed

[Wintersdark]

Telstra (sp?) Is having a hardware problem with their Aussie:North America routing, and ping times are much higher as a result. It's not using the normal route as a result, a longer backup route.

Anyways, an Aussie friend of mine was talking about it today after spending a looking time on the phone with them.


This means while you can lodge tickets/make complaints, ultimately you're just going to have to wait for the issue to get fixed.

[eli]

Almost a week later - status update: Still rooted.

[Bonger Bob]

yup, being fingered by telstra is issue #1.

go with any provider that is / uses OPTUS for international data connections. They own the fiber undersea cable that hops from Perth to south east asia, so it goes on a cleaner route than telstra's back-up bullshite. Though in saying that it means OPTUS are getting your money, directly or otherwise and that is evil to the extreme .......

rock and a hard place....

[Oderint dum Metuant]

This isn't the first time Telstra have had poor routing issues there a couple of threads on steam- but those plebs wont believe its down to ISP.

Try experimenting with some VPN services, they will route your traffic along different paths, they will improve your ping and also give you more ammo to throw at Telstra.

[Selbatrim]

Happy to hear I am not alone. I'm routed same way to Canada but interestingly not to sites in California.

Logged the complaint and was told to suck it up. Rest of you still having the same problems?

[SQW]

I'm with TPG in Melb and NA server is usually 250-300 pin ever since I got this game 2 months ago.

No problem so far. Sometimes the servers are unstable and I get disconnected often on a particular day but usually when I do have a stable connection, the game works fine.

[Troutmonkey]

1 2 ms 1 ms 2 ms www.routerlogin.com [192.168.1.1]
2 33 ms 31 ms 33 ms lns20.adl6.on.ii.net [redacted]
3 35 ms 38 ms 32 ms ae9.cr1.adl2.on.ii.net [redacted]
4 52 ms 54 ms 52 ms ae16.br1.syd4.on.ii.net [150.101.33.188]
5 199 ms 198 ms 199 ms te0-1-1-3.br2.lax1.on.ii.net [150.101.33.195]
6 216 ms 214 ms 200 ms ovh.as16276.any2ix.coresite.com [206.72.210.214]
7 258 ms 260 ms 259 ms nwk-5-a9.nj.us [198.27.73.165]
8 270 ms 271 ms 270 ms bhs-g2-a9.qc.ca [192.99.146.101]
9 269 ms 270 ms 273 ms bhs-g5-a9.qc.ca [198.27.73.233]
10 268 ms 272 ms 269 ms mwomercs.com [192.99.109.192]

Seems like a much more sensible way to get there
- From Adelaide with Internode

[Imperius]

http://www.theregist...t_connectivity/

This is most of your issue I'm sure, be glad you can connect

[Karamarka]

i get 260 to canada. plz make server west coast

even better is 360 to oceanic....

loool

I get WORSE to OCE then Canada.

[Oderint dum Metuant]

Main cables cut, and Telstra has always had issue with routing and overloaded hops.

[PocketYoda]

DV McKenna, on 10 February 2016 - 02:44 AM, said:

Main cables cut, and Telstra has always had issue with routing and overloaded hops.

Any source on this..

Also yep same here NA is unplayable for me as is EU

[Oderint dum Metuant]

Samial, on 10 February 2016 - 03:29 AM, said:

Any source on this..

Also yep same here NA is unplayable for me as is EU

To which bit? The article on the cable cut is like 3 posts up