Jump to content


Warning - do no use Orcon if you Game

Orcon Latency Ping Routing Problem

  • Please log in to reply
5 replies to this topic

Chewmatca #1 Posted 29 November 2017 - 12:30 PM

    Staff sergeant

  • Member
  • 16143 battles
  • 307
  • [RNS] RNS
  • Member since:
    11-04-2012

Have found after much investigating Orcon is not willing to update their routing to provide less latency. Currently getting 220ms via Orcon from NZ to WOT asia, when 120ms is attainable on their Gigabit Fibre Plan.

 

From Orcon:

 

As of the moment we cannot change the router path as our systems are configured to a standard for every Orcon customer.

Hopefully this information was helpful and please feel free to call us for additional inquiries

 

Kind regards,

Ron
TheTeam@Orcon

 

Standard? Standard slow internet...

 

Have sent one last email to request escalation to an engineer. If no luck, Ditching Orcon and happy to label them as Gamer Unfriendly.

 

Any recommendations for full gigabit net ISP from anyone in NZ?

 


Edited by Chewmatca, 29 November 2017 - 12:31 PM.


_BeNZene_ #2 Posted 29 November 2017 - 01:35 PM

    Corporal

  • Member
  • 25028 battles
  • 33
  • [DREAM] DREAM
  • Member since:
    11-03-2017

I take it that is 220ms to Singapore? Poor form by Orcon. 

 

I'm can't speak for full gigabit, but I have always had good latency (& everything else) on 2 Degrees fibre (formerly SNAP), using their 100/20 plan.



Hilly #3 Posted 29 November 2017 - 02:10 PM

    We always have room for someone with the right requirements

  • Council of Armored Forces
  • 11365 battles
  • 2,129
  • [PYRO] PYRO
  • Member since:
    11-19-2012

View PostChewmatca, on 29 November 2017 - 04:30 PM, said:

Have found after much investigating Orcon is not willing to update their routing to provide less latency. Currently getting 220ms via Orcon from NZ to WOT asia, when 120ms is attainable on their Gigabit Fibre Plan.

 

From Orcon:

 

As of the moment we cannot change the router path as our systems are configured to a standard for every Orcon customer.

Hopefully this information was helpful and please feel free to call us for additional inquiries

 

Kind regards,

Ron
TheTeam@Orcon

 

Standard? Standard slow internet...

 

Have sent one last email to request escalation to an engineer. If no luck, Ditching Orcon and happy to label them as Gamer Unfriendly.

 

Any recommendations for full gigabit net ISP from anyone in NZ?

 

 

Hey Chew, good to see you are still playing?  What sorta ping you getting to ANZ?

 

 

 

 



Pyromaniacs [PYRO] is recruiting now. Please email/pm me if you are interested.


Chewmatca #4 Posted 29 November 2017 - 02:37 PM

    Staff sergeant

  • Member
  • 16143 battles
  • 307
  • [RNS] RNS
  • Member since:
    11-04-2012

View PostHilly, on 29 November 2017 - 06:10 AM, said:

 

Hey Chew, good to see you are still playing?  What sorta ping you getting to ANZ?

 

Hi Hilly, yeah haven't played for a year or so, just moved back to Tauranga from QLD so back in NZ. When ANZ server is up i get 32ms in game or so which is brilliant so been using that and not bothering with Singapore server, but starting at 8pm to 4am kinda not working for weekend play. Bought a month of WTFast last night - that works, gets latency down to 120ms to Singapore server.

 

I think they over fixed the 13-57GF ... its too much fun now.



Chewmatca #5 Posted 30 November 2017 - 07:33 AM

    Staff sergeant

  • Member
  • 16143 battles
  • 307
  • [RNS] RNS
  • Member since:
    11-04-2012

Looks like im changing ISPs.

 

Routing via Orcon:

 

1 <1 ms <1 ms <1 ms fritz.box [192.168.0.1]
2 2 ms 2 ms 1 ms default-rdns.vocus.co.nz [xxx.xx.xx.xxx]
3 12 ms 5 ms 5 ms default-rdns.vocus.co.nz [101.98.5.23]
4 6 ms 6 ms 5 ms default-rdns.vocus.co.nz [101.98.5.22]
5 10 ms 6 ms 6 ms BE-101.bdr02.akl05.akl.VOCUS.net.nz [175.45.102.233]
6 30 ms 30 ms 30 ms bundle-10.cor01.akl05.akl.vocus.net.nz [114.31.202.100]
7 30 ms 29 ms 30 ms ten-0-3-0-4.cor03.syd03.nsw.vocus.net.au [114.31.202.83]
8 29 ms 29 ms 29 ms BE-10.cor01.syd11.nsw.VOCUS.net.au [114.31.192.111]
9 30 ms 30 ms 30 ms bundle-100.bdr01.syd03.nsw.vocus.net.au [114.31.192.85]
10 30 ms 29 ms 30 ms 220.101.73.81
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 32 ms 32 ms 32 ms 59.154.57.254
16 45 ms 43 ms 44 ms Bundle-Ether39.ken-edge902.sydney.telstra.net [165.228.132.205]
17 44 ms 44 ms 44 ms bundle-ether2.chw-edge902.sydney.telstra.net [203.50.11.105]
18 46 ms 45 ms 45 ms bundle-ether14.chw-core10.sydney.telstra.net [203.50.11.100]
19 46 ms 45 ms 44 ms bundle-ether8.exi-core10.melbourne.telstra.net [203.50.11.125]
20 58 ms 58 ms 59 ms bundle-ether5.way-core4.adelaide.telstra.net [203.50.11.92]
21 84 ms 86 ms 86 ms bundle-ether5.pie-core1.perth.telstra.net [203.50.11.17]
22 84 ms 83 ms 83 ms tengige0-0-1-0.pthp-core01.perth.net.reach.com [203.50.13.250]
23 231 ms 230 ms 231 ms i-0-1-3-0.sgpl-core01.bx.telstraglobal.net [202.84.143.181]
24 228 ms 228 ms 228 ms unknown.telstraglobal.net [202.84.224.198]
25 212 ms 212 ms 212 ms i-0-0-2-2.istt03.bi.telstraglobal.net [202.84.219.182]
26 * * * Request timed out.
27 237 ms 239 ms 237 ms sg2-n5596-fe-1-vl231.fe.core.pw [92.223.116.163]
28 221 ms 228 ms 244 ms sg2-v-a86.fe.core.pw [92.223.17.86]

 

