Forum Home
Press F1
 
Thread ID: 118514 2011-06-08 05:21:00 Orcon routing issue - What are my options? 8ftmetalhaed (14526) Press F1
Post ID Timestamp Content User
1207792 2011-06-08 05:21:00 I'm currently writing an email to orcon(saved it as a draft) because I'm having issues with my favorite team fortress 2 servers suffering from major lag.

They changed their public IP addresses in the second week of may, and my pings shot up from 70-90 all the way up to 200 average because my traffic now goes via new york, then florida, then finally on to australia. (thanks whois lookups :))

They're currently trying to say it's a general high latency issue, when the tracert and whois outputs I copy pasted CLEARLY show where the damn latency is.

(it's in their incorrect routing tables)

Anyway, before I send this email and hopefully get someone to look at it, is there any chance they're going to try and charge me for it?
I always have these sorts of issues and this is always what makes me just 'deal with it'. I always get the feeling they're TRYING to say it's my fault, and I sure as hell can't afford the $200 fee or whatever if it turns out it is.

Bleargh. really, it's not like they can't do it remotely anyway?

123.100.233.14
Actually, can anyone else do a tracert or ping to this IP address for me? 		8ftmetalhaed (14526)
1207793 2011-06-08 06:03:00 The attached ping and tracert screen dump may be too small to read, if so grab it from here : www.box.net Terry Porritt (14)
1207794 2011-06-08 06:09:00 I am also on Orcon and my tracert is crap too, usually my ping is very good
180ms average and goes to hell at point 5.

5 151ms 151ms 151ms ge-5-0-1.cre1.1a1.odyssey.net.nz [206.223.123.92] 		DeSade (984)
1207795 2011-06-08 06:10:00 Ping and tracert are all very good Safari (3993)
1207796 2011-06-08 07:09:00 can you post a screen shot of your results, and what is your isp?

If i can narrow it down to being an orcon problem, then awesome. Else i have no clue how I'd fix it. 		8ftmetalhaed (14526)
1207797 2011-06-08 12:51:00 I'm on orcon, here you go:

Tracing route to 123.100.233.14 over a maximum of 30 hops

1 1 ms 1 ms 2 ms 192.168.1.254
2 2 ms 3 ms 2 ms adsl.*******.co.nz [192.168.100.2]
3 32 ms 28 ms 18 ms lo1.ras1.nct.orcon.net.nz [60.234.8.201]
4 23 ms 24 ms 26 ms xe-1-0-0.cre1.nct.orcon.net.nz [121.98.9.13]
5 21 ms 17 ms 17 ms 121.99.12.0
6 146 ms 143 ms 147 ms ge-5-0-1.cre1.la1.odyssey.net.nz [206.223.123.92]
7 144 ms 204 ms 148 ms 10gigabitethernet1-3.core1.lax1.he.net [206.223.123.37]
8 178 ms 181 ms 174 ms 10gigabitethernet1-3.core1.pao1.he.net [72.52.92.21]
9 176 ms 179 ms 176 ms 10gigabitethernet3-4.core1.sjc1.he.net [72.52.92.113]
10 206 ms 186 ms 178 ms tpg-internet-pty-ltd.10gigabitethernet3-1.core1.sjc1.he.net [72.52.66.22]
11 171 ms 174 ms 173 ms eth2-12.rn-400harris-core-02.pipenetworks.com [203.161.136.193]
12 177 ms 176 ms 192 ms ip-18-136-161-203.static.pipenetworks.com [203.161.136.18]
13 175 ms 214 ms 176 ms 123.100.233.14

Trace complete. 		Deimos (5715)
1207798 2011-06-08 13:05:00 Mine
5 151ms 151ms 151ms ge-5-0-1.cre1.1a1.odyssey.net.nz [206.223.123.92]

Deimos
6 146 ms 143 ms 147 ms ge-5-0-1.cre1.la1.odyssey.net.nz [206.223.123.92]

There's your problem. 		DeSade (984)
1207799 2011-06-08 13:08:00 Cheers, although I would prefer to grab someone's tracert who isn't on orcon to confirm it.
Will keep this noted though :)

Just putting this here for reference - a friend just ping'ed and got