28 Steps... yuk

 

Routing via spark - 15 steps:

 

1    <1 ms    <1 ms    <1 ms  192.168.1.254
  2     1 ms     2 ms     1 ms  adsl.xtra.co.nz [xxx.xxx.xxx.xxx]
  3     *        *        *     Request timed out.
  4     2 ms     2 ms     2 ms  ae8-10.akbr6.global-gateway.net.nz [122.56.116.5]
  5     3 ms     2 ms     2 ms  ae2-6.tkbr12.global-gateway.net.nz [122.56.127.17]
  6    24 ms    24 ms    25 ms  122.56.119.77
  7    25 ms    24 ms    25 ms  122.56.119.86
  8    28 ms    28 ms    27 ms  i-0-11-0-0.sydp01.bi.telstraglobal.net [202.84.220.210]
  9    29 ms    27 ms    28 ms  i-0-1-0-6.sydp-core03.bi.telstraglobal.net [202.84.220.209]
 10    85 ms    87 ms    84 ms  i-0-7-1-0.pthw-core01.bi.telstraglobal.net [202.84.143.146]
 11   134 ms   131 ms   130 ms  i-0-3-0-0.istt-core02.bx.telstraglobal.net [202.84.137.30]
 12   126 ms   126 ms   125 ms  i-0-0-1-0.istt03.bi.telstraglobal.net [202.84.243.94]
 13     *        *        *     Request timed out.
 14   128 ms   127 ms   129 ms  sg2-n5596-fe-1-vl231.fe.core.pw [92.223.116.163]
 15   127 ms   127 ms   127 ms  sg2-v-a86.fe.core.pw [92.223.17.86]

 

Latest response is unreal, they cannot be bothered contacting their provider and show no understanding, supposedly vocus/ orcon own their own fibre to Perth. But for unknown reason arent using it.

 

Hi Matt,

Thank you for your response.

I believe we don't have control of requesting changes to the main Vocus connections.

We really apologize for the inconvenience and thank you for your utmost patience.

Kind regards,

Ron
TheTeam@Orcon

 

in reply to:

 

Hi Kevin
 
Thank you for your response.
 
 
Given that Vocus are connecting to Telstra, you are their customer and can request routing is reviewed as it is affecting your customer.
 
Can you please do this. Problem Route:
 
21 84 ms 86 ms 86 ms bundle-ether5.pie-core1.perth.telstra.net [203.50.11.17]
22 84 ms 83 ms 83 ms tengige0-0-1-0.pthp-core01.perth.net.reach.com [203.50.13.250]
23 231 ms 230 ms 231 ms i-0-1-3-0.sgpl-core01.bx.telstraglobal.net [202.84.143.181]
 
This is all within Telstra's network.
 
example of the good route via telstra:
 
 
  8    28 ms    28 ms    27 ms  i-0-11-0-0.sydp01.bi.telstraglobal.net [202.84.220.210]
  9    29 ms    27 ms    28 ms  i-0-1-0-6.sydp-core03.bi.telstraglobal.net [202.84.220.209]
 10    85 ms    87 ms    84 ms  i-0-7-1-0.pthw-core01.bi.telstraglobal.net [202.84.143.146]
 11   134 ms   131 ms   130 ms  i-0-3-0-0.istt-core02.bx.telstraglobal.net [202.84.137.30]

 12   126 ms   126 ms   125 ms  i-0-0-1-0.istt03.bi.telstraglobal.net [202.84.243.94]
 13     *        *        *     Request timed out.
 14   128 ms   127 ms   129 ms  sg2-n5596-fe-1-vl231.fe.core.pw [92.223.116.163]
 15   127 ms   127 ms   127 ms  sg2-v-a86.fe.core.pw [92.223.17.86]
 
 
Please send the two tracerts to a telstra engineer they would be able to review and rectify.
 
Kind Regards
Matt

 

 

 



Pwnedbyanoob #6 Posted 05 December 2017 - 03:12 PM

    Corporal

  • Member
  • 35698 battles
  • 12
  • Member since:
    01-14-2013

Dont bother with Trustpower either - same issue. Prior to the October cable cut I was getting 130ms to the Singapore server, now it's 190 ish (before the cable cut this week).    They send their uplink traffic to Vodafone who sends is to Japan then Hong Kong then Singapore.  I've asked them to raise it with their uplink provider and they've basically said no.

 

I've tried wtfast and that brought my ping back down to 130ms

 

 


Edited by Pwnedbyanoob, 05 December 2017 - 03:13 PM.






1 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users