I am receiving a reply
64 bytes from 123.100.233.14: icmp_req=5 ttl=117 time=52.7 ms on maxnet ISP 		8ftmetalhaed (14526)
1207800 2011-06-08 13:33:00 From Xtra:-

Tracing route to 123.100.233.14 over a maximum of 30 hops

1 49 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 45 ms 26 ms 33 ms 122-59-72-1.jetstream.xtra.co.nz [122.59.72.1]
3 * 42 ms 29 ms mdr-fid-int.akbr5.global-gateway.net.nz [202.37.244.222]
4 29 ms 30 ms 29 ms ae4-10.akbr5.global-gateway.net.nz [202.37.244.221]
5 29 ms 30 ms 29 ms ae1-2.akbr4.global-gateway.net.nz [202.50.232.77]
6 29 ms 30 ms 29 ms ae1-10.tkbr9.global-gateway.net.nz [202.50.232.37]
7 53 ms 54 ms 53 ms so7-0-1.sybr6.global-gateway.net.nz [122.56.127.42]
8 55 ms 53 ms 53 ms xe2-0-0-2.sybr4.global-gateway.net.nz [202.50.232.242]
9 53 ms 54 ms 54 ms vlan356.52gdc76f02.optus.net.au [59.154.21.137]
10 56 ms 56 ms 56 ms te3-3-3927.sg4.optus.net.au [61.88.241.255]
11 56 ms 55 ms 55 ms 119.225.5.238
12 56 ms 56 ms 57 ms syd-pow-cla-crt1-po8.tpgi.com.au [202.7.171.162]
13 57 ms 55 ms 55 ms eth2-12.rn-400harris-core-02.pipenetworks.com [203.161.136.193]
14 55 ms 55 ms 56 ms ip-18-136-161-203.static.pipenetworks.com [203.161.136.18]
15 55 ms 55 ms 53 ms 123.100.233.14

Trace complete. 		Snorkbox (15764)
1207801 2011-06-08 22:28:00 TelstraClear cable:

Tracing route to 123.100.233.14 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms ############### [192.168.1.2]
2 10 ms 7 ms 7 ms 10.33.32.1
3 216 ms 273 ms 229 ms lo0.internet.ivpn.pe25.telstraclear.net [218.101.61.124]
4 * * * Request timed out.
5 18 ms 23 ms 19 ms ie1-g-0-0-0.telstraclear.net [203.98.50.1]
6 25 ms 17 ms 21 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251]
7 19 ms 20 ms 21 ms 203.167.233.10
8 45 ms 45 ms 46 ms i-3-1-0.syd-core03.bx.reach.com [202.84.142.153]
9 45 ms 45 ms 50 ms i-0-5-4-0.sydp-core05.bx.reach.com [202.84.249.13]
10 62 ms 47 ms 45 ms i-11-0-0.sydp-core01.bi.reach.com [202.84.220.210]
11 77 ms 58 ms 54 ms telstra_domestic_peer-peer.sydp-core01.pr.reach.com [134.159.126.34]
12 46 ms 52 ms 64 ms Bundle-Ether3.chw-core2.Sydney.telstra.net [203.50.6.26]
13 46 ms 45 ms 46 ms TenGigabitEthernet7-1.chw38.Sydney.telstra.net [203.50.20.176]
14 48 ms 54 ms 44 ms aaptli.lnk.telstra.net [165.228.165.26]
15 52 ms 47 ms 45 ms te2-4.sglebdist01.aapt.net.au [202.10.14.6]
16 48 ms 45 ms 49 ms te2-1-110.sglebdist02.aapt.net.au [202.10.12.131]
17 51 ms 57 ms 53 ms te0-3-1-0.sclarcore01.aapt.net.au [202.10.12.9]
18 54 ms 51 ms 45 ms te2-2.sclardist01.aapt.net.au [202.10.12.2]
19 51 ms 53 ms 56 ms 1-1-1.sclarinte01.aapt.net.au [203.131.60.31]
20 48 ms 50 ms 47 ms 210.87.9.178
21 50 ms 44 ms 50 ms ip-18-136-161-203.static.pipenetworks.com [203.161.136.18]
22 45 ms 46 ms 45 ms 123.100.233.14

Trace complete. 		MushHead (10626)
1 2